Community
Participate
Working Groups
This is related to the fix in bug312917. If you run with -console (with no port option) and then run the disconnect command you will get the following stack trace in the log: java.lang.IllegalStateException: The service has been unregistered at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java:209) at org.eclipse.osgi.framework.internal.core.ConsoleManager.stopConsole(ConsoleManager.java:162) at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:412) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:198) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:331) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
Should fix in 3.6.1.
I got this exception in N20100620-2000 during a normal shutdown. Looks like it's not just a log entry, but interrupts the normal shutdown. At least the CVS plug-in did not shut down properly, and I lost all the newly-created change sets from that session (bug 98299). I could not reproduce with N20100627-2000, so it looks like this bug is also timing-dependent.
I launch with -clean -consolelog -showlocation -console -debug. The workbench was up for several days, and I did a lot of different things with this instance (e.g. traced it with YourKit). I don't think I've interacted with the console in other ways than pressing Ctrl+Break.
Created attachment 172907 [details] patch (In reply to comment #3) > I launch with -clean -consolelog -showlocation -console -debug. The workbench > was up for several days, and I did a lot of different things with this instance > (e.g. traced it with YourKit). I don't think I've interacted with the console > in other ways than pressing Ctrl+Break. Was the osgi> console still functional after pressing Ctrl-Break? I suspect the console gets disconnected similar to if you ran the disconnect command. This would explain the exception on shutdown. You are correct, this exception would prevent the proper shutdown of the framework. This patch protects against this.
Patch released to HEAD and to 3.6.1.
(In reply to comment #4) > Was the osgi> console still functional after pressing Ctrl-Break? Indeed, osgi> console is dead after Ctrl+Break, and after that, the exception is thrown on shutdown.
