Problems EJB invocations from a remote server instance

[julio.silveira]

Hi Guys,

I'm trying to implement the EJB remote connection between two servers JBoss7, using the documentation described in this document:

https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+server+instance

I did everything as described in this document but got the following error in the application deployment process:

...

14:50:54,507 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10) MSC00001: Failed to start service jboss.ejb3.dd-based-ejb-client-context."Sicop.war": org.jboss.msc.service.StartException in service jboss.ejb3.dd-based-ejb-client-context."Sicop.war": Failed to start service

at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]

at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]

Caused by: java.lang.RuntimeException: Operation failed with status WAITING

at org.jboss.ejb.client.remoting.IoFutureHelper.get(IoFutureHelper.java:93)

at org.jboss.as.ejb3.remote.DescriptorBasedEJBClientContextService.createRemotingConnections(DescriptorBasedEJBClientContextService.java:124)

at org.jboss.as.ejb3.remote.DescriptorBasedEJBClientContextService.start(DescriptorBasedEJBClientContextService.java:86)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

... 3 more

14:50:54,520 ERROR [org.jboss.remoting.remote.connection] (Remoting "zeus" read-1) JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed

14:50:54,720 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "Sicop.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.ejb3.dd-based-ejb-client-context.\"Sicop.war\"" => "org.jboss.msc.service.StartException in service jboss.ejb3.dd-based-ejb-client-context.\"Sicop.war\": Failed to start service"}}

14:50:54,739 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment Sicop.war in 19ms

14:50:54,741 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report

JBAS014777:   Services which failed to start:      service jboss.ejb3.dd-based-ejb-client-context."Sicop.war": org.jboss.msc.service.StartException in service jboss.ejb3.dd-based-ejb-client-context."Sicop.war": Failed to start service

14:50:54,743 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.ejb3.dd-based-ejb-client-context.\"Sicop.war\"" => "org.jboss.msc.service.StartException in service jboss.ejb3.dd-based-ejb-client-context.\"Sicop.war\": Failed to start service"}}}}

I ask this is a bug? Do you have any workaround to solve this problem? What other way to do remote connection between servers JBoss EJB 7?

thank you

Julio

[markus78]

It is a bug, you need to start the destination server first to be able to deploy on the client server. There is a Jira issue for this.

It's this one

https://issues.jboss.org/browse/AS7-3820

[julio.silveira]

Hi markus78,

the target server already started so do not fit into this problem, the server is configured with SASL security, for the JBoss client to connect to JBoss server does not have to pass the credentials? But the documentation did not see how to pass these credentials, the error returned by the client is not connecting to the server for invalid credentials, such as sending credentials to the JBoss Server?

Thanks

[schnabeltier]

Hi Markus, hi Julio,

i have the same problem - following the example and starting the destination server first does not help.

I get:

Failed to start service jboss.ejb3.dd-based-ejb-client-context."Inventory.Sync.ear": org.jboss.msc.service.StartException in service jboss.ejb3.dd-based-ejb-client-context."Inventory.Sync.ear": Failed to start service

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_27]

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_27]

    at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_27]

Caused by: java.lang.RuntimeException: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed

[jaikiran]

qqq qqqq, your's is a slightly different problem. Please create a separate thread for that.

[jaikiran]

Julio, please add more details including how you start the server and what exactly your configurations in the standalone*.xml and the jboss-ejb-client.xml look like. Also are these servers running on the same machine?

[julio.silveira]

Hi jaikiran,

servers running on different machines, the environment is configured using Hosted Control and Domain Control, with four instances of four machines, forming four clusters with one instance per machine according to the drawing attached.

EJBs to be accessed remotely instances are published in the "production-services-x" in the cluster and web applications that need to lookup remote instances are published in the "production-web-x" in the cluster. Before configuring the instances "production-web-x" to do lookup in remote instances "production-services-x", I did a test on a standalone instance trying to lookup the instance "production-services-one" IP192.168.0.223 , according to documentation. Configuration for Standalone instance to lookup the remote instance "production-services-one" is in the file "standalone-full.xml" in link. Also added the folder configuration of Domain Control and one of the machines Hosted Control, see DC-config.zip,HC-config.zip.

http://3layer.com.br/jboss7/DC-config.zip

http://3layer.com.br/jboss7/HC-config.zip

http://3layer.com.br/jboss7/jboss-ejb-client.xml

http://3layer.com.br/jboss7/standalone-full.xml

And if you need any more information about the environment just ask.

thank you

[julio.silveira]

Hi guys,

any news on my problem?

thank you

[jaikiran]

Julio, I missed your previous reply. I'll take a look at this today.

[forretress]

Same dilemma here .... i was looking for a way to register the credentials in the standalone-full.xml

[julio.silveira]

Hi jaikiran pai,

any news on my problem?

sds

[milenkovic.m]

Hi Julio,

I had similar problem with the Jboss AS7.1.0.Filan domain configuration. 

Can you please check if your remote (Hosted Controler) host.xml has folowing element:

            <http-interface security-realm="ManagementRealm">

                <socket interface="management" port="${jboss.management.http.port:9990}"/>

            </http-interface>

it the element exists, remove it, restart domain and retry

[jaikiran]

Sorry everyone, I haven't been able to write up the documentation for this. But 7.1.1.Final got released yesterday and I finally have some time to start writing up the docs and I expect this documentation to be available this week. Thank you for your patience.

[bob_walker99]

Hi,

Is this definitely just a documentation issue? I'm experiencing the same issue and with a little work, can provide a relatively small test case, if it's useful?

Best regards,

Bob Walker

[forretress]

Hi jaikiran

any news on the documentation ?