Are you using Tomcat 4.1.x ? If yes, is this only happening every second
time you restart the Tomcat engine ?
If yes again, it is a known Tomcat issue with serializing sessions.
There is a way to work around it by specifying another session manager
for your webapp context in the tomcat server.xml config file like this.
<Context path="/myapp" docBase="E:/src/myapp/target/myapp" debug="0">
<Manager className="org.apache.catalina.session.PersistentManager"
debug="0" saveOnRestart="false">
<Store className="org.apache.catalina.session.FileStore"/>
</Manager>
</Context>
It's the "safeOnRestart=false" that does the trick. This prevents Tomcat
from serializing your session and trying to deserialize it again on
startup, at which time it will encounter a classloading problem when
trying to instantiate your extended User object.
Good luck,
Age
> I'm developing with Turbine 2.2 and occasionally, at start
> up, the SecurityService will "hang". It seems to stop at the
> line of code that instantiates the User object using the
> Class.forName method. I'm using a subclassed User object and
> have referenced it in the TurbineResources property file . I
> thought it might be some kind of race condition but it's
> difficult to debug since it always works when I'm stepping through.
>
> I've searched the archive and have found a reference to the
> same problem:
>
http://www.mail-archive.com/[EMAIL PROTECTED]/msg09906.htm
l
Any ideas?
p.s. Thanks to all the developers of Turbine. This is a great framework.
Glen.
---------------------------------------------------------------------
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]
