Closed GoogleCodeExporter closed 9 years ago
GoogleCodeExporter
commented
9 years ago Since it works with JBoss 5, and not with JBoss 4.2, it seems to be a JBoss
issue and not a javamelody issue.
And JBoss 4.2 is old and should probably not be officially supported anymore.
Given both, it's won't fix here.
Note that you can still continue to use the monitoring without adding the
SessionListener.Original comment by evernat@free.fr on 13 Aug 2014 at 8:11
GoogleCodeExporter
commented
9 years ago Thanks a lot for the info evernat@free.fr! one question - how can we monitor
without adding the session listener in the web.xml?Original comment by ravi0...@gmail.com on 13 Aug 2014 at 8:25
GoogleCodeExporter
commented
9 years ago Just use the MonitorinFilter in web.xml like you already have:
<filter>
<filter-name>monitoring</filter-name>
<filter-class>net.bull.javamelody.MonitoringFilter</filter-class>
<init-param>
<param-name>allowed-addr-pattern</param-name>
<param-value>10\.8\..*|127.0.0.1</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>monitoring</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
(allowed-addr-pattern is copied here like you have written above)Original comment by evernat@free.fr on 13 Aug 2014 at 8:42
Original issue reported on code.google.com by
ravi0...@gmail.comon 13 Aug 2014 at 4:58