Community
Participate
Working Groups
I've been trying to figure out a vexing problem in JBE, the Jazz Build Engine, a command-line OSGi app. Several people have reported that, sometimes, arguments they've specified on the command line are ignored. TR> sudo BUILD_SYSTEM_DIR/jazz/buildsystem/buildengine/eclipse/jbe -repository [myrepository] -userId rtimothy -pass [mypass] -vm /opt/ibm/java2-i386-50/bin/java -engineId rbf-wica-3.tivlab.austin.ibm.com and it keeps telling me: CRRTC3501E: Missing required argument "-userId". The command line processing logic in JBE is dead simple, and I've traced through it several times and can't see how an argument could get ignored. While looking into this, I noticed that org.eclipse.equinox.internal.app.CommandLineArgs is not thread-safe, yet is used by multiple threads. Its processCommandLine method gets called on one thread, then getApplicationArgs() gets called from another. For more details, see the Jazz work item: https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/123796 I don't think this would explain the original problem, though, since I'd expect either the array or its entries to be null if it was a threading problem, which would cause our code to fail with an NPE since we don't actually check for null.
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.
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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.
