Community
Participate
Working Groups
On the very first start of a downloaded RSE on a fresh blank workspace, the following exception is logged to the PDE Error Log. I also observe that opening the RSE Perspective is slow. Perhaps creating the RSE DOM in the RemoteSystemsConnections project is too slow? While loading class "org.eclipse.rse.persistence.IRSEPersistenceManager", thread "Worker-2" timed out waiting (5000ms) for thread "main" to finish starting bundle "org.eclipse.rse.ui". To avoid deadlock, thread "Worker-2" is proceeding but "org.eclipse.rse.persistence.IRSEPersistenceManager" may not be fully initialized. java.lang.Exception: Generated exception. at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.preFindLocalClass(EclipseLazyStarter.java:75) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:409) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:188) at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:339) at org.eclipse.osgi.framework.internal.core.SingleSourcePackage.loadClass(SingleSourcePackage.java:37) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:388) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:352) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) at org.eclipse.rse.files.ui.resources.SystemTempFileListener.resourceChanged(SystemTempFileListener.java:136) at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:280) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:274) at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:148) at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:256) at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:958) at org.eclipse.core.internal.resources.Folder.create(Folder.java:106) at org.eclipse.rse.persistence.PropertyFileProvider.getFolder(PropertyFileProvider.java:597) at org.eclipse.rse.persistence.PropertyFileProvider.saveNode(PropertyFileProvider.java:143) at org.eclipse.rse.persistence.PropertyFileProvider.saveRSEDOM(PropertyFileProvider.java:121) at org.eclipse.rse.internal.persistence.SaveRSEDOMJob.run(SaveRSEDOMJob.java:46) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
I don't think the DOM creation is slow. Its no different at startup than it is at other times. I suspect there are reasons the creation job is waiting due to other portions of workbench startup. This error appears even when the old persistence manager was being used. Kushal - can you see what the problem is here?
I don't see this problem either. Martin, can you please let us know if you still see this problem, and if so, which JVM you are trying this with? I'm marking the bug as works for me.
Note that I can not reproduce bug 138360 either when running a downloaded RSE or through PDE runtime.
I also don't see it any more with the 1.0.1 candidates. Looks like this was fixed by changing the persistence manager. Closing for now.
The issue was seen again in RSE 2.0, now being tracked as bug 203105.
