|
Hi Michael, Would you mind posting the exact command you are prompting? As mentioned, there is a fix for a stack overflow problem in 6.0.0.2. Do you have it installed? thanks, Violaine Batthish WebSphere Development Studio Client, IBM Toronto Lab You know you've achieved perfection in design, not when you have nothing more to add, but when you have nothing more to take away. - Antoine de Saint-Exupéry wdsci-l-bounces@xxxxxxxxxxxx wrote on 15/11/2005 19:47:30: > While prompting a CL command (SNDPGMMSG within the EXEC for a MONMSG), I > received an error dialog informing me a stack overflow happened. It was > recommended to exit the workbench or risk workbench termination and gave > me the option to exit immediately. It also directed me to the .log file. > I chose not to exit immediately, instead canceling my way back to my CLP. > Then I closed the workbench and saved my (partially) modified member. It > successfully saved to my AS/400 (er -- to the OS/400) source file and > ended normally. > > I was able restart the workbench and navigate my way back to the member > and open it without any problems. That is until I tried the same prompt > action again. It presents the prompted SNDPGMMSG command, but when I try > to type any additional text in the MSG parameter, I get the same error all > over. While it is nice error recovery, I would like to add the necessary > text to the message. > > Here's the pertinent entries from the .log file for the stack overflow (in > case IBM happens to be monitoring and is interested): > > > !ENTRY org.eclipse.ui 4 4 Nov 15, 2005 19:11:43.569 > !MESSAGE Unhandled event loop exception > > !ENTRY org.eclipse.ui 4 0 Nov 15, 2005 19:11:43.584 > !MESSAGE java.lang.StackOverflowError > !STACK 0 > java.lang.StackOverflowError > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:63) > at java.lang.Long.parseLong(Long.java:408) > at java.lang.Long.valueOf(Long.java:523) > at > com.ibm.etools.iseries.core.util.clprompter.ClLiteral.getObject(Long.java) > at > com.ibm.etools.iseries.core.util.clprompter.ClExpression.<init>(Unknown > Source) > <...snip...> > .... repeats the line directly above 1191 times ... > ....> > at > com.ibm.etools.iseries.core.util.clprompter.ClExpressionListener. > modifyText(Unknown > Source) > at org.eclipse.swt.widgets.TypedListener.handleEvent(Unknown > Source) > at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source) > at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source) > at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source) > at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source) > at org.eclipse.swt.widgets.Text.wmCommandChild(Unknown Source) > at org.eclipse.swt.widgets.Control.WM_COMMAND(Unknown Source) > at org.eclipse.swt.widgets.Control.windowProc(Unknown Source) > at org.eclipse.swt.widgets.Display.windowProc(Unknown Source) > at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native > Method) > at org.eclipse.swt.internal.win32.OS.CallWindowProc(Unknown > Source) > at org.eclipse.swt.widgets.Text.callWindowProc(Unknown Source) > at org.eclipse.swt.widgets.Control.windowProc(Unknown Source) > at org.eclipse.swt.widgets.Display.windowProc(Unknown Source) > at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native > Method) > at org.eclipse.swt.internal.win32.OS.DispatchMessage(Unknown > Source) > at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source) > at org.eclipse.jface.window.Window.runEventLoop(Unknown Source) > at org.eclipse.jface.window.Window.open(Unknown Source) > at > com.ibm.etools.iseries.core.util.clprompter.ClCommandLineDialog. > prompt(Unknown > Source) > at > com.ibm.etools.iseries.core.util.clprompter.ClPromptKeyListener. > keyPressed(Unknown > Source) > at org.eclipse.swt.widgets.TypedListener.handleEvent(Unknown > Source) > at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source) > at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source) > at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source) > at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source) > at org.eclipse.swt.widgets.Control.sendKeyEvent(Unknown Source) > at org.eclipse.swt.widgets.Text.sendKeyEvent(Unknown Source) > at org.eclipse.swt.widgets.Control.sendKeyEvent(Unknown Source) > at org.eclipse.swt.widgets.Control.WM_KEYDOWN(Unknown Source) > at org.eclipse.swt.widgets.Control.windowProc(Unknown Source) > at org.eclipse.swt.widgets.Display.windowProc(Unknown Source) > at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native > Method) > at org.eclipse.swt.internal.win32.OS.DispatchMessage(Unknown > Source) > at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source) > at org.eclipse.jface.window.Window.runEventLoop(Unknown Source) > at org.eclipse.jface.window.Window.open(Unknown Source) > at > com.ibm.etools.iseries.core.util.clprompter.ClCommandLineDialog. > prompt(Unknown > Source) > at > com.ibm.etools.iseries.core.util.clprompter.CLPrompter.showDialog(Unknown > Source) > at > com.ibm.etools.iseries.editor.ISeriesEditorCLParser.showPromptDialog(Unknown > Source) > at > com.ibm.etools.iseries.editor.ISeriesEditorCLParser.prompt(Unknown Source) > at > com.ibm.etools.iseries.editor.ISeriesEditorParser.doPromptAction(Unknown > Source) > at > com.ibm.etools.iseries.editor.ISeriesEditorParserAction.run(Unknown > Source) > at > com.ibm.etools.iseries.editor.ISeriesEditorParserAction.doAction(Unknown > Source) > at com.ibm.lpex.core.ActionHandler.doActionIfAvailable(Unknown > Source) > at com.ibm.lpex.core.ActionHandler.doKeyEvent(Unknown Source) > at com.ibm.lpex.core.TextWindow.processKeyEvent(Unknown Source) > at com.ibm.lpex.core.TextWindow.access$400(Unknown Source) > at com.ibm.lpex.core.TextWindow$6.handleEvent(Unknown Source) > at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source) > at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source) > at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source) > at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source) > at org.eclipse.swt.widgets.Control.sendKeyEvent(Unknown Source) > at org.eclipse.swt.widgets.Control.sendKeyEvent(Unknown Source) > at org.eclipse.swt.widgets.Control.WM_KEYDOWN(Unknown Source) > at org.eclipse.swt.widgets.Control.windowProc(Unknown Source) > at org.eclipse.swt.widgets.Display.windowProc(Unknown Source) > at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native > Method) > at org.eclipse.swt.internal.win32.OS.DispatchMessage(Unknown > Source) > at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source) > at org.eclipse.ui.internal.Workbench.runEventLoop(Unknown Source) > at org.eclipse.ui.internal.Workbench.runUI(Unknown Source) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Unknown > Source) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(Unknown Source) > at org.eclipse.ui.internal.ide.IDEApplication.run(Unknown Source) > at > org.eclipse.core.internal.runtime.PlatformActivator$1.run(Unknown Source) > at > org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273) > at > org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) > at > sun.reflect.DelegatingMethodAccessorImpl. > invoke(DelegatingMethodAccessorImpl.java:60) > at java.lang.reflect.Method.invoke(Method.java:391) > at org.eclipse.core.launcher.Main.basicRun(Main.java:185) > at org.eclipse.core.launcher.Main.run(Main.java:704) > at org.eclipse.core.launcher.Main.main(Main.java:688) > > The second crash (er.. exception) log looks pretty similar, but not quite > as long. > > Michael Quigley > AS/400 Programming Coordinator > The Way International > www.TheWay.org
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.