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 41201 - tomcat jsp debugging does not start with jdk1.5
Summary: tomcat jsp debugging does not start with jdk1.5
Status: VERIFIED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 3.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: issues@debugger
URL:
Keywords: JDK_SPECIFIC
Depends on:
Blocks:
 
Reported: 2004-03-22 16:01 UTC by radam
Modified: 2005-07-11 15:24 UTC (History)
0 users

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 radam 2004-03-22 16:01:12 UTC 
Starting the integrated tomcat 5 in the 
debugmode in netbeans with jdk1.5 beta (tiger) 
fails with the message:
start debugger failed: null
This problem appears with a recent debian 
installation and a redhat 8 installation. The 
problem disappears when using an older jdk 
(1.4.1).
Comment 1 Martin Grebac 2004-03-22 16:34:35 UTC 
This is not a 3.6 relevant issue.
Comment 2 radam 2004-03-22 19:06:52 UTC 
There is another big difference between the use of jdk14.x and jdk1.5 
when running the Netbeans IDE 3.6rc1. With jdk1.4.x the netbeans ide 
uses only one process but with jdk1.5 a large amount of processes 
(>10).
Comment 3 Martin Grebac 2004-03-26 11:58:33 UTC 
This is actually a bug in jpda dbg. The NPE is in
RemoteDebuggerInfo(hostname, port) constructor.
Comment 4 Maros Sandor 2004-03-29 10:11:39 UTC 
A modification of Java 1.5 JDI behavior which should be taken into 
account on our side. Requires simple and straightforward modification 
of 5 classes that deal with this API.
Comment 5 L Martinek 2004-03-29 13:42:38 UTC 
I tried it with jdk1.5 Beta 1 (b32c) and it really doesn't work.
However, with last internal build (b43) it works.
Comment 6 Jan Jancura 2004-03-29 14:50:09 UTC 
reviewed - looks good!
Comment 7 Maros Sandor 2004-03-30 14:44:22 UTC 
Fixed by checking for possible null Transport in a JDI Connector.

/cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/Launcher.java
,v  <--  Launcher.java
new revision: 1.18.2.1; previous revision: 1.18
/cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/RemoteDebugge
rInfo.java,v  <--  RemoteDebuggerInfo.java
new revision: 1.17.152.1; previous revision: 1.17
/cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/ListeningDebu
ggerInfo.java,v  <--  ListeningDebuggerInfo.java
new revision: 1.2.12.1; previous revision: 1.2
/cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/util/Utils.ja
va,v  <--  Utils.java
new revision: 1.15.90.1; previous revision: 1.15
Comment 8 Max Sauer 2005-07-11 15:24:39 UTC 
This feature works fine now. Verified in nbdev200507061800.