Hello,
A few days ago, Tomcat (5.5.20 on linux) suddenly refused to initialize one
of my webapps,
claiming that a HttpSessionListener that I have implemented has 'unresolved
compilation
problems':
2007-07-18 15:39:15,496 ERROR - StandardContext - Error configuring
application
listener of class com.tryllian.bonfire.client.BonfireSessionListener
java.lang.Error: Unresolved compilation problems:
The import some.import cannot be resolved
The import some.import cannot be resolved
The import some.import cannot be resolved
The import some.import cannot be resolved
some_class cannot be resolved to a type
some_other_class cannot be resolved to a type
some_other_class cannot be resolved to a type
a_third_class cannot be resolved to a type
The method some_method is undefined for the type yet_another_class
a_fourth_class cannot be resolved
This is a strange error: the listener and the classes on which it depends
have not been changed
for quite a while. All classes and packages mentioned as '... cannot be
resolved' are actually
present in WEB-INF/classes and are undamaged. Despite those facts, Tomcat
doesn't find them
and even thinks 'some_method' is missing in one of them, even though the
classes compiled
correctly.
I'm considering exotic options like: Tomcat unpacks the war in a different
thread from the one that is
initializing the webapp and the war (now ~20MB) has reached a size where it
takes longer for the
war to be unpacked than for the inialization thread to start initializing
the listener.
Even stranger is the fact that repeatedly repacking and deploying the webapp
sometimes results in
a succesfull deployment. Does anyone have an idea about what may be going
on?
sincerely,
--
Ivo Wever
--
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)