You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jspwiki.apache.org by "Juan Pablo Santos RodrÃguez (JIRA)" <ji...@apache.org> on 2013/01/12 23:16:12 UTC
[jira] [Commented] (JSPWIKI-659) NotSerializableException on Tomcat
restart , UserManager not Serializable
[ https://issues.apache.org/jira/browse/JSPWIKI-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552081#comment-13552081 ]
Juan Pablo Santos RodrÃguez commented on JSPWIKI-659:
-----------------------------------------------------
Hi,
JSONRPCBridge needs to be in session to enable javascript access to all classes implementing org.apache.wiki.rpc.RPCCallable (cfr. [related link to jsonrpc|http://viralpatel.net/blogs/calling-rpc-in-javascript-using-json-rpc-java/]). In this case, seems to me that JSONUserModule#getUserInfo() gets called at ./src/webdocs/templates/default/admin/UserManagement.jsp, line 44.
Aside from JSONUserModule there are 3 more classes implementing RPCCallable, with functionalities related to search, file upload and a sample plugin with AJAX support.
Declaring UserManager transient inside JSONUserModule seems to be insufficient to make it Serializable (cfr. http://stackoverflow.com/q/7144912). Haven't tested yet, but promoting JSONUserModule to a first level class instead of being an inner class would take away the exception. If that's the case, I think we could do this in 2.9.1, doesn't seem to me like a class used for extending JSPWiki...
br,
juan pablo
> 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
>
>
> 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