jakarta-cactus-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kazuhito SUGURI <suguri.kazuh...@lab.ntt.co.jp>
Subject Re: Running <cactus> from Ant
Date Wed, 12 Oct 2005 05:32:42 GMT

In article <s34b71b3.064@dfg.ca.gov>,
Tue, 11 Oct 2005 08:02:27 -0700,
"Kevin Murdoff" <KMURDOFF@dfg.ca.gov> wrote: 
KMURDOFF> I read in the docs that the <containerset> won't start and stop
KMURDOFF> Tomcat if it is already running, but when I use it with a port of
KMURDOFF> 8080, it complains (obviously) that port 8080 is already bound.
KMURDOFF> No doubt by my existing Tomcat instance.

AFAIK, to know whether a container is already running,
<cactus> task accesses to ServletRedirector of the target contextURL
and checks its response status. In other words, <cactus> task checks
whether the target cactified application is available.
So, you need to deploy the cactified application
prior to the <cactus> task call.

KMURDOFF> However, when I change the port to say 55555, none of my tests succeed.
KMURDOFF> The test classes could not be loaded by the Context and web apps class loaders.

If you only changed the port attribute of the tomcat5x element
in your build.xml, that may be not enough. You need to provide
a server configuration file (server.xml) for the new server instance.
In your use case, I think, the server.xml, which has been configured
for the existing server instance, has conflicting conditions
that cause the start up of the new server to be failed.
<tomcat5x> task uses ${directory specified by dir attr}/conf/server.xml
to start up the new server by default, but you can change it
by using serverxml attribute.

Be sure that all ports the new server will listen to are not in use
by the existing server, 8005 and 8080 for examples.

Hope this helps,
Kazuhito SUGURI

View raw message