[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-659) SFSB throws exception with second passivation

[Ben Wang (JIRA)]

     [ http://jira.jboss.com/jira/browse/EJBTHREE-659?page=all ]

Ben Wang resolved EJBTHREE-659.
-------------------------------

    Resolution: Done

I have fixed this in 4.0 branch and will port it to head soon.

> SFSB throws exception with second passivation
> ---------------------------------------------
>
>                 Key: EJBTHREE-659
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-659
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC8 - FD
>            Reporter: Ben Wang
>         Assigned To: Ben Wang
>             Fix For: EJB 3.0 RC9 - FD
>
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> I have created a test case to illustrate this for both SimpleStatefulCache and StatefulTreeCache, NestedBeanUnitTestCase (cache and clusteredsession). Basically, if we do this:
> bean.getXXX
> sleep(10000); // to passivate
> bean.getXXX; // to acitvate
> sleep(10000); // to passivate again
> This will produce:
> 2006-07-24 04:46:59,358 ERROR [org.jboss.ejb3.cache.simple.SimpleStatefulCache] problem passivation thread^M
> javax.ejb.EJBException: Could not passivate; failed to save state^M
>         at org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager.passivateSession(StatefulSessionFilePersistenceManager.java:363)^M
>         at org.jboss.ejb3.cache.simple.SimpleStatefulCache.passivate(SimpleStatefulCache.java:196)^M
>         at org.jboss.ejb3.cache.simple.SimpleStatefulCache$SessionTimeoutTask.run(SimpleStatefulCache.java:129)^M
> Caused by: java.lang.NullPointerException^M
>         at org.jboss.serial.util.StringUtil.calculateUTFSize(StringUtil.java:319)^M
>         at org.jboss.serial.util.StringUtil.saveString(StringUtil.java:63)^M
>         at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput.writeUTF(DataContainer.java:265)^M
>         at org.jboss.ejb3.stateful.StatefulBeanContextReference.writeExternal(StatefulBeanContextReference.java:65)^M
>         at org.jboss.serial.persister.ExternalizePersister.writeData(ExternalizePersister.java:58)^M
>         at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:275)^M
>         at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput.writeObject(DataContainer.java:197)^M
>         at org.jboss.serial.io.JBossObjectOutputStream.writeObjectOverride(JBossObjectOutputStream.java:181)^M
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:287)^M
>         at org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager.passivateSession(StatefulSessionFilePersistenceManager.java:347)^M
>         ... 2 more^M
> This is caused by a bug from ProxiedStatefuleBeanContext serialization where we dont serialiaze parentRef if it is not null.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira