Hello,
I use tomcat 5.0.28 with jdk 1.4.2 and OPS 2.8. When I restart tomcat, I have this exception: GRAVE: Exception au chargement des sessions depuis le stockage persistant (persistent storage) java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.orbeon.oxf.xml.SAXStore$1 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1278) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769).... My technical support explain me that tomcat try to reload the old session. Indeed when I delete the file "SESSIONS.ser" in the repository "work" of tomcat, I don't have this error. When I stop tomcat I have this error: INFO: Impossible de s?rialiser l'attribut de session org.orbeon.oxf.portlet-container pour la session E35CD7BBAF2FCF9C65AD052BC634D8E9 java.io.NotSerializableException: org.orbeon.oxf.portlet.PortletConfigImpl$DefaultResourceBundle at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304).... Have you a idea ? thank you. -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Administrator
|
Julien,
This happens if you are using the OPS examples portal, which stores some non-serializable objects into the session. This shouldn't happen in your own applications, which likely don't use the OPS examples portal. There is probably a way to avoid seeing those exceptions anyway, but we haven't looked into this yet. -Erik [hidden email] wrote: > Hello, > > I use tomcat 5.0.28 with jdk 1.4.2 and OPS 2.8. > When I restart tomcat, I have this exception: > > GRAVE: Exception au chargement des sessions depuis le stockage persistant (persistent storage) > java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.orbeon.oxf.xml.SAXStore$1 > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1278) > at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845) > at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769).... > > > My technical support explain me that tomcat try to reload the old session. > Indeed when I delete the file "SESSIONS.ser" in the repository "work" of tomcat, I don't have this error. > > When I stop tomcat I have this error: > > INFO: Impossible de s?rialiser l'attribut de session org.orbeon.oxf.portlet-container pour la session E35CD7BBAF2FCF9C65AD052BC634D8E9 > java.io.NotSerializableException: org.orbeon.oxf.portlet.PortletConfigImpl$DefaultResourceBundle > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054) > at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332) > at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304).... > > Have you a idea ? > > thank you. -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Thank you for your response.
Yes I use the OPS examples portal. But why tomcat try to reload this object on the start ? In fact I use the structure of examples portal with my "example". And I store object in session like this: <p:processor name="oxf:scope-serializer"> <p:input name="data" href="#instance#xpointer(/form/formId)" /> <p:input name="config"> <config> <key>formID</key> <scope>session</scope> </config> </p:input> </p:processor> And when I stop tomcat, this object looks non-serializable too. How to make it serializable ? And what object is not serializable in the examples portal ? thank you. -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Administrator
|
[hidden email] wrote:
> Thank you for your response. > > Yes I use the OPS examples portal. But why tomcat try to reload this object on the start ? That is probably just the default behavior or the default session manager behavior. You may be able to learn more here: http://tomcat.apache.org/tomcat-5.5-doc/config/manager.html > In fact I use the structure of examples portal with my "example". And I store object in session like this: > <p:processor name="oxf:scope-serializer"> > <p:input name="data" href="#instance#xpointer(/form/formId)" /> > > <p:input name="config"> > <config> > <key>formID</key> > <scope>session</scope> > </config> > </p:input> > </p:processor> > > And when I stop tomcat, this object looks non-serializable too. How to make it serializable ? And what object is not serializable in the examples portal ? I think it would be non trivial to make this serializable. This has not been considered a serious issue, since the examples portal is not meant at this point to be really used by end users' applications. Now what the scope serializer stores in the session should definitely be serializable. In fact, it should be a SAXStore object, which was meant to be serializable, but there may be a bug. Feel free to check that, but in the meanwhile I enter an RFE to track this: https://forge.objectweb.org/tracker/index.php?func=detail&aid=304313&group_id=168&atid=350210 -Erik -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Free forum by Nabble | Edit this page |