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.
Using dev. builds of NB and the Profiler from 2005-10-24 on JDK5U5, WinXP. Using the exercise2 project that is included with the Profiler Tutorial (http://www.netbeans.org/kb/articles/nb-profiler-tutor-8.html), I tried the following: 1. Start NB. 2. Clean and build the project 3. Run the project. 4. After the browser display's the application's page, switch back to NB. 5. Choose Profile > Profile Main Project An error message was displayed that said Tomcat could not be started because port 8084 was already in use. I was eventually able to get the Profiler to work, but only after manually stopping Tomcat over in the Runtime tab. This seems like a regression - in NB 4.1 didn't this result in the Profiler being smart enough to figure out that it should stop Tomcat and then restart it in profiling mode? If this is *not* a regression, then please change this IZ to be an ENHANCEMENT, thanks.
In NB 5.0 new API was created and is used to profile web applications. The problem reported is a known bug in nbstartprofiledserver ant task from this API, which doesn't correcty stop the server if running before profiling session. There is already filed Issue 66716 about it. The only workaround for now is to stop the server manually from Runtime tab before starting new profiling session. *** This issue has been marked as a duplicate of 66716 ***
Verification of old issues.
Closing old issues
Reverting to original Target Milestone value changed by mistake. Sorry for inconvenience.