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 98350 - Wrong Tomcat status when debugger is attached manually
Summary: Wrong Tomcat status when debugger is attached manually
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Infrastructure (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-20 15:15 UTC by Martin Schovanek
Modified: 2007-09-10 17:49 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 Martin Schovanek 2007-03-20 15:15:05 UTC 
[#200703181900, jdk1.5.0]

to reproduce:
-------------
1) start Tomcat in debug mode
2) choose 'Run > Attach Debugger'
3) choose 'Run > Pause'
4) refresh the Tomcat node
ERROR1: Tomcat node looks like stopped (in fact is paused)
5) choose 'Run > Continue'
6) refresh the Tomcat node
ERROR2: Tomcat node looks like running (should display running in debug mode status)
Comment 1 Sherold Dev 2007-08-14 09:05:54 UTC 
The issue is still reproducible, tm -> 6.0
Comment 2 Petr Hejl 2007-09-10 16:09:48 UTC 
This is not just the tomcat issue. It is bug in server code - check for debugging session is very fragile to different
hostnames.
Comment 3 Petr Hejl 2007-09-10 17:49:52 UTC 
Fixed. Was caused by comparing hostnames. Improved hostname equality resolution.

Checking in src/org/netbeans/modules/j2ee/deployment/impl/ServerInstance.java;
/cvs/j2eeserver/src/org/netbeans/modules/j2ee/deployment/impl/ServerInstance.java,v  <--  ServerInstance.java
new revision: 1.85; previous revision: 1.84
done