- This topic has 47 replies, 16 voices, and was last updated 13 years, 6 months ago by
.
-
Posts
-
Guys, thank you for the report and details. Something fishy going on here. The first thing we need to do is establish some common ground and confirm exactly what everyone is seeing is the same behavior. I’m going to summarize below and you guys confirm if this is the issue:
PROBLEM: Every few moments while editing a dialog will popup saying that an error has occurred updating progress. This also happens when saving a file.
If that is correct, the first thing to do is go to Window > Show View > Other > PDE Runtime > Error Log, hit the red “X” to clear all the errors then start working again until it occurs, then paste any exception you find here. That will help us figure out what code is failing. (I know mspronk posted his stack trace above but unfortunately it didn’t have any very specific start or end point to help us troubleshoot what was going on).
NOTE: For the non-Pulse folks, you might want to go to Help > Softwre Update > Manage Configuration, and confirm that there aren’t any load errors listed suggesting that something is borked with the install.
@support-rkalla wrote:
I’m going to summarize below and you guys confirm if this is the issue:
PROBLEM: Every few moments while editing a dialog will popup saying that an error has occurred updating progress. This also happens when saving a file.
Not exactly the case for me. I was able to narrow down a bit more than before. I have Weblogic 10.2 installed, and am controlling it via the servers tab in the MyEclipse perspective. I went about editing some JSF files and deploying to the server successfully. I came across some errors in my code and, to clear up the server, I right-clicked the server and selected ‘Restart’. That’s when I got the errors… three of them. Here’s was displayed in the PDE errors log:
Error Tue Jul 22 13:33:40 GMT-07:00 2008 Unhandled event loop exception org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalArgumentException: Argument cannot be null) at org.eclipse.swt.SWT.error(SWT.java:3563) at org.eclipse.swt.SWT.error(SWT.java:3481) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:132) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3659) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447) at org.eclipse.equinox.launcher.Main.run(Main.java:1173) at org.eclipse.equinox.launcher.Main.main(Main.java:1148) Caused by: java.lang.IllegalArgumentException: Argument cannot be null at org.eclipse.swt.SWT.error(SWT.java:3547) at org.eclipse.swt.SWT.error(SWT.java:3481) at org.eclipse.swt.SWT.error(SWT.java:3452) at org.eclipse.swt.widgets.Widget.error(Widget.java:432) at org.eclipse.swt.widgets.Link.setText(Link.java:571) at org.eclipse.ui.internal.progress.ProgressInfoItem.updateText(ProgressInfoItem.java:773) at org.eclipse.ui.internal.progress.ProgressInfoItem.setLinkText(ProgressInfoItem.java:759) at org.eclipse.ui.internal.progress.ProgressInfoItem.refresh(ProgressInfoItem.java:530) at org.eclipse.ui.internal.progress.ProgressInfoItem.setDisplayed(ProgressInfoItem.java:902) at org.eclipse.ui.internal.progress.ProgressInfoItem.setDisplayed(ProgressInfoItem.java:888) at org.eclipse.ui.internal.progress.DetailedProgressViewer.updateVisibleItems(DetailedProgressViewer.java:503) at org.eclipse.ui.internal.progress.DetailedProgressViewer.access$0(DetailedProgressViewer.java:497) at org.eclipse.ui.internal.progress.DetailedProgressViewer$2.controlMoved(DetailedProgressViewer.java:99) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:210) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:962) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:943) at org.eclipse.swt.widgets.Control.WM_MOVE(Control.java:4186) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3718) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4351) at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2260) at org.eclipse.swt.widgets.Scrollable.callWindowProc(Scrollable.java:77) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3760) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4351) at org.eclipse.swt.internal.win32.OS.SetWindowPos(Native Method) at org.eclipse.swt.widgets.Widget.SetWindowPos(Widget.java:1235) at org.eclipse.swt.widgets.Control.setBounds(Control.java:2521) at org.eclipse.swt.widgets.Control.setBounds(Control.java:2503) at org.eclipse.swt.widgets.Control.setLocation(Control.java:2829) at org.eclipse.swt.custom.ScrolledComposite.setContent(ScrolledComposite.java:438) at org.eclipse.ui.internal.progress.DetailedProgressViewer.updateForShowingProgress(DetailedProgressViewer.java:180) at org.eclipse.ui.internal.progress.DetailedProgressViewer.remove(DetailedProgressViewer.java:424) at org.eclipse.ui.internal.progress.ProgressViewerContentProvider.remove(ProgressViewerContentProvider.java:218) at org.eclipse.ui.internal.progress.ProgressViewUpdater$1.runInUIThread(ProgressViewUpdater.java:280) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:94) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:129) ... 23 moreThen this…
Error Tue Jul 22 13:33:40 GMT-07:00 2008 Unhandled event loop exception org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) at org.eclipse.swt.SWT.error(SWT.java:3563) at org.eclipse.swt.SWT.error(SWT.java:3481) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:132) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3659) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447) at org.eclipse.equinox.launcher.Main.run(Main.java:1173) at org.eclipse.equinox.launcher.Main.main(Main.java:1148) Caused by: java.lang.NullPointerException at org.eclipse.ui.internal.progress.JobTreeElement.compareTo(JobTreeElement.java:82) at org.eclipse.ui.internal.progress.JobInfo.compareTo(JobInfo.java:167) at org.eclipse.ui.internal.progress.ProgressManagerUtil$1.compare(ProgressManagerUtil.java:107) at org.eclipse.jface.viewers.ViewerComparator$1.compare(ViewerComparator.java:187) at java.util.Arrays.mergeSort(Unknown Source) at java.util.Arrays.sort(Unknown Source) at org.eclipse.jface.viewers.ViewerComparator.sort(ViewerComparator.java:185) at org.eclipse.ui.internal.progress.DetailedProgressViewer.add(DetailedProgressViewer.java:158) at org.eclipse.ui.internal.progress.ProgressViewerContentProvider.add(ProgressViewerContentProvider.java:213) at org.eclipse.ui.internal.progress.ProgressViewUpdater$1.runInUIThread(ProgressViewUpdater.java:277) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:94) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:129) ... 23 moreand, finally, this…
Error Tue Jul 22 13:33:39 GMT-07:00 2008 Unhandled event loop exception org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalArgumentException: Argument cannot be null) at org.eclipse.swt.SWT.error(SWT.java:3563) at org.eclipse.swt.SWT.error(SWT.java:3481) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:132) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3659) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447) at org.eclipse.equinox.launcher.Main.run(Main.java:1173) at org.eclipse.equinox.launcher.Main.main(Main.java:1148) Caused by: java.lang.IllegalArgumentException: Argument cannot be null at org.eclipse.swt.SWT.error(SWT.java:3547) at org.eclipse.swt.SWT.error(SWT.java:3481) at org.eclipse.swt.SWT.error(SWT.java:3452) at org.eclipse.swt.widgets.Widget.error(Widget.java:432) at org.eclipse.swt.widgets.Link.setText(Link.java:571) at org.eclipse.ui.internal.progress.ProgressInfoItem.updateText(ProgressInfoItem.java:773) at org.eclipse.ui.internal.progress.ProgressInfoItem.setLinkText(ProgressInfoItem.java:759) at org.eclipse.ui.internal.progress.ProgressInfoItem.refresh(ProgressInfoItem.java:530) at org.eclipse.ui.internal.progress.ProgressInfoItem.createChildren(ProgressInfoItem.java:280) at org.eclipse.ui.internal.progress.ProgressInfoItem.<init>(ProgressInfoItem.java:186) at org.eclipse.ui.internal.progress.DetailedProgressViewer.createNewItem(DetailedProgressViewer.java:193) at org.eclipse.ui.internal.progress.DetailedProgressViewer.add(DetailedProgressViewer.java:167) at org.eclipse.ui.internal.progress.ProgressViewerContentProvider.add(ProgressViewerContentProvider.java:213) at org.eclipse.ui.internal.progress.ProgressViewUpdater$1.runInUIThread(ProgressViewUpdater.java:277) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:94) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:129) ... 23 moreI should also mention that once I receive this error, the only way to clear it out is to restart the IDE.
Any more feedback from the experts on this issue??
One thing that seems to be consistent for me (and I believe someone else mentioned this as well) is that this issue does not start appearing until I have at least started a web application locally in a Tomcat Server.
I have tried Tomcat 5.5, 6.0 as well as the MyEclipse Tomcat, it does not seem to make a difference. It does not start guaranteed, but having started an app in Tomcat at least once seem to be a ‘pre-requisite’ for the problem to start coming up.
After the error shows up once, it keeps showing up (I normally just move the error window to my 2nd monitor so it doesn’t interfere), until MyEclipse is restarted. Stopping and/or starting Tomcat at this point does not affect the occurrence of the error anymore: once you’ve at least started it once that seems to be the trigger.
MWThomas and Timo, would you concur with what mspronk said? About needing to have a server started and a web project deployed before this error will start popping up and then never stops until you restart the workbench?
I am declaring race-condition on this… but need to narrow it down a bit more. Thanks for your help guys!
NOTE: Just to be clear, I’ve tried to reproduce this already and had 2 of my QA engineers give this 2 hours already trying to reproduce… that’s one of the reasons I need details, I don’t know what we are missing here.
I’m using Tomcat 5.5 too and I’m seeing this error after *some* time developing (including running and testing) my JSF-Spring-Hibernate apps. It occured *after* running tomcat for the first time so far, but not every time.
Hope this helps… :-/
Just to make clear: This bug is still a half of a year open and hundred of users have to rebuild their workspaces all the time the error appears spending 1000h of hours of time…
i finally fixed that problem for me:
a) leave myeclipse
b) point explorer to the .metadata folder
c) right mouse button select “search” giving criteria ‘org.eclipse.update*’ (without quotes)
d) deleting all the files/folders found
e) restart myeclipseno further messages appeared till now…
I can confirm that, at least in my case, I have to have an app server running. In my case, I’m using Weblogic 8.1 and Weblogic 10.2. I get the same errors no matter which app server I use though.
Thanks for your time on this…
MWThomson,
By chance did you try kirsch’s workaround posted above, did that help?I would suggest “moving” the found files out into a separate dir incase it hoses the workspace as I’m not sure why this even works in the first place… very strange.
QQ: Has anyone tried restarting using the -clean command line argument?
https://www.genuitec.com/forums/topic/troubleshoot-using-the-clean-command-line-argument/I would try kirsch’s solution, but I don’t have any org.eclipse.updates* files found in my .metadata folder. But, I’m running a new install of MyEclipse 6.5… not sure if that has anything to do with it.
I restarted using the -clean command line arg and that seems to be working for now. But, not knowing for sure what I did to get the error in the first place, this may not mean anything…
Please keep us posted… -clean forces the IDE to rebuild it’s plugin cache, I wonder if it was managing an invalid/old state that was making it freak out.
@support-rkalla wrote:
Please keep us posted… -clean forces the IDE to rebuild it’s plugin cache, I wonder if it was managing an invalid/old state that was making it freak out.
Apparently, -clean had little to no effect. After working in MyEclipse for just one hour, the IDE started throwing exceptions again. Same thing as before.
