Community
Participate
Working Groups
Build Identifier: 3.6.0.v20100517 We're using Equinox as our OSGi container. At times, when running with -console flag, and we shutdown our product we get one of the two stack traces (will atttach stack traces). It seems like there's a race in the way ConsoleManager and ConsoleSession interact with each other, and causes it to try to unregister the service more than once. People have seen this more often when running our product in the background (but still with -console) Reproducible: Sometimes Steps to Reproduce: 1. Start equinox, pass in -console 2. Let start-up complete, do stuff 3. Shutdown
Created attachment 207057 [details] shows the stack trace of the exception thrown and the stack trace of how the console is closed in ConsoleSession
The top stack trace is what we get as we try to shutdown our product running in background with -console. Why anyone would want to do that is a good question since you cant read stdin in this case. But people are doing it. The bottom stack trace is how we see the console being shut down almost immediately after start, in background, probably precisely because you cant read stdin in this case. A possible fix is to set builtinSession field of ConsoleManager to null in this case.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
