Thanks for the prompt reply Petar. Here is the relevant portion from my build file.
<cactus warfile="${build.dir}/test.war" fork="yes" printsummary="yes" haltonerror="true" haltonfailure="true"> <classpath> <path refid="project.classpath"/> <pathelement location="${httpunit.jar}"/> <pathelement location="${nekohtml.jar}"/> <pathelement location="${build.classes.dir}"/> <pathelement location="${build.classes.cactus.dir}"/> </classpath> <containerset> <cargo containerId="jboss42x" output="${logs.dir}/cargo_output.log" log="${logs.dir}/cargo.log" home="${jboss.home.dir}" action="start" wait="false"> <configuration> <property name="cargo.servlet.port" value="8081"/> <property name="cargo.jboss.configuration" value="${jboss.config}"/> <property name="cargo.jvmargs" value="${jvmargs}"/> <property name="cargo.logging" value="${cargo.logging}"/> <deployable type="war" file="${build.dir}/test.war"/> </configuration> </cargo> </containerset> <formatter type="brief" usefile="false"/> <formatter type="xml"/> <batchtest> <fileset dir="${src.test.dir}"> <include name="**/*Test.class"/> </fileset> </batchtest> </cactus> With this the startup of the server always fails with port already in use error. Instead of cargo as the nested element, can I use something like this -- Instead of the cargo portion I tried using <jboss42x dir="${jboss.home.dir}" output="${logs.dir}/server_output.txt" port="8081"/> or is this no longer supported because this gives an error saying jboss42x is not a supported nested element. Thanks On Mon, Dec 29, 2008 at 12:36 AM, Petar Tahchiev <paranoia...@gmail.com>wrote: > Hi Naha, > > first you need to use the jboss42x nested element for Cargo to work. > This is clearly defined in the Cargo documentation: > http://cargo.codehaus.org/JBoss+4.2.x > > Before you paste your configuration (the Ant scripts or the Maven poms) > I am unable to locate the problem any further. > > Cheers, Petar. > > 2008/12/29 Neha Agarwal <neha...@gmail.com> > > Hi, >> >> I have cactus 1.8 and Jboss 4.2 installed. I am tryong to get cactus >> working >> but if I use the jboss4x nested element within containerset, it gives me >> an >> error saying that jboss4x is not supported for ContainerSet. Just to >> check, >> I tried jboss3x but I get the same error for that as well. >> >> Was inidividual containerset element support removed in favor of cargo in >> cactus 1.8? >> >> I do not want to use, cargo because I need to start my server separately >> and >> then use cactus to run my tests in a different shell. >> >> Also when I try to use cargo to start my server and run the tests on it, I >> get a "Port already in use error" even though I have nothing running on >> that >> port (I checked). When cargo is trying to start up my server when I check >> that port, the only output I see is this: >> >> java 1847 nxxx 263u IPv6 0xb484d90 0t0 TCP >> [::127.0.0.1]:53442->[::127.0.0.1]:sunproxyadmin (ESTABLISHED) >> java 1847 nxxx 265u IPv6 0x5b26984 0t0 TCP >> [::127.0.0.1]:53443->[::127.0.0.1]:sunproxyadmin (ESTABLISHED) >> java 1850 nxxx 13u IPv6 0x5b26be8 0t0 TCP >> [::127.0.0.1]:sunproxyadmin (LISTEN) >> >> Right before cargo starts up, there is nothing on that port. If it makes >> any >> difference I am using port 8081 for my jboss server. >> If I get rid of this error, I might be able to use cargo. >> >> Any suggestions on why I am seeing this? >> >> Any help would be greatly appreciated, >> Thanks, >> N. >> > > > > -- > Regards, Petar! > Karlovo, Bulgaria. > - - - - - - - - > | Author @ Manning Publications. > | Senior Sofware Engineer @ Unic > | BGJUG-Bulgarian Java User Group Leader. > | Apache Jakarta PMC member. > | Jakarta Cactus Lead Developer. > | Blogger: http://weblogs.java.net/blog/paranoiabla/ > - - - - - - - - > Public PGP Key at: > https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611 > Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611 >