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.
[ BUILD # : 200808210201 ] [ JDK VERSION : 1.6.0_06 ] Hi, In about 99% of the cases I am profiling my J2EE app the build fails (see below output) but the profiler is running and I actually can profile the application. This seems incorrect. I haven't found an option anywhere to extend the timeout for the build to wait for the profiler to be started either. Iwan profile-j2ee: start-profiled-server-extraargs: Server is ready waiting for profiler to attach... Profiler attached, waiting for the server to start up... C:\Iwan\SticktailGames\projects\FriendOrFoe\backend\IFFServer\nbprojec t\profiler-build-impl.xml:19: The following error occurred while executing this line: C:\Iwan\SticktailGames\projects\FriendOrFoe\backend\IFFServer\nbprojec t\profiler-build-impl.xml:30: Starting of server in profile mode timed-out after 300 secs. BUILD FAILED (total time: 5 minutes 32 seconds)
I think you can use -J-Dprofiler.agent.startup.timeout to control this timeout. See http://blogs.sun.com/nbprofiler/entry/tweaking_profiler_timeouts for detailed description. I hope that helps and next time please use mailing list for this type of questions.
I think it is a bug, either the build-profiler combination is not working correctly together, or the documentation is lacking this information at the least. Especially considering you're referring to a blog entry that supposedly has the answer. At the least the info from the blog entry could be outputted in the result from the build as to hint that the timeout can be extended. Iwan
The default timeout should be long enough. In rare situation this timeout is not enough so we added system property to allow to extend it. Does your application server start for more than 300 seconds? You did not write if the extending timeout helped or not and if this is a bug report you did not provide steps how to reproduce the problem.
From the lack of response it seems the problem was solved by the longer timeout via command line option -> resolving as worksforme. If it was not then please reopen the issue and add the requested info.