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.

Bug 211004 - Frequent "exec returned: 170" during debug start
Summary: Frequent "exec returned: 170" during debug start
Status: RESOLVED DUPLICATE of bug 207530
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 7.2
Hardware: PC Solaris
: P3 normal (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-11 12:25 UTC by Egor Ushakov
Modified: 2012-11-01 10:25 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Egor Ushakov 2012-04-11 12:25:59 UTC 
From time to time I see this error and NB module debug start fails:
/cnd-main/nbbuild/templates/projectized.xml:379: The following error occurred while executing this line:
/cnd-main/nbbuild/build.xml:916: The following error occurred while executing this line:
/cnd-main/nbbuild/build.xml:990: exec returned: 170

usually it helps just to restart the debug session
Comment 1 Jesse Glick 2012-04-11 15:03:09 UTC 
This is probably coming from CLIHandler, but I have no idea what a 170 exit code would mean.
Comment 2 Jesse Glick 2012-04-11 15:04:13 UTC 
I seem to recall some other (unreproducible) report mentioning exit code 170 but I cannot find it now.
Comment 3 Egor Ushakov 2012-04-11 15:12:55 UTC 
In our environment it is reproduced almost every other time, I could enable any logging required to provide more information
Comment 4 Libor Fischmeistr 2012-04-12 12:15:42 UTC 
I have managed to reproduce this bug/nobug. The problem is when you kill the debugged instance of NB using finish button (Shift-F5) the application doesn't finish properly and the lock file in userdir isn't deleted. When you try to debug next time, the lock file still exists and you get 170 exit code and the lock file is deleted. Next time you run debug everything works and NB will start.

This behavior is described in issue 141069.
Comment 5 Jesse Glick 2012-04-23 14:56:45 UTC 
I am still unable to reproduce the 170 exit code, and still have no clue what code might refer to "170" (this exit status does not appear in any part of NB sources I have looked in). Anyway I plan to look into rewriting the mechanism that used to be able to detect a stale lock (left behind by a crashed JVM) but which might no longer be functional.

*** This bug has been marked as a duplicate of bug 207530 ***
Comment 6 seriyvolk 2012-11-01 10:25:28 UTC 
(In reply to comment #5)
> I am still unable to reproduce the 170 exit code, and still have no clue what
> code might refer to "170" (this exit status does not appear in any part of NB
> sources I have looked in). Anyway I plan to look into rewriting the mechanism
> that used to be able to detect a stale lock (left behind by a crashed JVM) but
> which might no longer be functional.

I had same error, but then I've removed next option from propject.properties

run.args=-J-ea -J-Xms24m -J-Xmx1024m -J-Djava.net.preferIPv4Stack=true -Dsun.java2d.opengl=true  -J-Xverify:none -J-Duser.language=en -J-Duser.country=EN

my application launched without error.

Application was originally created at 6.8 version and reopened in 7.2.