Unable to passivate due to ctx lock IS GONE

aloubyansky Apr 21, 2006 12:02 PM

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.

1. Re: Unable to passivate due to ctx lock IS GONE

vigong May 30, 2006 1:55 PM (in response to aloubyansky)

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
Actions
2. Re: Unable to passivate due to ctx lock IS GONE

vigong May 30, 2006 1:57 PM (in response to aloubyansky)

forgot to tell you, i'm using jboss-4.0.3SP1
Actions
3. Re: Unable to passivate due to ctx lock IS GONE

aloubyansky May 30, 2006 5:14 PM (in response to aloubyansky)

You should use user forums for such questions.
The issue is fixed in 4.0.4.GA.
Actions
4. Re: Unable to passivate due to ctx lock IS GONE

oyabun Nov 6, 2006 11:17 AM (in response to aloubyansky)

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

--
Alex
Actions
5. Re: Unable to passivate due to ctx lock IS GONE

aloubyansky Nov 6, 2006 3:44 PM (in response to aloubyansky)

See JBAS-979 for the info.
Actions
6. Re: Unable to passivate due to ctx lock IS GONE

oyabun Nov 7, 2006 3:40 AM (in response to aloubyansky)

Thanks
Actions

Go to original post