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 98386 - IDE doesn't determine Tomcat's state correct
Summary: IDE doesn't determine Tomcat's state correct
Status: RESOLVED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Petr Hejl
URL:
Keywords:
: 102636 102656 191938 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-03-20 18:13 UTC by Roman Mostyka
Modified: 2010-11-15 08:38 UTC (History)
2 users (show)

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 Roman Mostyka 2007-03-20 18:13:06 UTC 
1. I added Tomcat 5.0.28, Tomcat 5.5.17.
2. Start Tomcat !!!5.5.23!!! outside IDE.

Result: Added Tomcat 5.0.28 and Tomcat 5.5.17 are shown as running. It is
possible to expand their nodes.

OR

1. I added Tomcat 5.0.28, Tomcat 5.5.17, Tomcat 5.5.23.
2. Start Tomcat 5.5.23 from IDE.

Result: Tomcat 5.5.23 is shown as running, Tomcat 5.0.28 and Tomcat 5.5.17
aren't. But after click refresh on Tomcat 5.0.28 and Tomcat 5.5.17, they are
also shown as running.
Comment 1 Sherold Dev 2007-04-26 16:23:45 UTC 
*** Issue 102636 has been marked as a duplicate of this issue. ***
Comment 2 Sherold Dev 2007-04-26 16:36:32 UTC 
We might be able to improve detection of running status among different versions
of tomcat based on the http response headers. Unfortunately, we won't be able to
distinguish two Tomcat instances of the same minor version.

Setting TM -> 6.0
Comment 3 Petr Hejl 2007-08-08 11:30:07 UTC 
Unfortunately, there is no way how to get the tomcat version from http response. Other possibilities would be
complicated and not reliable.
Comment 4 Sherold Dev 2007-08-09 14:13:08 UTC 
*** Issue 102656 has been marked as a duplicate of this issue. ***
Comment 5 Petr Hejl 2010-11-15 08:38:07 UTC 
*** Bug 191938 has been marked as a duplicate of this bug. ***