You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Simon Kitching (JIRA)" <de...@myfaces.apache.org> on 2009/05/18 13:51:45 UTC
[jira] Reopened: (ORCHESTRA-32) Hot-restart of Tomcat causes
NullPointerException while deserializing saved http-session
[ https://issues.apache.org/jira/browse/ORCHESTRA-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Kitching reopened ORCHESTRA-32:
-------------------------------------
Thanks for reporting this Mark. It's definitely a bad idea for a readResolve method to use the FrameworkAdapter because it may not exist at that time.
> Hot-restart of Tomcat causes NullPointerException while deserializing saved http-session
> ----------------------------------------------------------------------------------------
>
> Key: ORCHESTRA-32
> URL: https://issues.apache.org/jira/browse/ORCHESTRA-32
> Project: MyFaces Orchestra
> Issue Type: Bug
> Components: Conversation
> Affects Versions: 1.2
> Reporter: Simon Kitching
> Assignee: Simon Kitching
> Fix For: 1.4
>
>
> Tomcat displays this message on restart:
> SCHWERWIEGEND: Exception loading sessions from persistent storage
> java.lang.NullPointerException
> at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:881)
> at org.apache.catalina.session.StandardSession.readObject(StandardSession.java:1445)
> The problem is that the orchestra ConversationManager class has a readResolve method that returns null, intending that the object just gets created "on demand" later. However Tomcat tries to put the deserialized object into its session - and null objects are not permitted in an HttpSession.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.