"Could not deserialize session data" error during sign out

Hello,
I have an application deployed on WLS 8.1, one instance, no clustering. The application EAR contains 1 web module and 2 ejb modules. When I try to sign out(I use Single Sign-On for Multiple Applications - a sign out application deployed separately) I receive the attached error.
Notes: my session is serializable - I did a test that serialize and deserialize the session and I have no errors.
Q: Why does WLS try to deserialize the session data during sign out? I don't use any session persistance/replication.
The error ClassNotFoundException from my point of view is normal: UsersTableModel(from web modile) is not visible from the Application Classloader.
Here is the error:
<> <BEA-100028> <Could not deserialize session data.
java.lang.ClassNotFoundException: xxx.controller.actions.UsersTableModel: This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on all other members of that cluster
     at weblogic.j2ee.ApplicationManager.loadClass(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.ClassLoader;Z)Ljava.lang.Class;(ApplicationManager.java:344)
     at weblogic.j2ee.ApplicationManager.loadClass(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.ClassLoader;)Ljava.lang.Class;(ApplicationManager.java:258)
     at weblogic.j2ee.ApplicationManager.loadClass(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)Ljava.lang.Class;(ApplicationManager.java:253)
     at weblogic.j2ee.ApplicationManager.loadClass(Ljava.lang.String;Ljava.lang.String;)Ljava.lang.Class;(ApplicationManager.java:216)
     at weblogic.common.internal.WLObjectInputStream.resolveClass(Ljava.io.ObjectStreamClass;)Ljava.lang.Class;(WLObjectInputStream.java:48)
     at java.io.ObjectInputStream.readNonProxyDesc(Z)Ljava.io.ObjectStreamClass;(Unknown Source)
     at java.io.ObjectInputStream.readClassDesc(Z)Ljava.io.ObjectStreamClass;(Unknown Source)
     at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown Source)
     at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
     at java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown Source)
     at weblogic.servlet.internal.AttributeWrapper.convertBytesToObject([B)Ljava.lang.Object;(AttributeWrapper.java:173)
     at weblogic.servlet.internal.AttributeWrapper.getObject(Z)Ljava.lang.Object;(AttributeWrapper.java:114)
     at weblogic.servlet.internal.AttributeWrapper.getObject()Ljava.lang.Object;(AttributeWrapper.java:69)
     at weblogic.servlet.internal.session.SessionData.removeAttribute(Ljava.lang.String;Z)Ljava.lang.Object;(SessionData.java:614)
     at weblogic.servlet.internal.session.SessionData.removeAttribute(Ljava.lang.String;)V(SessionData.java:596)
     at weblogic.servlet.internal.session.SessionData.remove()V(SessionData.java:808)
     at weblogic.servlet.internal.session.MemorySessionContext.invalidateSession(Lweblogic.servlet.internal.session.SessionData;)Z(MemorySessionContext.java:69)
     at weblogic.servlet.internal.session.SessionData.invalidate()V(SessionData.java:750)
     at weblogic.servlet.security.ServletAuthentication.invalidateAll(Ljavax.servlet.http.HttpServletRequest;)Z(ServletAuthentication.java:184)
     at xxx.framework.authentication.WebAuthenticationHelper.invalidateSessions(Ljavax.servlet.http.HttpServletRequest;)V(WebAuthenticationHelper.java:574)
     at xxx.framework.authentication.WebAuthenticationHelper.closeSession(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(WebAuthenticationHelper.java:523)
     at xxx.framework.authentication.WebAuthenticationHelper.logout(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(WebAuthenticationHelper.java:250)
     at xxx.yyy.ViewDispatcher.process(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(ViewDispatcher.java:75)
     at xxx.yyy.ViewDispatcher.doGet(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(ViewDispatcher.java:42)
     at javax.servlet.http.HttpServlet.service(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava.lang.Object;(ServletStubImpl.java:996)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Lweblogic.servlet.internal.FilterChainImpl;)V(ServletStubImpl.java:419)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(ServletStubImpl.java:315)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run()Ljava.lang.Object;(WebAppServletContext.java:6452)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(SecurityManager.java:118)
Edited by: user11291053 on 22-Jun-2009 02:52
Edited by: user11291053 on 22-Jun-2009 03:01
Edited by: user11291053 on 23-Jun-2009 01:42

When OptimisticSerialization is turned on, WebLogic server does not serialize-deserialize context and request attributes upon getAttribute(name) when a request gets dispatched across servlet contexts. This means you will need to make sure that the attributes common to Web applications are scoped to a common parent classloader (they are application-scoped) or placed in the system classpath if the two Web applications do not belong to the same application.
When OptimisticSerialization is turned off (which is the default) WebLogic Server does serialize-deserialize context and request attributes upon getAttribute(name) to avoid the possibility of ClassCastExceptions. The value of OptimisticSerialization can also be overridden for specific Web applications by setting the optimistic-serialization value in weblogic.xml.
[http://edocs.bea.com/wls/docs100/ConsoleHelp/pagehelp/Corecoredomaindomainconfigwebapptitle.html]
[http://e-docs.bea.com/wls/docs90/webapp/weblogic_xml.html#1067857]
I hope this helps :)

Similar Messages

"Could not deserialize session data" error during shutdown WLS 6.0SP2

          Hello all,
          I get this Error ("Could not deserialize session data") when shutting down WLS
          6.0 SP2.
          I set the property 'PersistentStoreType' to 'memory' in weblogic.xml to use memory-based
          storage for session data. So WLS should not try to serialize the session and save
          it to disk (and I didn't find any files). I set a breakpoint in the writeObject()/readObject()
          methods and realized that WLS calls writeObject on all in the session saved objects
          and readObject directly afterwards. Here's the stackTrace:
          ObjectOutputStream.writeObject()/ObjectOutputStream.readObject()
          AttributeWrapper.getObject()
          SessionData.removeAttribute()
          SessionData.removeValue()
          SessionData.remove()
          MemorySessionContext.invalidateSession()
          MemorySessionContext.shutDown()
          WebAppServletContext.destroyServlets()
          HttpServer.destroyServlets()
          HttpServer.shutDown()
          WebService.shutDown()
          ServerServiceList.shutDown()
          T3srvr.die()
          T3srvr.waitForDeath()
          T3srvr.run()
          Server.main()
          I do save some objects which are not Serializable in the session. I understand
          that session data can be made persistent in a file/jdbc and then the objects must
          be Serializable but not when saving the session data in memory.
          Why is WLS trying to Serialize the Session Data and how can I switch it off ?
          The Documentation says that it is allowed to store any object in the sessio, as
          long as it is not persistet.
          Thanks for your help,
          Oliver
          [weblogic.xml]


          Hello Oliver & All-
          Did anyone ever make any progress with this question, or come up with an answer?
          I've found similar behavior when properly shuting down a WLS server with this command:
          java -classpath $CLASSPATH weblogic.Admin -url t3://localhost:7001 -username <user>
          -password <passwd> SHUTDOWN
          TIA.
          --oliver.
          "Oliver Seiler" <[email protected]> wrote:
          >
          >Hello all,
          >
          >I get this Error ("Could not deserialize session data") when shutting down
          >WLS
          >6.0 SP2.
          >I set the property 'PersistentStoreType' to 'memory' in weblogic.xml to
          >use memory-based
          >storage for session data. So WLS should not try to serialize the session
          >and save
          >it to disk (and I didn't find any files). I set a breakpoint in the writeObject()/readObject()
          >methods and realized that WLS calls writeObject on all in the session saved
          >objects
          >and readObject directly afterwards. Here's the stackTrace:
          >
          >ObjectOutputStream.writeObject()/ObjectOutputStream.readObject()
          >AttributeWrapper.getObject()
          >SessionData.removeAttribute()
          >SessionData.removeValue()
          >SessionData.remove()
          >MemorySessionContext.invalidateSession()
          >MemorySessionContext.shutDown()
          >WebAppServletContext.destroyServlets()
          >HttpServer.destroyServlets()
          >HttpServer.shutDown()
          >WebService.shutDown()
          >ServerServiceList.shutDown()
          >T3srvr.die()
          >T3srvr.waitForDeath()
          >T3srvr.run()
          >Server.main()
          >
          >I do save some objects which are not Serializable in the session. I understand
          >that session data can be made persistent in a file/jdbc and then the objects
          >must
          >be Serializable but not when saving the session data in memory.
          >Why is WLS trying to Serialize the Session Data and how can I switch it
          >off ?
          >The Documentation says that it is allowed to store any object in the sessio,
          >as
          >long as it is not persistet.
          >
          >Thanks for your help,
          > Oliver
          >

Use of error page resulting in could not deserialize session data exception

          We have recently converted classes that store objects in the HTTP Session to implement
          serializable.
          Our application uses an error page set up in our web.xml for 500 errors.
          It also uses filters.
          When our application throws an exception and allows the server to handle it
          via the error page setup, we end up with the exception we threw, plus a number
          of
          "Could not deserialize session data" exceptions in the stack trace.
          In general, the exceptions can be traced to lines in code that attempt to reference
          one of our "serializable" session objects to get user info for logging purposes.
          Problem is, other applications that do not use error pages to handle exceptions
          do not throw these types of exceptions in the wl-domain.log and they use the same
          classes.
          Does anyone know why this happens when using error pages and what we need to do
          to correct it?
          We are using Weblogic 8.1sp2.
          Thanks!!
          Example of the stack trace messages:
          ####<May 5, 2004 2:52:17 PM EDT> <Error> <HTTP Session> <machinexyz> <cgServer>
          <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-100028>
          <Could not deserialize session data.
          java.io.NotSerializableException: weblogic.servlet.internal.FilterConfigImpl
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
               at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1330)
               at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1302)
               at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
               at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
               at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.java:136)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:112)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:69)
               at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:431)
               at doh.stuff.OurFilter.doFilter(OurFilter.java:67)
               at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
               at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:305)
               at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:523)
               at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletContext.java:3908)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3683)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          >
          ####<May 5, 2004 2:52:17 PM EDT> <Error> <HTTP Session> <machinexyz> <cgServer>
          <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-100028>
          <Could not deserialize session data.
          java.io.NotSerializableException: java.util.Vector$1
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
               at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1330)
               at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1302)
               at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
               at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
               at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.java:136)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:112)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:69)
               at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:431)
               at doh.stuff.OurHTML.<init>(OurHTML.java:57)
               at doh.stuff.OurFilter.startLog4j(OurFilter.java:513)
               at doh.stuff.OurFilter.doFilter(OurFilter.java:75)
               at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
               at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:305)
               at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:523)
               at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletContext.java:3908)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3683)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          >


          We have recently converted classes that store objects in the HTTP Session to implement
          serializable.
          Our application uses an error page set up in our web.xml for 500 errors.
          It also uses filters.
          When our application throws an exception and allows the server to handle it
          via the error page setup, we end up with the exception we threw, plus a number
          of
          "Could not deserialize session data" exceptions in the stack trace.
          In general, the exceptions can be traced to lines in code that attempt to reference
          one of our "serializable" session objects to get user info for logging purposes.
          Problem is, other applications that do not use error pages to handle exceptions
          do not throw these types of exceptions in the wl-domain.log and they use the same
          classes.
          Does anyone know why this happens when using error pages and what we need to do
          to correct it?
          We are using Weblogic 8.1sp2.
          Thanks!!
          Example of the stack trace messages:
          ####<May 5, 2004 2:52:17 PM EDT> <Error> <HTTP Session> <machinexyz> <cgServer>
          <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-100028>
          <Could not deserialize session data.
          java.io.NotSerializableException: weblogic.servlet.internal.FilterConfigImpl
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
               at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1330)
               at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1302)
               at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
               at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
               at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.java:136)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:112)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:69)
               at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:431)
               at doh.stuff.OurFilter.doFilter(OurFilter.java:67)
               at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
               at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:305)
               at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:523)
               at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletContext.java:3908)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3683)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          >
          ####<May 5, 2004 2:52:17 PM EDT> <Error> <HTTP Session> <machinexyz> <cgServer>
          <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-100028>
          <Could not deserialize session data.
          java.io.NotSerializableException: java.util.Vector$1
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
               at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1330)
               at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1302)
               at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
               at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
               at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.java:136)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:112)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:69)
               at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:431)
               at doh.stuff.OurHTML.<init>(OurHTML.java:57)
               at doh.stuff.OurFilter.startLog4j(OurFilter.java:513)
               at doh.stuff.OurFilter.doFilter(OurFilter.java:75)
               at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
               at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:305)
               at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:523)
               at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletContext.java:3908)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3683)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          >

BEA 100028 Could not deserialize session data.

Hi there,
We have a production system which is running WL 8.1 which our J2EE application on top.
In the WL domain logs the following error occurs :
####<Jan 31, 2007 8:50:07 AM CET> <Error> <JDBC> <viepapsro10> <viepapsro10> <ExecuteThread: '0' for queue: 'JMSStore<viepapsro10JDBCStore>.ioThreadPool'> <<WLS Kernel>> <> <BEA-001112> <Test "SELECT 1 FROM DUAL" set up for pool "com.jr.jms.jdbcstore.cp" failed with exception: "java.sql.SQLException: OALL8 is in an inconsistent state.".>
####<Jan 31, 2007 8:50:34 AM CET> <Error> <HTTP Session> <viepapsro10> <viepapsro10> <ExecuteThread: '2' for queue: 'weblogic.admin.RMI'> <<anonymous>> <> <BEA-100028> <Could not deserialize session data.
java.lang.Throwable: com.jr.broadband.webapp.taglib.search.SearchResult
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at java.util.HashMap.writeObject(HashMap.java:978)
at sun.reflect.GeneratedMethodAccessor23.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.java:171)
at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:146)
at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:83)
at weblogic.servlet.internal.session.SessionData.removeAttribute(SessionData.java:613)
at weblogic.servlet.internal.session.SessionData.removeAttribute(SessionData.java:595)
at weblogic.servlet.internal.session.SessionData.remove(SessionData.java:807)
at weblogic.servlet.internal.session.MemorySessionContext.invalidateSession(MemorySessionContext.java:69)
at weblogic.servlet.internal.session.SessionContext$InvalidationAction.run(SessionContext.java:613)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.session.SessionContext$SessionInvalidator.cleanupExpiredSessions(SessionContext.java:533)
at weblogic.servlet.internal.session.SessionContext.deleteInvalidSessions(SessionContext.java:410)
at weblogic.servlet.internal.WebAppRuntimeMBeanImpl.deleteInvalidSessions(WebAppRuntimeMBeanImpl.java:234)
at sun.reflect.GeneratedMethodAccessor135.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
BEAs explanation is :
BEA-100028
Error: Could not deserialize session data.
Description
Could not deserialize session data.
Cause
Failed to deserialize session data.
Action
Make sure the object you are putting into the session is serializable and also the non-transient object it aggregates are also serializable.
If any of the non-transient objects in the entire object graph are not serializable, you will receive this error message.
which doesn't make a great deal of sense to me, can any one shed any light on what exactly is going on?
Kind Regards,
AListair Mckeown

hi,
seems like your connection has gone bad, this could happen for a number of reasons I guess. Here it could be either a misconfiguration of the DB driver against the DB version, or perhaps the session data is simply to big.
google for OALL8 and look for a solution there.
- [url http://blog.thej2eestruggle.com]Anders Mathisen

NullPointerException: Could not deserialize session data

Hi all,
I am getting this exception on the portal application again and again. Can somebody help me out with this?
####Sept 29, 2007 2:34:23 PM EST> <Error> <HTTP Session> <beapweb1> <HUSLM01> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<anonymous>> <> <BEA-100028> <Could not deserialize session data.
java.lang.NullPointerException
     at com.bea.wlw.netui.pageflow.FlowController.valueUnbound(FlowController.java:1968)
     at com.bea.wlw.netui.pageflow.PageFlowController.valueUnbound(PageFlowController.java:643)
     at weblogic.servlet.internal.session.SessionData.removeAttribute(SessionData.java:543)
     at weblogic.servlet.internal.session.SessionData.removeAttribute(SessionData.java:345)
     at weblogic.servlet.internal.session.ReplicatedSessionData.removeAttribute(ReplicatedSessionData.java:597)
     at weblogic.servlet.internal.session.SessionData.remove(SessionData.java:854)
     at weblogic.servlet.internal.session.ReplicatedSessionData.remove(ReplicatedSessionData.java:312)
     at weblogic.servlet.internal.session.ReplicatedSessionContext.invalidateSession(ReplicatedSessionContext.java:567)
     at weblogic.servlet.internal.session.SessionContext$InvalidationAction.run(SessionContext.java:612)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:323)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:101)
     at weblogic.servlet.internal.session.SessionContext$SessionInvalidator.cleanupExpiredSessions(SessionContext.java:560)
     at weblogic.servlet.internal.session.SessionContext$SessionInvalidator.trigger(SessionContext.java:467)
     at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:293)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:323)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:101)
     at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
     at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:213)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:214)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:179)
The application is on WebLogic Portal 8.1 SP5 and it's on a cluster.
Any help would be greatly appreciated.
Thanks
Sam

Hi
you seem to have session replication turned on in your cluster .
In which case any private member variable in any pageflow must be serializable for the session replication to work.(or marked as transient etc.)
regards
deepak

Could not deserialize session data

Hello,
I have created Adf application which have SOA worklist link in it. I have deployed both worklist and Adf application on soa_server having port 8001. When I open link to worklist from Adf application I got following error .( and it invalidates all the session from adf application)
<Error> <HTTP Session> <BEA-100028> <Could not deserialize session data.
java.lang.ClassCastException: oracle.adf.model.dcframe.DataControlFrameImpl cann
ot be cast to oracle.adf.model.DataControlFrame.....
Also while searching on blogs I found it is related to OptimisticSerialization in web.xml. But I was not able to find the option from weblogic console i.e.. localhost:7001/em.
Please let me know any solution for same.
Thank you,
Sandeep.

Hello,
I have created Adf application which have SOA worklist link in it. I have deployed both worklist and Adf application on soa_server having port 8001. When I open link to worklist from Adf application I got following error .( and it invalidates all the session from adf application)
<Error> <HTTP Session> <BEA-100028> <Could not deserialize session data.
java.lang.ClassCastException: oracle.adf.model.dcframe.DataControlFrameImpl cann
ot be cast to oracle.adf.model.DataControlFrame.....
Also while searching on blogs I found it is related to OptimisticSerialization in web.xml. But I was not able to find the option from weblogic console i.e.. localhost:7001/em.
Please let me know any solution for same.
Thank you,
Sandeep.

Could not deserialize session data, java.io.InvalidClassException

Whenever I click on logout link from Liferay(Which deployed as application on Weblogic 10.3),It shows below Exception in the console however i am able to logout sucessfully.
Could not deserialize session data.
java.io.InvalidClassException: org.hibernate.proxy.pojo.javassist.SerializableProxy; local class incompatible: stream classdesc serialVersionUID = 1180036893511205383, local class serialVersionUID = -2265249369383210104 at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:560)
It seems to be Classpath polluted with different hibernate jars.But still not able to figure it out.Below is the jar files which i have in classpath.
hibernate-annotations.jar
hibernate-commons-annotations.jar
hibernate-core.jar
hibernate3.jar
Application Server: Weblogic 10.3
Any Help would be much appreciated.

Sounds like you have two different versions of a class in the two applications.
If you change a class implementation and recompile - the updated class gets a new UID. Looks like maybe one app has a jar with the older class and the other app has a jar with the new class.

User Mapping: Could not save logon data

Hi
I have installed EP6 NW04 SP9 on an AIX system with DB2 database and I'm trying to assign mapping data (user & password) to users through User Administration -> User Mapping option.
When I try to save it, the portal shows the message: Could not save logon data.
During the installation I imported the Cryptography toolkit with strong encription so the property ume.usermapping.unsecure is set to false.
Would it be possible somebody to help me please.
Thanks

Hi,
I have the same problem and the parameter 'ume.usermapping.unsecure' is TRUE and encryption is weak. So, in UME configuration, the portal is integrated with ADS using ADS Flat + Database.
The version portal is EP6 SP 11!
Help us, please!
Thanks

Could not convert the data value due to reasons other than sign mismatch or overflow. ADSI Provider

I'm trying to run the following query against Active Directory using the ADSI Provider using SSMS 2012 SP1:
SELECT
TOP901
*FROMOpenQuery
ADSI
'SELECT description
FROM ''LDAP://OU=MMICorporate,DC=mmis,DC=mi,DC=com''
WHERE objectClass = ''User''
and objectcategory = ''Person''
and ''userAccountControl:1.2.840.113556.1.4.803:''<>2
)AStblADSI
Msg 7346, Level 16, State 2, Line 2
Cannot get the data of the row from the OLE DB provider "ADsDSOObject" for linked server "ADSI". Could not convert the data value due to reasons other than sign mismatch or overflow.
I only have this issue querying the Description Field.
I also found a hotfix KB: 887474 for this but it is for Windows 2003. SQL Server OS I have is Server 2008 R2. Is there a fix for 2008 R2?
Thanks

Thanks for the quick response.
I checked out the link and I can only convert to Ul8 and when I try I get the same error:
SELECT
TOP901
*FROMOpenQuery
ADSI
'SELECT name, convert(UI8, description)
FROM ''LDAP://OU=MMICorporate,DC=mmis,DC=mi,DC=com''
WHERE objectClass = ''User''
and objectcategory = ''Person''
and ''userAccountControl:1.2.840.113556.1.4.803:''<>2
)AStblADSI
Am I missing something?
Thanks

How to solve the error message "Could not activate cellular data network: PDP authentication failure"when using 3g or gPRS on safari with an iphone 4 and latest software updates

Please can someone help me to solve the error message "Could not activate cellular data network: PDP authentication failure"when using 3G or GPRS on safari with an iphone 4GS and latest software updates. I have tried resetting the network and phone settings. I have restored the factory settings on itunes and still the problem persists.

All iPhones sold in Japan are sold carrier locked and cannot be officially unlocked by the carrier. If you unlocked it, it was by unauthorized means (hacked), and support cannot be given to you in this forum.
Hacked iPhones are subject to countermeasures by Apple, particularly when updating the firmware. It is likely permanently re-locked or permanently disabled.
Message was edited by: modular747

IPHONE 5: can't receive calls & random error messages, such as "could not activate cellular data network" and "no connection - network unavailable, please connect to wifi or cellular network." This occurs even when signal strength or wifi is operational.

IPHONE 5: can't receive calls and random error messages, such as "could not activate cellular data network" and "no connection - network unavailable, please connect to wifi or cellular network." This occurs even when signal strength or wifi is operational, and it does not matter whether wifi is on or off. ATT went through the standard protocol - resetting network, resetting sim card, etc. No changes. Other phones working fine in same region with same carrier. Apple's solution is to restore software, but haven't gone there yet. Anyone successfully addressed this/these issues?

I should point out that it worked when the iPhone was set back to factory settings, but when restored with the backup, data/internet no longer works again, and I get the "Could not activate cellular data network" error message yet again.

Getting an error when using adobe photoshop CC, "Could not move the data because of a program error". Any idea on what this means?

Getting an error when using adobe photoshop CC, "Could not move the data because of a program error". Any idea on what this means?

Have no idea of what you were even doing in Photoshop my crystal ball is out for repairs so I can not see.

After Loading Lion I now get 5 windows w/ a graphic of a Red Stop sign with an ! mark and the following text message: "DAVE Networking Dave kernel extensions could not be loaded! Error 71 - Too many levels of remote in path."

After Loading Lion I now get 5 windows w/ a graphic of a Red Stop sign with an ! mark and the following text message:
"DAVE Networking
Dave kernel extensions could not be loaded! Error
71 - Too many levels of remote in path."
I have uninstalled DAVE and used Clean App to remove trace elements of program, however I still get the message and am unable to eliminate the error messages. When I click OK the message goes away briefly and then comes back up.
Any solutions would be great.

Dave,
Thanks....What I did was load the free eval version of Dave 9.0 and then used the uninstaller which must have deleted the kernel giving me the problem.
Thanks for the response.
Razor

Debuging mapping - error : Could not find test data for target operators ?

Hello, Please help me.
I use Oracle Warehouse Builder 10gR2.
I created a cube with two dimensions.
I debugged the mappings of these two dimensions then viewed their data after deployment.
I tried to debug the mapping of the cube, and got the error: Could not find test data for all source and target operators.
For source objects exist test data but for the target operator (cube_out) logically we do not need test data !!!! .
But the error is here: Could not find test data for target operators. Why ??
How to configure or explain to owb that the target operator do not have test data ????
I need your help.
thank you in advance.

Sorry, I can not understand your approach ?
I explain you in detail : I work in ROLAP.
I have two dimensions : DIM_1 and DIM_2 linked with the cube (Fact_table).
I have three mappings : MAP_DIM1, MAP_DIM2, MAP_CUBE.
For the MAP_CUBE, I have source operator : VIEW_IN and Target operator : CUBE_OUT.
I could see the data dimensions : DIM_1 and DIM_2 after debugging and Deployment in the OLAP schema.
I tried debugged the mapping: MAP_CUBE so I got the error: Could not find test data for all source and target operators.*
thank you for help.

Whenever i try to download a rather large file i continue to get the "could not read source file" error. Tried new profile, uninstalling and looking for the compreg.dat file to delete nothing is working. Please help

whenever i try to download a rather large file i continue to get the "could not read source file" error. Tried new profile, uninstalling and looking for the compreg.dat file to delete nothing is working. Please help

Did you reinstall CS3 after CC?
For that matter, doing an in-place upgrade on the OS is always a gamble with Adobe programs. Reinstalling all the versions you need, in order, would probably solve your problem.
And you shouldn't need to save as IDML after opening the .inx in CC.

"Could not deserialize session data" error during sign out

Similar Messages

Maybe you are looking for