Deploying an app with a runtime dependency missing resulted in Servlet.init()
throwing a ServletException caused by a ClassNotFoundException.
Tomcat manager however reported the application as running. I guess it was
to a certain extent, however it would have been more useful to me to know
that
Have been looking at the source, although not documented (for TC5.5), it
seems that it is possible to nest a Listener element
(org.apache.catalina.LifecycleListener) under the Server element as
http://tomcat.apache.org/tomcat-5.5-doc/config/context.html described here
for nesting within Context
I was meaning that it appears you can add a listener directly to the Server
element (AFAIU from the code anyway).
Server ...
Listener ... /
...
Not synchronous? Aren't notifications almost always synchronous?
Yes, the notification would be synchronous but the call to stop is still
Using:
$CATALINA_HOME/bin/catalina.sh stop
$CATALINA_HOME/bin/catalina.sh start
in quick succession to restart Tomcat,
it is possible that the start operation will run before all ports have been
released by the instance I'm stopping.
Is there a synchronous method for stopping Tomcat, i.e. one
Filip Hanik - Dev Lists wrote:
Derek Alexander wrote:
the same app would have to run on both instances,
You mean this error is normal when starting the first server in a
cluster?
if it was the first server, it wouldn't request state from another,
would it ?:)
Indeed, using
Does this application run well in a tomcat that isn't clustered?
Yes
Does your application have the distributable/ element in web.xml?
Yes
I'd recommend looking through the output in the other log files in
$CATALINA_HOME/logs/, especially localhost, to see whether there are
any exceptions
the same app would have to run on both instances,
You mean this error is normal when starting the first server in a cluster?
--
View this message in context:
http://www.nabble.com/Error-reported-when-starting-app-in-cluster-tf4212847.html#a11985035
Sent from the Tomcat - User mailing list
Getting an ERROR reported when starting webapp within a cluster.
Note, at this time I am starting the first server in the cluster, which is
the 192.168.0.1 mentioned in the error message.
Can someone please explain if it is correct that I am receiving an error and
if so, what is wrong.
Hi,
I want to use the manager to deploy an app with the context path like
/123/456/789
If I use the manager path=/123/456/789 war=file:789.war it doesn't work.
At the client end (ant) I'm seeing: FAIL - Failed to deploy application at
context path /123/456/789
In the logs on server, there is
