NotSerializableException during passivation.

Question

Hi there,
I have a stateful session bean which has only one field. This field
has no problem being serialized (I tested it). Everything works fine
until the session bean in passivated, then I get the exception below.
After looking inside all fields in the wrapping EJB object, there is
one reference ( __WL_bmtx ) of type
weblogic.transaction.internal.ServerTransactionImpl. The value of its
toString() method suggests that it is a transaction that was already
committed and finished (after looking at my log), even before other
transactions took place before passivation.
To explain it better, before the session bean is passivated, it goes
under three or four transactions (during different calls), and the one
that is being referenced is the second one. So, my question: Does
anyone know, why would WebLogic keep a reference to a committed,
closed, unused transaction? What am I doing wrong?
I have logged everything during the processing and have confirmed that
ALL database connections are being closed and de-referenced; all
transactions are committed.
Any suggestions? any place to look at?
I am using Weblogic 7.0 SP1, Tamino XML database, all on Windows 2000.
(Exception:)
<Error during passivation: java.io.NotSerializableException:
weblogic.transaction.internal.ServerTransactionImpl
     at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1143)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:361)
     at java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1822)
     at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:475)
     at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1209)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:361)
     at weblogic.ejb20.swap.PassivationUtils.write(PassivationUtils.java:93)
     at weblogic.ejb20.swap.DiskSwap.write(DiskSwap.java:176)
     at weblogic.ejb20.manager.StatefulSessionManager.swapOut(StatefulSessionManager.java:898)
     at weblogic.ejb20.cache.NRUCache.moveInActiveToFree(NRUCache.java:472)
     at weblogic.ejb20.cache.NRUCache.reclaimNodes(NRUCache.java:500)
     at weblogic.ejb20.cache.NRUCache.getFreeNode(NRUCache.java:239)
     at weblogic.ejb20.cache.NRUCache.put(NRUCache.java:319)
     at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:710)
     at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:745)
     at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:164)
     at com.aker.beans.webdispatcherEJB_qu7z0l_HomeImpl.create(webdispatcherEJB_qu7z0l_HomeImpl.java:96)
     at jsp_servlet._jsp.__componentsmain._jspService(__componentsmain.java:154)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:945)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:332)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:242)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5360)
     at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:721)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3043)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2468)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
Thanks in advance,
-- Juan

Answer 1

Are you spanning one transaction across multiple methods of SFSB?
This is one case, I can assume, the container stores the tx reference in the
bean.
Are you sure by the time the SFSB method call is finished, tx status in not
active
(committed or rolled back whatever but not Status.STATUS_ACTIVE). This is
a case
container stores tx in the bean.
Hope this may provide some pointers. If can reproduce it, please open a
support case otherwise.
Cheers,
..maruthi
"JUAN F. ARJONA" <[email protected]> wrote in message
news:[email protected]...
Hi there,
I have a stateful session bean which has only one field. This field
has no problem being serialized (I tested it). Everything works fine
until the session bean in passivated, then I get the exception below.
After looking inside all fields in the wrapping EJB object, there is
one reference ( __WL_bmtx ) of type
weblogic.transaction.internal.ServerTransactionImpl. The value of its
toString() method suggests that it is a transaction that was already
committed and finished (after looking at my log), even before other
transactions took place before passivation.
To explain it better, before the session bean is passivated, it goes
under three or four transactions (during different calls), and the one
that is being referenced is the second one. So, my question: Does
anyone know, why would WebLogic keep a reference to a committed,
closed, unused transaction? What am I doing wrong?
I have logged everything during the processing and have confirmed that
ALL database connections are being closed and de-referenced; all
transactions are committed.
Any suggestions? any place to look at?
I am using Weblogic 7.0 SP1, Tamino XML database, all on Windows 2000.
(Exception:)
<Error during passivation: java.io.NotSerializableException:
weblogic.transaction.internal.ServerTransactionImpl
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1143)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:361)
atjava.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1822)
atjava.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:475)
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1209)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:361)
at weblogic.ejb20.swap.PassivationUtils.write(PassivationUtils.java:93)
at weblogic.ejb20.swap.DiskSwap.write(DiskSwap.java:176)
atweblogic.ejb20.manager.StatefulSessionManager.swapOut(StatefulSessionManager
.java:898)
at weblogic.ejb20.cache.NRUCache.moveInActiveToFree(NRUCache.java:472)
at weblogic.ejb20.cache.NRUCache.reclaimNodes(NRUCache.java:500)
at weblogic.ejb20.cache.NRUCache.getFreeNode(NRUCache.java:239)
at weblogic.ejb20.cache.NRUCache.put(NRUCache.java:319)
atweblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.
java:710)
atweblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionMa
nager.java:745)
atweblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:164)
atcom.aker.beans.webdispatcherEJB_qu7z0l_HomeImpl.create(webdispatcherEJB_qu7z
0l_HomeImpl.java:96)
atjsp_servlet._jsp.__componentsmain._jspService(__componentsmain.java:154)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
atweblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
tStubImpl.java:945)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:332)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:242)
atweblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(W
ebAppServletContext.java:5360)
atweblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManage
r.java:721)
atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:3043)
atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2468)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
Thanks in advance,
-- Juan