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 116547 - external shutdown and the HTTP Monitor
Summary: external shutdown and the HTTP Monitor
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: HTTP Monitor (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: issues@javaee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-24 15:53 UTC by Vince Kraemer
Modified: 2009-12-21 06:19 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 Vince Kraemer 2007-09-24 15:53:22 UTC 
If the user starts the server with the IDE and then shuts it down with the command line, the code to remove the HTTP
monitoring never fires...  Later on the server log can get buried in warning messages from HTTP monitoring.
Comment 1 Vince Kraemer 2007-09-24 15:59:11 UTC 
more details in thread: http://forums.java.net/jive/thread.jspa?threadID=31083&tstart=0
Comment 2 Vince Kraemer 2007-09-25 19:25:45 UTC 
The best fix for this is in the HTTP monitor code. Repeating the same failure message unacceptable for something that
can get left "on" if the IDE crashes.  It was designed for the embedded Tomcat instance and then stretched to fit the AS
case... In the case of Tomcat, the embedded instance doesn't have as much admin exposure as the AS does.... Folks aren't
as likely to start/stop the embedded TC instance from outside NetBeans....
Comment 3 Vince Kraemer 2007-09-25 19:28:51 UTC 
applying changes to the plugin would be a hack to cover for the limitations of the monitoring implementation.
Comment 4 Quality Engineering 2009-12-21 06:19:57 UTC 
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. 

We apologize for any inconvenience.


Thank you.
The NetBeans Team