This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
when using Netbeans Platform to create my own application, sometimes (1 out of 10 tries), application won't start (run) here are a few last lines in netbeans IDE console: Generating information for Auto Update... run: run.run: Unrecognized option --test-userdir-lock-with-invalid-arg Result: 170 after that run fails
now it happens after modules were loaded.. - with the same error code I am sorry, but I cannot provide any steps to reproduce, because it happens randomly and ... well I would think that running app is a normal (bug-free) process however, I would be glad to provide any information to solve this issue
This fake option is passed by the IDE when you try to run the app and it is already running, or it was forcibly terminated before and left behind its lock file. In the former case the attempted launch should return error codes 2 or 50346 and the Ant console should print "The application is already running within the test user directory. You must shut it down before trying to run it again." In the latter case the app should start up after a few moments when no previous instance responds to its ping (but currently you need to do a clean build first). Never heard of status code 170. You did not say what version of the NB IDE or Platform you were using.
sorry: I am using NB 7.1 as IDE and Platform as well
there are few other guys with this problem: http://forums.netbeans.org/viewtopic.php?p=123459 mKutscheid points out, that this "error code 170" problem occures when application is forced stopped by "red stop button" (i.e. netbeans platform application is not properly closed)
Created attachment 115483 [details] Example log file for "Result: 170" This is an error log, taken from a debug run with NetBeans 7.1 that resulted in "Result: 170"
The IDE should use the same mechanism as ./org/netbeans/nbbuild/IsLocked.java and common.xml is using to detect whether the application is really running or not.
*** Bug 211004 has been marked as a duplicate of this bug. ***
core-main #48544616eb4b
The IsLockable Ant condition seems to work fine, so I am glad the apisupport.project also move in this direction.
Integrated into 'main-golden', will be available in build *201204250400* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/48544616eb4b User: Jesse Glick <jglick@netbeans.org> Log: #207530: error during start Removing --test-userdir-lock-with-invalid-arg mechanism for testing liveness of target platform. Instead just checking whether $userdir/lock can be locked by the IDE process.