NetBeans 3.6 (Beta and RC 1): When debugging a
J2EE application within a Tomcat, the debugging
is enabled too late, so the start process of the
Tomcat server, including the loading of server
classes, predefined modules or extenssions etc.
cannot be debugged. All breakpoints are ignored
during the start process. Just after the
deployment process is finished, the debugging is
enabled and IDE steps into the break points as
With NetBeans 3.5x it is possible to debug the
start of Tomcat 4.x.
Well, in 3.5 it worked only with a luck - IDE was trying to attach to
the server in some increasing time intervals, so some code could have
been easily missed during the start, too. More, the approach lead to
connection errors if tomcat has been starting longer than we expected.
So, in promoB (3.6) we are waiting for the server to start first as
we don't have an option of listening connectors yet.
Listening connectors support will be added in promoD, and we'll use
them to be able to fulfill your request and handle debugging of server
Please, could You tell, what is the target "promo-D" of NetBeans?
The Promo-D is a code name for the next netbeans release. It is a
direct successor of netbeans 3.6 (Promo-B) and its version will be
very likely 4.0.
this is not a defining feature
corner case, decreasing priority to P3 (approved by QE).
*** Issue 70538 has been marked as a duplicate of this issue. ***
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.
Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss