cargo:start doesn't work with JBoss EAP 5.1

You need to provide more info! What's the error message, etc.

Hi,

sorry, I was in a hurry when I reported.

There's no error message - it simply times out.

[20:19:56.826][info][neLocalConfiguration] Configuring JBoss using the [default] server configuration
[20:19:56.838][info][talledLocalContainer] Parsed JBoss version = [5.1.0]
[20:19:56.871][info][stalledLocalDeployer] Deploying [/home/ondra/work/JOPRembedded/embjopr-svn-trunk/jsfunit/target/admin-console-jsfunit.war] to [target/jboss5x/deploy]...
[20:20:01.042][info][talledLocalContainer] JBoss 5.1.0 starting...

I'd set log level to DEBUG but I haven't found how: http://cargo.codehaus.org/Maven2+Plugin+Reference+Guide

IIRC, JBoss AS plugin starts by calling run.sh from Ant, and then checks if it's started by HTTP requests to some jsp or such.
The JBoss AS process is not started at all, so the problem is most probably in the code calling run.sh.
I am not aware of any changes in EAP which would break the run.sh API.

Stacktrace from maven log attached, but it only informs about the fact that it could not reach that HTML page.

Cannot reproduce with CARGO 1.0.6.

Ali, did you verify with JBoss EAP? That's a different beast compared to jboss community app server. If not, please reopen.

You're probably right, let's reopen it then

Ondrej, can you please attach JBoss' logs so we can see what the problem really is?

I did a quick test with a project using JBoss EAP 5.0.0.GA and switched to EAP 5.1.0. It worked without any problems (using Cargo 1.0.6).

So Anders you did verify with EAP

Ondrej, did you try with Cargo 1.0.6?

Yes, JBoss EAP 5.1.0 (GA).

Cool 8)

So I guess if Ondrej doesn't reply we can assume this one closed...

Anders, could you also try with Cargo 1.0.2 or do you prefer joining the saturday evening parties?

I don't have the project with me, it's a work project. I actually didn't notice he reported towards 1.0.2.

Ondrej, if you could check if you can reproduce with Cargo 1.0.6 and EAP 5.1.0 GA (not CR) it would be great. We'll close this ticket in a week as can't reproduce if we don't hear anything (you can always ask us to reopen later).

This cannot be reproduced on Cargo 1.0.6; and therefore has (probably) already been fixed since version 1.0.2 (the one used by the reporter). Moreover, no reply received from reporter since long time. Hence, closing the ticket.