[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-612) Nested bean during repeated failover throw NPE

[Ben Wang (JIRA)]

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

Ben Wang resolved EJBTHREE-612.
-------------------------------

    Resolution: Done

> Nested bean during repeated failover throw NPE
> ----------------------------------------------
>
>                 Key: EJBTHREE-612
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-612
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: Clustering
>            Reporter: Ben Wang
>         Assigned To: Ben Wang
>             Fix For: EJB 3.0 RC9 - FD
>
>
> I have encountered this during writing more complete unit testing for sfsb clustering. The test case is:
> org.jboss.ejb3.test.clusteredsession.unit.testStatefulBeanCounterFailover
> Here is how to reproduce it:
> Create a ParentBean and NestedBean for nested sfsb case. Hit node1, failover to node2, and execute will produce the following exception:
> Caused by: java.lang.NullPointerException^M
>         at org.jboss.ejb3.stateful.StatefulBeanContextReference.<init>(StatefulBeanContextReference.java:51)^M
>         at org.jboss.ejb3.stateful.ProxiedStatefulBeanContext.writeExternal(ProxiedStatefulBeanContext.java:92)^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.JBossObjectOutputStreamSharedTree.writeObjectOverride(JBossObjectOutputStreamSharedTree.java:59)^M
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:287)^M
>         at org.jboss.cache.marshall.EnhancedTreeCacheMarshaller.marshallObject(EnhancedTreeCacheMarshaller.java:258)^M
> @                                                                               
> Note that this error has already existed before any refactoring is in place.

-- 
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