John Cartwright wrote:
Thanks Ethan, that makes sense. Any ideas on what could cause that
listener to fail? I tried changing the log level for tomcat to capture
any stack trace on the failure but didn't gain any extra information.
--john
the listener ss the first thing that gets loaded - so problems with
classpath, etc, show up there first, that have nothing to do with the
listener code per se.
have you checked all log files to see if there are any more messages?
delete all log files, startup, then look everything.