hi there,
in your web.xml include these
*
monitoring
net.bull.javamelody.MonitoringFilter
monitoring
/*
net.bull.javamelody.SessionListener
*
and
*
Just a thought from someone who knows nothing more than the contents of this
thread about the issue.
Would it make sense to only cache classes within a jar? i.e. empty the cache
when moving on to scan the next jar?
Possibly one might get enough performance benefit from intra-jar class
hierarch
Dear all,
Javamelody is supposedly very easy to install for Tomcat but We do
have a webapp using the Struts framework and I can't figure out how to
configure Javamelody or get any error log of what I'm doing wrong. The
web.xml example in the Javamelody is blocking my webapp to work (we use
Pid * wrote:
>On 14 Apr 2012, at 22:50, Gautam wrote:
>> > minSpareThreads="25"
>> maxSpareThreads="75" enableLookups="true" acceptCount="100"
>> connectionTimeout="2"
>> disableUploadTimeout="true"
>>scheme="https"
>>secure="false"
>>SSLEnabled="true"
>>p