[
https://issues.apache.org/jira/browse/JSPWIKI-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552522#comment-13552522
]
Janne Jalkanen commented on JSPWIKI-659:
----------------------------------------
Yup. So I am assuming that the JSON api will stop to work if you switch to
GlobalBridge.
> NotSerializableException on Tomcat restart , UserManager not Serializable
> -------------------------------------------------------------------------
>
> Key: JSPWIKI-659
> URL: https://issues.apache.org/jira/browse/JSPWIKI-659
> Project: JSPWiki
> Issue Type: Bug
> Components: Core & storage
> Affects Versions: 2.8.3, 2.9.1
> Environment: apache-tomcat-6.0.16
> Reporter: Vasilij Pupkin
> Assignee: Harry Metske
> Priority: Minor
> Attachments: ff.patch, JSPWIKI-659.patch
>
>
> If you stop Tomcat using ctrl-C and restart it again, there is a
> NotSerializableException on the console. Looks like this has no consequences,
> but still it should not be.
> SCHWERWIEGEND: IOException while loading persisted sessions:
> java.io.WriteAbortedException: writing
> aborted; java.io.NotSerializableException:
> com.ecyrd.jspwiki.auth.UserManager$JSONUserModule
> java.io.WriteAbortedException: writing aborted;
> java.io.NotSerializableException: com.ecyrd.jspwiki.
> auth.UserManager$JSONUserModule
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1333)
> at
> java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)
> <<< SKIPPED >>>
> Starting up background thread: WatchDog for 'JSPWiki'.
> 17.03.2008 11:40:43 org.apache.coyote.http11.Http11Protocol start
> INFO: Starting Coyote HTTP/1.1 on http-8080
> 17.03.2008 11:40:43 org.apache.jk.common.ChannelSocket init
> INFO: JK: ajp13 listening on /0.0.0.0:8009
> 17.03.2008 11:40:43 org.apache.jk.server.JkMain start
> INFO: Jk running ID=0 time=0/31 config=null
> 17.03.2008 11:40:43 org.apache.catalina.startup.Catalina start
> INFO: Server startup in 4239 ms
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
