Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ptp-dev] Problems with Eclipse session hang after starting proxy

I don't claim to understand this code, but I fixed a couple of places not checking for null return.

Anyone willing to rewrite and/or document the UI code so that it is understandable will get automatic entry to the PTP hall of fame :-)

Greg


On Oct 11, 2007, at 9:46 AM, Dave Wootton wrote:

Greg
The hang seems to be gone now. I did notice another minor problem that I think might be related. When I shut down my PTP session and restart it, I
notice the following error showing up in the error log. I suspect it's
part of Eclipse shutdown since I don't see it until I restart the PTP
session

Dave

org.osgi.framework.BundleException: Exception in
org.eclipse.ptp.core.PTPCorePlugin.stop() of bundle org.eclipse.ptp.core.
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop (BundleContextImpl.java:1056)
at
org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker (BundleHost.java:457)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend (AbstractBundle.java:526)
at
org.eclipse.osgi.framework.internal.core.Framework.suspendBundle (Framework.java:1148)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL (StartLevelManager.java:675)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartL evel(StartLevelManager.java:291)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown (StartLevelManager.java:261)
at
org.eclipse.osgi.framework.internal.core.SystemBundle.suspend (SystemBundle.java:188)
at
org.eclipse.osgi.framework.internal.core.Framework.shutdown (Framework.java:622)
at
org.eclipse.osgi.framework.internal.core.Framework.close (Framework.java:525)
at org.eclipse.osgi.framework.internal.core.OSGi.close(OSGi.java:41)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown (EclipseStarter.java:399)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run (EclipseStarter.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:64)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
at org.eclipse.equinox.launcher.Main.main(Main.java:1144)
Caused by: java.lang.NullPointerException
at
org.eclipse.ptp.ui.managers.JobManager.removeProcess (JobManager.java:95)
at
org.eclipse.ptp.ui.views.ParallelJobsView.handleEvent (ParallelJobsView.java:292)
at
org.eclipse.ptp.internal.core.elements.PJob.fireRemoveProcesses (PJob.java:286)
at
org.eclipse.ptp.internal.core.elements.PJob.removeProcesses (PJob.java:237)
at
org.eclipse.ptp.internal.core.elements.PQueue.removeJobs (PQueue.java:180)
at
org.eclipse.ptp.rmsystem.AbstractResourceManager.removeQueues (AbstractResourceManager.java:1059)
at
org.eclipse.ptp.rmsystem.AbstractResourceManager.cleanUp (AbstractResourceManager.java:738)
at
org.eclipse.ptp.rmsystem.AbstractResourceManager.shutdown (AbstractResourceManager.java:511)
at
org.eclipse.ptp.internal.core.ModelManager.stopResourceManagers (ModelManager.java:278)
at
org.eclipse.ptp.internal.core.ModelManager.shutdown (ModelManager.java:250)
at org.eclipse.ptp.core.PTPCorePlugin.stop(PTPCorePlugin.java:188)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$3.run (BundleContextImpl.java:1040) at java.security.AccessController.doPrivileged (AccessController.java:242)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop (BundleContextImpl.java:1036)
... 20 more
Root exception:
java.lang.NullPointerException
at
org.eclipse.ptp.ui.managers.JobManager.removeProcess (JobManager.java:95)
at
org.eclipse.ptp.ui.views.ParallelJobsView.handleEvent (ParallelJobsView.java:292)
at
org.eclipse.ptp.internal.core.elements.PJob.fireRemoveProcesses (PJob.java:286)
at
org.eclipse.ptp.internal.core.elements.PJob.removeProcesses (PJob.java:237)
at
org.eclipse.ptp.internal.core.elements.PQueue.removeJobs (PQueue.java:180)
at
org.eclipse.ptp.rmsystem.AbstractResourceManager.removeQueues (AbstractResourceManager.java:1059)
at
org.eclipse.ptp.rmsystem.AbstractResourceManager.cleanUp (AbstractResourceManager.java:738)
at
org.eclipse.ptp.rmsystem.AbstractResourceManager.shutdown (AbstractResourceManager.java:511)
at
org.eclipse.ptp.internal.core.ModelManager.stopResourceManagers (ModelManager.java:278)
at
org.eclipse.ptp.internal.core.ModelManager.shutdown (ModelManager.java:250)
at org.eclipse.ptp.core.PTPCorePlugin.stop(PTPCorePlugin.java:188)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$3.run (BundleContextImpl.java:1040) at java.security.AccessController.doPrivileged (AccessController.java:242)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop (BundleContextImpl.java:1036)
at
org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker (BundleHost.java:457)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend (AbstractBundle.java:526)
at
org.eclipse.osgi.framework.internal.core.Framework.suspendBundle (Framework.java:1148)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL (StartLevelManager.java:675)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartL evel(StartLevelManager.java:291)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown (StartLevelManager.java:261)
at
org.eclipse.osgi.framework.internal.core.SystemBundle.suspend (SystemBundle.java:188)
at
org.eclipse.osgi.framework.internal.core.Framework.shutdown (Framework.java:622)
at
org.eclipse.osgi.framework.internal.core.Framework.close (Framework.java:525)
at org.eclipse.osgi.framework.internal.core.OSGi.close(OSGi.java:41)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown (EclipseStarter.java:399)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run (EclipseStarter.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:64)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
at org.eclipse.equinox.launcher.Main.main(Main.java:1144)

Dave



Greg Watson <g.watson@xxxxxxxxxxxx>
Sent by: ptp-dev-bounces@xxxxxxxxxxx
10/11/2007 07:43 AM
Please respond to
Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>


To
Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>
cc

Subject
Re: [ptp-dev] Problems with Eclipse session hang after starting proxy






Dave,

I found a potential problem in ParallelMachinesView. After this fix
I'm no longer able to reproduce the problem. Can you give it a try
and let me know if it looks ok?

Thanks,

Greg

On Oct 9, 2007, at 2:56 PM, Greg Watson wrote:

Ok, I'm able to repeat this. Will try and fix asap.

Greg

On Oct 9, 2007, at 2:18 PM, Greg Watson wrote:

Dave,

Is anything displayed in the PTP Runtime at this point (machines,
nodes, etc.)? Also, which version of RSE are you using? The
release version, or have you checked it out from CVS?

Greg

On Oct 9, 2007, at 12:34 PM, Dave Wootton wrote:

I'm running into a problem which now seems to happen every time I
start my
proxy. Up until the point where I start the proxy, my test
Eclipse session
runs normally. Once I start the proxy, the Eclipse UI works for a
while
then is completely frozen. There is no response to mouse clicks
anywhere,
and if I obscure and expose part of the Eclipse session window,
it does
not repaint. This leads me to believe something is blocked or
looping on
one of the main UI threads. I think this is happening after the
front end
receives a machine state event in response to the proxy creating
a new
machine (default) since that's the last message I see before the
hang. If
I click the UI quickly enough, before I see this message, then it
responds
for a couple seconds before it hangs.

Has anyone else seen this with the latest code level?

I started to debug this by suspending the UI threads and looking
at call
stacks, but I'm not sure how to identify a UI thread out of the
dozen or
so threads in the session. I'm not sure this is the correct approach
either since I suppose the UI thread could be running normally
and is just
blocked waiting for notification from some ther thread.

This has been happening off and on for me for the last few days.
Now it
seems to be consistent. The only code I have been changing today
is my
parallel tab code, which I'm not even getting to now.

I don't see any messages in the error log, or elsewhere.

Any suggestions?

Thanks
Dave
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev


_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev


_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev


_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev


_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev




Back to the top