Thanks, Scott. Implementing Serializable to the object that I store didn't
really help. Now tomcat complains about a velocity-object (!) not being
serializable:

2003-02-23 01:54:55 StandardManager[/audiotex] IOException while loading
persisted sessions: java.io.WriteAbortedException: writing aborted;
java.io.NotSerializableException:
org.apache.velocity.runtime.parser.node.ASTMethod
java.io.WriteAbortedException: writing aborted;
java.io.NotSerializableException:
org.apache.velocity.runtime.parser.node.ASTMethod
        at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1278)
        at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
        at java.util.HashMap.readObject(HashMap.java:985)
        at sun.reflect.GeneratedMethodAccessor91.invoke(Unknown Source)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:824)
....

and

2003-02-23 01:54:55 StandardManager[/audiotex] Exception loading sessions
from persistent storage
java.io.WriteAbortedException: writing aborted;
java.io.NotSerializableException:
org.apache.velocity.runtime.parser.node.ASTMethod
        at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1278)
        at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
        at java.util.HashMap.readObject(HashMap.java:985)
        at sun.reflect.GeneratedMethodAccessor91.invoke(Unknown Source)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:824)
        at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1746)
.......


What is that?





> -----Ursprungliche Nachricht-----
> Von: Scott Eade [mailto:[EMAIL PROTECTED]
> Gesendet: Sonntag, 23. Februar 2003 01:24
> An: turbine-user
> Betreff: Re: any restrictions for objects to store them to user.Temp?
>
>
> Marc,
>
> 1. When you put an object in user.Temp you are putting it into
> the session,
> so whether or not you should do it depends on the amount of
> memory available
> and configured as well as how busy the site is in terms of number of
> concurrently logged in users.
> 2. Tomcat will attempt to serialize the sessions when it is
> restarted (can't
> recall if this is the default behaviour, I think it may well be),
> so if the
> object in user.Temp is not serializable you will run into the kind of
> problem you describe below.  I am using Jetty for development
> which doesn't
> do this by default but have not yet moved to Jetty for production (still
> using Tomcat) - I have been hitting this problem myself today (storing
> LargeSelect objects in user.Temp).  Either turn off persistent sessions or
> make the objects you are storing in user.Temp serializable.
>
> HTH,
>
> Scott
> --
> Scott Eade
> Backstage Technologies Pty. Ltd.
> http://www.backstagetech.com.au
> .Mac Chat/AIM: seade at mac dot com
>
>
> On 23/02/2003 11:02 AM, "Marc Lustig" <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > I'm storing an objekt to user.Temp which might be a little large.
> > Since I've done that there is some trouble with Tomcat:
> >
> > 2003-02-23 00:53:22 StandardManager[/audiotex] Exception
> loading sessions
> > from persistent storage
> > java.io.WriteAbortedException: writing aborted;
> > java.io.NotSerializableException:
> > de.geoconnect.audiotex.navigation.Navigation
> > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1278)
> > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
> > at java.util.Hashtable.readObject(Hashtable.java:837)
> > at sun.reflect.GeneratedMethodAccessor89.invoke(Unknown Source)
> > at
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAc
cessorImpl
> > .java:25)
> > at java.lang.reflect.Method.invoke(Method.java:324)
> > at
> java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:824)
> > ......
> >
> > The webapp still seems to work properly, except that the login takes 20
> > seconds.
> >
> > Is there any restriction in size for storing objects to User.Temp?
> > Or must objects meet certain requirements to store them to User.Temp?
> > (must implement Serializable ??)
> >
> >
> > Marc
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to