Eclipse Community Forums: Hudson » Deploy to JBoss 7.x fails

Home » Archived » Hudson » Deploy to JBoss 7.x fails(Authentication failed: all available authentication mechanisms failed)

Deploy to JBoss 7.x fails [message #985934]

Fri, 16 November 2012 13:03

Eclipse User

Morning all ...

To open, we originally setup Hudson to deploy to a Tomcat7 server, and all works like a charm, but the developers have decided they wish to use features available in JBoss 7.x, so we are migrating our environment over to it.

I've got JBoss 7.x standalone up and running, and can access the console by going to http:// server:8080 -> Application Console ... I used the add-user.sh script to create a user in both the Management and Application Realms (I believe its only the Application Realm I need though?) and then proceeded to reconfigure my project in Hudson, with 'JBoss URL' set to http:// server and JMX Port set to 9999 ...

If I go there via my browser, it connects, I get a few 'graphic characters' and then the IP of the remote server ...

When I do a 'Build Now' in Hudson, it can't deploy though, with a fairly long stacktrace, but I believe the relevant part of it is:

"Authentication failed: all available authentication mechanisms failed"

I've searched Google for every combination I can think of, and am coming up dry ... I'm suspecting I've missed a setup / configuration option on the JBoss side, but not a clue as to what it is, or where to look for an answer ...

Suggestions / help ... ?

Thanks ...

Re: Deploy to JBoss 7.x fails [message #985939 is a reply to message #985934]

Fri, 16 November 2012 13:17

Eclipse User

Hi Marc, are you trying to deploy using deploy plugin?

Re: Deploy to JBoss 7.x fails [message #985940 is a reply to message #985939]

Fri, 16 November 2012 13:22

Eclipse User

Yes, and made sure I was upgraded to the newest version ...

Re: Deploy to JBoss 7.x fails [message #985941 is a reply to message #985940]

Fri, 16 November 2012 13:33

Eclipse User

What version of hudson, and jboss 7.x specifically are you using?

[Updated on: Fri, 16 November 2012 13:44] by Moderator

Re: Deploy to JBoss 7.x fails [message #985947 is a reply to message #985941]

Fri, 16 November 2012 14:47

Eclipse User

Sorry, should have known to include all of that Sad

JBoss 7.1.1.Final
Hudson 2.2.1
Deploy Plugin 1.8
OpenJDK 7.6.24 (both on JBoss and Hudson Servers ... separate machines)

Re: Deploy to JBoss 7.x fails [message #985952 is a reply to message #985947]

Fri, 16 November 2012 15:46

Eclipse User

Make sure security-realm="ManagementRealm" is set in the remote tag of your host.xml file.

[Updated on: Fri, 16 November 2012 15:53] by Moderator

Re: Deploy to JBoss 7.x fails [message #985958 is a reply to message #985952]

Fri, 16 November 2012 16:02

Eclipse User

k, so this may be where I'm doing things wrong ... the only host.xml I find is in domain/configuration ... I'm running standalone ... so, for what I'm trying to do, should I be using domain? or just copy host.xml -> standalone?

I had thought that domain was for when / if I had multiple jboss servers, which was why I was running standalone for now ...

thx

Re: Deploy to JBoss 7.x fails [message #985963 is a reply to message #985958]

Fri, 16 November 2012 16:10

Eclipse User

Note that I just checked my standalone.xml file, and it does appear to have it:

    <management>
        <security-realms>
            <security-realm name="ManagementRealm">
                <authentication>
                    <properties path="mgmt-users.properties" relative-to="jboss.server.config.dir"/>
                </authentication>
            </security-realm>
            <security-realm name="ApplicationRealm">
                <authentication>
                    <properties path="application-users.properties" relative-to="jboss.server.config.dir"/>
                </authentication>
            </security-realm>
        </security-realms>
        <management-interfaces>
            <native-interface security-realm="ManagementRealm">
                <socket-binding native="management-native"/>
            </native-interface>
            <http-interface security-realm="ManagementRealm">
                <socket-binding http="management-http"/>
            </http-interface>
        </management-interfaces>
    </management>

Re: Deploy to JBoss 7.x fails [message #985988 is a reply to message #985963]

Fri, 16 November 2012 20:11

Eclipse User

Would it be possible to see the entire standalone.xml file? You can email it to me (schristou88@gmail.com).

Re: Deploy to JBoss 7.x fails [message #986274 is a reply to message #985988]

Mon, 19 November 2012 11:56

Eclipse User

Sent it over the weekend, let me know if you didn't receive and I'll resend ... it seemed a wee bit long to post it to here ...

thx

Re: Deploy to JBoss 7.x fails [message #988409 is a reply to message #986274]

Thu, 29 November 2012 14:22

Eclipse User

Deploy Plugin has been update to 1.9 to resolve this issue.

Re: Deploy to JBoss 7.x fails [message #1020314 is a reply to message #988409]

Sun, 17 March 2013 18:33

Eclipse User

It seems the issue has not been fixed in new version 1.9. Here below is my obeservation;

1). version 1.8, it gave the error
===================================================================
Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:315)
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:214)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:180)
at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
at org.xnio.nio.NioHandle.run(NioHandle.java:90)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:184)
at ...asynchronous invocation...(Unknown Source)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:337)
at org.jboss.as.protocol.ProtocolChannelClient.connect(ProtocolChannelClient.java:125)
at org.jboss.as.protocol.ProtocolChannelClient.connectSync(ProtocolChannelClient.java:134)
... 30 more

2). after upgraded to version 1.9, now getting new error
===================================================================
org.codehaus.cargo.util.CargoException: Deployment action ADD failed
at org.codehaus.cargo.tools.jboss.JBossDeployer.executeAction(JBossDeployer.java:145)
at org.codehaus.cargo.tools.jboss.JBossDeployer.deploy(JBossDeployer.java:84)
at org.codehaus.cargo.container.jboss.JBoss5xRemoteDeployer.deploy(JBoss5xRemoteDeployer.java:212)
at org.codehaus.cargo.container.spi.deployer.AbstractDeployer.redeploy(AbstractDeployer.java:212)
at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:62)
at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:92)
at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:75)
at hudson.FilePath.act(FilePath.java:791)
at hudson.FilePath.act(FilePath.java:773)
at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:75)
at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:45)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:51)
at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:646)
at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:624)
at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:811)
at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:566)
at hudson.model.Run.run(Run.java:1414)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:414)
at hudson.model.ResourceController.execute(ResourceController.java:81)
at hudson.model.Executor.run(Executor.java:137)

Re: Deploy to JBoss 7.x fails [message #1020851 is a reply to message #1020314]

Mon, 18 March 2013 23:25

Eclipse User

What version of jboss as are you deploying to (According to the stack trace it's version 5x)?

Re: Deploy to JBoss 7.x fails [message #1021248 is a reply to message #1020851]

Tue, 19 March 2013 14:22

Eclipse User

I am also wonderring the Jboss verion in the error log, the log was showing as it as, but it was from HUDSON log, not my JBoss log.

This is my environment:
- My deployment target server: "jboss-as-7.1.1.Final" in Linux
- HUDSON: version 3 running in Tomcat 6 at the same box as Jboss above.
Deploy Plugin: HUDSON 3 installed the plugin in version 1.8 with following libs:
cargo-core-api-container-1.1.2.jar
cargo-core-api-generic-1.1.2.jar
cargo-core-api-module-1.1.2.jar
cargo-core-api-util-1.1.2.jar
cargo-core-container-glassfish-1.1.2.jar
cargo-core-container-jboss-1.1.2.jar
cargo-core-container-tomcat-1.1.2.jar
cargo-core-container-weblogic-1.1.2.jar

With version 1.8, it gave my first error in my previous message, after I downloaded version 1.9, it gave me the second error. Then I also tried updated cargo related libs to version 1.3.3 manually, it doesn't help any.

Thanks
Edwin

Previous Topic:	Error when using Git
Next Topic:	Hudson builds due to CVSROOT mismatch

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Jul 17 01:24:07 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter