Unable to passivate due to ctx lock in JBoss-4.0.4GA

[syedtaj]

Hi,

We are having loads of these errors in the logs in production after porting to JBoss4.0.4GA from JBoss3.2.3 :-

2007-07-17 21:40:56,580 61910688 WARN [org.jboss.ejb.plugins.AbstractInstanceCache] (Thread-37:) Unable to passivate due to ctx lock, id=192.168.128.105:1099:f48gb6cb-umb
2007-07-17 21:40:56,580 61910688 WARN [org.jboss.ejb.plugins.AbstractInstanceCache] (Thread-37:) Unable to passivate due to ctx lock, id=192.168.128.105:1099:f48fdejr-ukx
2007-07-17 21:40:56,580 61910688 WARN [org.jboss.ejb.plugins.AbstractInstanceCache] (Thread-37:) Unable to passivate due to ctx lock, id=192.168.128.105:1099:f48fdenp-ukz

Loads of them.

These are coming mostly after the afterCompletion() of the SFSB is called.

Is it related to the following JBAS-979:-

http://jira.jboss.com/jira/browse/JBAS-979

But the above had been fixed in Jboss4.0.4GA and I am using the same.

And once these start coming, the system becomes quite slow.

Can anyone provide me any pointers or direct me to anything specific.

[syedtaj]

This topic suggests that this is a warning that will still come for SFSB - Stateful session beans.

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=81523

However is this error anyways related to slowness.

And why does the error occur? Is it because when the cache is attempting to flush, it is unable to?

Any light will be great.
[/url]

[syedtaj]

Just a correction to my earlier message.

I understand it is not an error, just a warn - but does hundreds of messages like this indicate a problem that we need to investigate?