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 139653 - http monitoring is hard to turn off
Summary: http monitoring is hard to turn off
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 6.x
Hardware: PC Solaris
: P3 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-10 23:15 UTC by Vince Kraemer
Modified: 2009-02-19 23:03 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vince Kraemer 2008-07-10 23:15:18 UTC
Once you enable http monitoring, it is hard to turn it off completely.

Details below.

the monitor is implemented as a filter in the jar file org-netbeans-modules-web-httpmonitor.jar.

when the user enables the http monitor and starts the server from inside the IDE...
 the jar is put in the domain's lib directory... so the code for the monitor becomes available.
 the default-web.xml file is altered so that requests WILL pass through the filter to become monitored, if they are
deployed AFTER the edits are made.

When an app is deployed... the default-web.xml is mixed into the deployment configuration of the app...
 requests to that app will try to contact the IDE with monitoring data.

When the user disables http monitoring...
 the filter and mapping info for the MonitorFilter are removed from default-web.xml

And the user would hope that the monitor was really disabled... it is not.

The monitor filter is still configured to be triggered by any and all of the apps deployed between the time the user
enabled the monitor and disabled the monitor in the IDE...

So, disabling the monitor is not enough.  the user must redeploy all apps that have has the monitor filter "mixed in".

So.. how can the user tell that the monitor is not mixed into any of the web.xml files associated with their install?

If you find the string MonitorFilter in files under <domain-root>/generated/xml/j2ee-* then you know that there are
still apps that will try to contact the IDE with monitoring data.
Comment 1 Vince Kraemer 2008-07-21 00:03:52 UTC
It looks like Tomcat does not run into this problem.  Have query on GF mailing lists for additional info on a different
approach.
Comment 2 Vince Kraemer 2008-07-21 21:19:25 UTC
the gf team had a fix for this... but it seems to have regressed...
Comment 3 Vince Kraemer 2008-07-28 18:44:54 UTC
gf issue for x-ref: https://glassfish.dev.java.net/issues/show_bug.cgi?id=3844
Comment 4 Vince Kraemer 2008-10-25 04:55:46 UTC
I think we just need to verify that the server works as 'expected' to close this issue.  this should happen for v2 and
v3, soon. 2008/10/27
Comment 5 Vince Kraemer 2008-11-14 21:49:05 UTC
the GF fix did not pass testing.
Comment 6 Vince Kraemer 2008-12-06 00:28:48 UTC
I just tested v2.1 b60a and the monitoring seems to be much easier to turn off.  The server needs to be restarted, but
the applications do not need to be redeployed.

Marking as fixed... though users will need to use GF v2.1 to see this.  I doubt the fix will be backported into a v2
update release.