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 18175 - Servlet debugger fails to start in some case
Summary: Servlet debugger fails to start in some case
Status: CLOSED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: Sun Solaris
: P2 blocker (vote)
Assignee: Damian Frach
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-29 03:14 UTC by Mikhail Romanov
Modified: 2003-07-02 08:32 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mikhail Romanov 2001-11-29 03:14:32 UTC
Bug found in NB3.3 beta 6 (Build 200111280100) with JDK1.3.1
on Solaris 8 / Ultra 10.

Servlet debugger fails to start for the very first time after
restarting the IDE. 

How to reproduce:

1. Start IDE and mount Web module with servlet
2. Toggle breakpoint on some line in the servlet
3. Select servlet node in Explorer and click on Debug->Start
   item in the Main Window. Notice that dialog with the following 
   message appears on screen: "Exception while starting debugger: 
   Cannot connect to remote VM. ...", though Tomcat was started 
   (you can access servlet via browser).
4. Try steps 1-3 again - sometime debugger fails to start for
   several times.
5. However if one executes servlet before starting debugger, 
   it works fine.
Comment 1 Damian Frach 2001-12-04 09:46:15 UTC
investigation:

the bug occurs only: solaris and jdk 1.3
others OSs or solaris and jdk 1.4 are OK

the bug occurs with the Pilsen too

bugfix:

I have not been able to find a bugfix or a bug reason
Comment 2 Damian Frach 2002-01-04 09:26:01 UTC
I am not able to fix it or find a bug reason.
Comment 3 Quality Engineering 2003-07-02 08:25:44 UTC
Resolved for 3.4.x or earlier, no new info since then -> verify.

Comment 4 Quality Engineering 2003-07-02 08:32:16 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.