You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Pascal Alberty <pa...@albertyorban.be> on 2006/10/09 10:01:45 UTC
Waiting for monitor entry & waiting to lock with ehcache
Hi all,
our web application which is an add server (Java 1.5, Apache2 worker
mpm, Tomcat 5, mod_jk, on Debian) is using ehcache 1.2.3 to cache
data.
All was ok since we deploy a new feature which is occasionnaly cpu
consuming. This feature slow down the server for few seconds. After
this slow down, Tomcat stay at 100% CPU and Apache then is overloaded.
By dumping the JVM, I can observed many (around 200) threads waiting
for monitor and waiting for lock:
"TP-Processor91" daemon prio=1 tid=0x8a8e8b48 nid=0x1c05 waiting for
monitor entry [0x88e12000..0x88e130c0]
at net.sf.ehcache.Cache.get(Cache.java:653)
- waiting to lock <0x91607ce0> (a net.sf.ehcache.Cache)
at net.sf.ehcache.Cache.get(Cache.java:631)
...
This occurs (only) each time I use this cpu consuming feature.
Any idea ?
Thanks
--
Pascal Alberty
http://pascal.albertyorban.be
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Waiting for monitor entry & waiting to lock with ehcache
Posted by Pascal Alberty <pa...@albertyorban.be>.
On 10/9/06, Leon Rosenberg <ro...@googlemail.com> wrote:
> Hello Pascal,
>
> I think you should ask your question in the ehcache support list,
> since your stacktrace shows that the problem is in their code.
>
> regards
> Leon
Already asked on ehcache sourceforge forum ... thanks :)
--
Pascal Alberty
http://pascal.albertyorban.be
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Waiting for monitor entry & waiting to lock with ehcache
Posted by Leon Rosenberg <ro...@googlemail.com>.
Hello Pascal,
I think you should ask your question in the ehcache support list,
since your stacktrace shows that the problem is in their code.
regards
Leon
On 10/9/06, Pascal Alberty <pa...@albertyorban.be> wrote:
> Hi all,
> our web application which is an add server (Java 1.5, Apache2 worker
> mpm, Tomcat 5, mod_jk, on Debian) is using ehcache 1.2.3 to cache
> data.
>
> All was ok since we deploy a new feature which is occasionnaly cpu
> consuming. This feature slow down the server for few seconds. After
> this slow down, Tomcat stay at 100% CPU and Apache then is overloaded.
>
> By dumping the JVM, I can observed many (around 200) threads waiting
> for monitor and waiting for lock:
>
> "TP-Processor91" daemon prio=1 tid=0x8a8e8b48 nid=0x1c05 waiting for
> monitor entry [0x88e12000..0x88e130c0]
> at net.sf.ehcache.Cache.get(Cache.java:653)
> - waiting to lock <0x91607ce0> (a net.sf.ehcache.Cache)
> at net.sf.ehcache.Cache.get(Cache.java:631)
> ...
>
> This occurs (only) each time I use this cpu consuming feature.
>
> Any idea ?
>
> Thanks
>
> --
> Pascal Alberty
> http://pascal.albertyorban.be
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org