environment issue?

Jchem3.1.6


This problem did not exist yesterday - today it appears to.


Not sure why? Please help. Click on the query button in vanilla JSP and window/error below pops up? Contents of Catalina are as follows:





17-Aug-2006 12:39:31 org.apache.catalina.session.StandardManager doLoad


SEVERE: IOException while loading persisted sessions: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: oracle.jdbc.driver.OracleConnection


java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: oracle.jdbc.driver.OracleConnection


at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1278)


at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)


at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)


at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)


at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)


at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)


at org.apache.catalina.session.StandardSession.readObject(StandardSession.java:1342)


at org.apache.catalina.session.StandardSession.readObjectData(StandardSession.java:885)


at org.apache.catalina.session.StandardManager.doLoad(StandardManager.java:416)


at org.apache.catalina.session.StandardManager.load(StandardManager.java:343)


at org.apache.catalina.session.StandardManager.start(StandardManager.java:657)


at org.apache.catalina.core.ContainerBase.setManager(ContainerBase.java:499)


at org.apache.catalina.startup.ContextConfig.managerConfig(ContextConfig.java:315)


at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:635)


at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:216)


at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)


at org.apache.catalina.core.StandardContext.start(StandardContext.java:4290)


at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083)


at org.apache.catalina.core.StandardHost.start(StandardHost.java:789)


at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083)


at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478)


at org.apache.catalina.core.StandardService.start(StandardService.java:480)

The error message is invoked because the initalization of the Calculator Plugin menu ("Tools" menu) failed.


Have you modified the marvin/xjars/plugin.properties file?


If not, it may be a caching problem. If resources of two Marvin versions are mixing, it can cause similar problem.


Try to clean JRE's cache, probably, it solves the problem.

I have cleared the $CATALINA_HOME/work directory and I'm afraid the problem still persists are you refering to a $JAVA_HOME\<cache> if so can you specify where this is please?

As I saw, the exception was dropped by the applet. Thus, you should clear JRE cache.


See the following topic: How I can clear JRE cache

I have tried the suggestions, but I fear the error persists...





Any other suggestions for this error message?





Cheers,


Daniel.

Dear Daniel,





There are two independent problems there.





Problem 1 (Tomcat stack trace):





This is not a real problem, you have only noticed this, because other problems made you look for anything suspicious.





When you shut down and restart Tomcat, it automatically tries to preserve the state of the sessions via serialization (converting Java objects into binary form). If it encounters non-serializable objects amongst session variables it will throw an exception, and will not initialize this variable, but this does not do any harm.





This is a relatively new feature in Tomcat.





I suggest you to turn it off to prevent these messages flood your log file.


This may very bit according to Tomcat version.


If using the latest version (5.5) please do the following:





Locate

Code:

<tomcat_home_dir>/conf/context.xml

Uncomment this line:

Code:

<Manager pathname="" />

Problem 2 (applet stack trace):


This is totally independent from problem #1, it is a client side problem, wile the other was a server-side stack trace.





Please follow the advice of Tamas (clearing browser cache), and check if the marvin directory is intact on the server.





Best regards,





Szilard

Thanks Szilard and Tamas, all problems resolved...Cheers Daniel.