Unable to passivate due to ctx lock IS GONE

[aloubyansky]

This warning is not going to be logged for entity beans any more. It still is for SFSB.
The reasons to remove it was the refactoring done as part of the work on flushCache issue http://jira.jboss.com/jira/browse/JBAS-979

I don't think there should be a warning logged in a case an instance cannot be passivated since such cases seem to be normal situations a user should not worry about. At least after the refactoring.
The following is the page I wrote that decribes these situations and how they are handled now http://wiki.jboss.org/wiki/Wiki.jsp?page=CMPFlushAgeOutStoreNotFlushed

If you think there should be other more specific warning messages logged, let's discuss them.

[vigong]

could you please post an example for commit D configuration,
because i use Standard CMP 2.x EntityBean with cache invalidation with commit D and i got Unable to passivate due to ctx lock warning.

thx

[vigong]

forgot to tell you, i'm using jboss-4.0.3SP1

[aloubyansky]

You should use user forums for such questions.
The issue is fixed in 4.0.4.GA.

[oyabun]

So if it's gone, what product has the fix (cache, server)? And what version?

--
Alex

[aloubyansky]

See JBAS-979 for the info.

[oyabun]

Thanks