I am new to cargo, but I think this is stopping my progress as well. I have tried the 1.0.1 snapshot as well, with no difference. In addition, the port for communication seems to be hardcoded for 1299, and doesn't respect having a different admin port passed to it:
<target name="stopJboss">
<echo message="JBoss is located at ${JBOSS_HOME}" />
<cargo containerId="jboss42x" home="${JBOSS_HOME}" output="./output.log"
log="./cargo.log" action="stop">
<configuration type="existing" home="${JBOSS_HOME}/server/default">
<property name="cargo.remote.username" value="xxxx"/>
<property name="cargo.remote.password" value="xxxx"/>
<property name="cargo.rmi.port" value="1099"/>
</configuration>
</cargo>
</target>
Exception is:
Exception in thread "main" java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console
at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:97)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
...
________________________________________
From: nicolas de loof [mailto:
nicolas.deloof@...]
Sent: Wednesday, May 13, 2009 9:26 AM
To:
user@...
Subject: Re: [cargo-user] cargo to setup JBoss EAP
The conf override works fine, bu this doesn't fix my issue :
I can connect to jboss admin console but a login/password is expected. The plugin doesn't seem to set it, and the org.jboss.Shutdow command fails.
(java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console)
I'll patch the AS zip, seems simplier :)
Cheers,
Nicolas
2009/5/13 nicolas de loof <
nicolas.deloof@...>
Right,
I just notice a typo on
http://cargo.codehaus.org/Custom+File+ConfigurationsThe maven sample is missing the closing </file> "/"
2009/5/13 Matt Wringe <
mwringe@...>
On Wed, 2009-05-13 at 16:04 +0200, nicolas de loof wrote:
> Nice solution, I'll test this
FYI, there was a couple of issues with the custom files on the 1.0
release, so you might want to try with the 1.0.1-SNAPSHOT if you run
into issues.
>
> Thanks a lot for quick reply :D
>
>
> 2009/5/13 Matt Wringe <
mwringe@...>
> On Wed, 2009-05-13 at 15:48 +0200, nicolas de loof wrote:
> > Hi guys,
> >
> >
> > mi cargo configuration runs fine with Jboss 4.2.3,
> > I now would like to use the exact target platform : JBoss
> EAP
> > 4.2.0.GA-CP04 (that's a funy name, isn't it ?)
> >
> >
> > All runs fine (container setup, app get deployed, test
> pass..) but
> > cargo-stop fails because this EAP version *by default* has
> the admij
> > user disabled in jmx-console-users.properties.
>
>
> Is this a standalone cargo configuration?
> If its a standlone one, then you can overwrite the
> jmx-console-users.properties file with the one that you want
> to use.
>
> See
http://cargo.codehaus.org/Custom+File+Configurations>
> >
> > Is there any way to override such configuration
> > from cargo-maven-plugin ?
> >
> >
> > Best regards,
> > Nicolas
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>
http://xircles.codehaus.org/manage_email>
>
>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email