Re: Question about cactus 1.8 and jboss 4.2
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: java1847 nxxx 263u IPv6 0xb484d90 0t0 TCP [::127.0.0.1]:53442-[::127.0.0.1]:sunproxyadmin (ESTABLISHED) java1847 nxxx 265u IPv6 0x5b26984 0t0 TCP [::127.0.0.1]:53443-[::127.0.0.1]:sunproxyadmin (ESTABLISHED) java1850 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
Re: Question about cactus 1.8 and jboss 4.2
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.comwrote:
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:
java1847 nxxx 263u IPv6 0xb484d90 0t0 TCP
[::127.0.0.1]:53442-[::127.0.0.1]:sunproxyadmin (ESTABLISHED)
java1847 nxxx 265u IPv6 0x5b26984 0t0 TCP
[::127.0.0.1]:53443-[::127.0.0.1]:sunproxyadmin (ESTABLISHED)
java1850 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
Re: Question about cactus 1.8 and jboss 4.2
Never mind about starting the container. I was able to fix that. It was a problem with my build file since I was not poitning to the existing installation of the container. The container starts up correctly now, but cactus does not seem to be running the tests. Here is the output from my console. test.cactus: [cactus] - [cactus] Parsed JBoss version = [4.2.1] [cactus] Running tests against JBoss 4.2.1 @ http://localhost:8081 [cactus] - [cactus] Deploying [/Users/temp/build/test.war] to [/Users/servers/jboss4.2/server/all/deploy]... [cactus] JBoss 4.2.1 starting... [cactus] JBoss 4.2.1 started on port [8081] BUILD FAILED /User/src/test.xml:1052: Failed to start the container after more than [18] ms. Trying to connect to the [ http://localhost:8081/test/ServletRedirector?Cactus_Service=RUN_TEST] test URL yielded a [-1] error code. Please run in debug mode for more details about the error. So even though the container started, I am getting a failed to start container error and the tests do not run after this. Any ideas? Once again, any help is greatly appreciated. Thanks
Re: Question about cactus 1.8 and jboss 4.2
Hi Neha,
this error happens when there was something wrong with the war
that you deploy. Make sure that the test.war you
try to deploy is cactified and it's web.xml contains the servletRedirector
definitions.
Also one more thing that struck me in your build.xml:
Are you sure that you have something selected here:
fileset dir=${src.test.dir}
include name=**/*Test.class/
/fileset
Do you really have .class files in your src directory?
Cheers, Petar.
P.S. Have a look at the sample applications that come with cactus. Try
to run them and in case it was possible look for the differences between
your configuration and the sample one.
2008/12/29, Neha Agarwal neha...@gmail.com:
Never mind about starting the container. I was able to fix that. It was a
problem with my build file since I was not poitning to the existing
installation of the container.
The container starts up correctly now, but cactus does not seem to be
running the tests. Here is the output from my console.
test.cactus:
[cactus]
-
[cactus] Parsed JBoss version = [4.2.1]
[cactus] Running tests against JBoss 4.2.1 @ http://localhost:8081
[cactus]
-
[cactus] Deploying [/Users/temp/build/test.war] to
[/Users/servers/jboss4.2/server/all/deploy]...
[cactus] JBoss 4.2.1 starting...
[cactus] JBoss 4.2.1 started on port [8081]
BUILD FAILED
/User/src/test.xml:1052: Failed to start the container after more than
[18] ms. Trying to connect to the [
http://localhost:8081/test/ServletRedirector?Cactus_Service=RUN_TEST] test
URL yielded a [-1] error code. Please run in debug mode for more details
about the error.
So even though the container started, I am getting a failed to start
container error and the tests do not run after this. Any ideas?
Once again, any help is greatly appreciated.
Thanks
--
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
Re: Question about cactus 1.8 and jboss 4.2
Yes I checked my web.xml file. My tests seem to be cactified and deployed
correctly with the redirector definitions. However I still see that error. I
have looked at the cactus samples before, but I will look again to make sure
I am not missing anything. Thanks for your help.
PS: Thanks for pointing out the fileset filter mistake. I have fixed that as
well.
On Mon, Dec 29, 2008 at 10:51 AM, Petar Tahchiev paranoia...@gmail.comwrote:
Hi Neha,
this error happens when there was something wrong with the war
that you deploy. Make sure that the test.war you
try to deploy is cactified and it's web.xml contains the servletRedirector
definitions.
Also one more thing that struck me in your build.xml:
Are you sure that you have something selected here:
fileset dir=${src.test.dir}
include name=**/*Test.class/
/fileset
Do you really have .class files in your src directory?
Cheers, Petar.
P.S. Have a look at the sample applications that come with cactus. Try
to run them and in case it was possible look for the differences between
your configuration and the sample one.
2008/12/29, Neha Agarwal neha...@gmail.com:
Never mind about starting the container. I was able to fix that. It was a
problem with my build file since I was not poitning to the existing
installation of the container.
The container starts up correctly now, but cactus does not seem to be
running the tests. Here is the output from my console.
test.cactus:
[cactus]
-
[cactus] Parsed JBoss version = [4.2.1]
[cactus] Running tests against JBoss 4.2.1 @ http://localhost:8081
[cactus]
-
[cactus] Deploying [/Users/temp/build/test.war] to
[/Users/servers/jboss4.2/server/all/deploy]...
[cactus] JBoss 4.2.1 starting...
[cactus] JBoss 4.2.1 started on port [8081]
BUILD FAILED
/User/src/test.xml:1052: Failed to start the container after more than
[18] ms. Trying to connect to the [
http://localhost:8081/test/ServletRedirector?Cactus_Service=RUN_TEST]
test
URL yielded a [-1] error code. Please run in debug mode for more details
about the error.
So even though the container started, I am getting a failed to start
container error and the tests do not run after this. Any ideas?
Once again, any help is greatly appreciated.
Thanks
--
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
