Hey Vinay,
 
There is no way to track cache hits, but there is the possibility to track
cache misses (and almost every other cache activity). You have to set the
BeanCacheJMSMonitoringEnabled flag to true in the container factory MBean
(jboss.jcml), and then write a client that listen for the wanted messages on
the "beancache" topic.
See the 2 jars in dist/bin (sources are included) for monitoring the cache
using JMX and/or JMS (beware that may be out of date, especially the JMS
one, because of topic name changes). See also the code in
AbstractInstanceCache and LRUEnterpriseContextCachePolicy for JMS messages
sent on cache activity.
 
Hope helped,
 
Simon

-----Original Message-----
From: K.V. Vinay Menon [mailto:[EMAIL PROTECTED]]
Sent: luned� 4 giugno 2001 13:07
To: User @ JBoss; Dev @ JBoss
Subject: [JBoss-dev] Logging Cache Hits


Hi,
     Does anyone know how to turn on cache hit tracking in JBoss without
recompiling the code!? Is this possible? I am trying to stress JBoss to
about as far as it can get [it has not yet fallen over!!! ] but the time for
queries seem a bit odd. I have large intial retrieval times and then they
fall off [as expected I guess dues to cache hits - want to confirm this
though]. But I do get spikes in the middle [probably because the number of
beans has reached a stage where passivation kicks in]. What I'd like to know
is whether successive queries actually hit the database or work [as
promised] by hitting the cache even under very high loads. I am testing with
about 10000 client threads hitting the application server any where between
10milliseconds to about 1000 milliseconds on a huge Tru64 box. The queries
could return 1,15,150,1250 records depending on the type of client. The
underlying table has about half a million records and is an Oracle 8i
database. 
 
Regards,
 
Vinay


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to