----- Original Message -----
From: "Scott Marlow" <smarlow(a)redhat.com>
Sent: Thursday, July 31, 2014 4:06:24 PM
Subject: Re: [wildfly-dev] We started seeing test failure in
PassivationTestCase.testPassivationMaxSize() which has
passivation max-size=1 and repeated called to two separate beans...
From talking with Paul about this situation, it sounds like we
currently do allow direct passivation of the nested stateful beans,
without passivating the top level bean that might reference it.
Sorry if I wasn't clear, but that's not the case.
All nested beans are always passivated together - they have to be to preserve references
to the same objects (e.g. the XPC).
Up to now, I thought that we always passivated the top level
bean and all referenced beans, as a group. We actually do passivate the
entire group (top level + nested beans), when the top level bean is
passivated but we also allow the nested beans to passivated in an
That's not quite true either. A bean forever belongs to the group into which it was
So, even if a nested bean is invoked directly (rather than via the parent bean) - it would
still passivate as a group along with its other associated beans.
My question at this point is, could we switch to only passivating
level beans? I'm not sure if we know the difference between top-level
and nested beans, which might make this difficult or impossible.
The issue, I think, is when passivation of the group is triggered within the context of
the invocation that uses the bean.
The reason this is happening in this test is because the passivation threshold is lower
than the depth of your nested beans.
When did this test start failing? I suspect it might be related to this commit:
If so, I should have a fix for this shortly.
Let's also keep in mind that this isn't really a real-world scenario, as nobody in
their right mind would ever set their max-size of the SFSB cache to be so small.
So, this is more about getting the test to pass than to fix a functional issue.
On 07/31/2014 11:22 AM, Scott Marlow wrote:
> Just to keep everyone in the loop, it seems like configuring the
> passivation max-size to be less than "one + number of nested beans",
> could be the cause. We are currently configuring the passivation cache
> max-size to be one, which may lead to passivation of the nested bean.
> In the PassivationTestCase test, each top level session bean has a
> nested bean. The top level bean shares the extended persistence context
> with the nested bean.
> If users hit this same failure, they should ensure that max-size is at
> least equal to "1 + number of nested beans referenced from top level
> We will continue to discuss this case on IRC or email and keep you all
> On 07/31/2014 05:52 AM, Tomaž Cerar wrote:
>> For time beeing I have muted and assigned this test failure on brontes
>> to you Scott.
>> This way people wont get bogus PR test failures while you are working on
>> a fix.
>> On Thu, Jul 31, 2014 at 4:18 AM, Scott Marlow <smarlow(a)redhat.com
>> <mailto:email@example.com>> wrote:
>> We started to see what looks like a JPA extended persistence context
>> related error.  is the server.log that shows the exception (see
>> last one near the bottom) that shouldn't be happening on WildFly
>> Also, there are some marshalling errors that I didn't see on
>> (I'm wondering if there is a concurrency error between the bean
>> invocation and passivation/activation when Hibernate throws the
>> "java.lang.IllegalStateException: Cannot serialize a session while
>> connected" error during marshalling as if bean is active).
>> I am able to recreate the failure locally with a modification to the
>> PassivationTestCase.testPassivationMaxSize()  to repeatedly
>> alternative between calls to remote1 + remote2 beans.
>> I don't have this nailed down to the actual cause but it seems like a
>> race condition between passivation/activation and bean invocation
>>  https://www.dropbox.com/s/277pwvxv53dp8vk/server.zip
>> results from more than one test run. If you look at the server.log,
>> probably should go to the end and see the last
>> WFLYJPA0030: Found extended persistence context in SFSB invocation
>> stack but that cannot be used" error
>>  unit test change to loop repeatedly until failure occurs
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org <mailto:firstname.lastname@example.org>
> wildfly-dev mailing list
wildfly-dev mailing list