Help with Remote EJB call standalone java program.

[foutjo]

I am in the process of migrating from EAP 6.2 to WIldfly 9.0.

We have a standalone java program that calls a SLSB running on the Wildfly 9.0 server.

All of my settings are the same from when running with EAP 6.2.

After migrating to Wildfly 9.0 when running my standalone java program it is unable to connect to the SLSB on the wildfly server.

Based on the following stack trace it looks like the lookup of the SLSB works fine. 

To me it looks like its the actual call to the SLSB method that is causing the connection error.

07:36:46,829 Thread-1   WARN  - Could not register a EJB receiver for connection to localhost:4447 [org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector]

java.lang.RuntimeException: java.net.ConnectException: Connection refused: no further information

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

  at org.jboss.ejb.client.remoting.ConnectionPool.getConnection(ConnectionPool.java:80)

  at org.jboss.ejb.client.remoting.RemotingConnectionManager.getConnection(RemotingConnectionManager.java:51)

  at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.setupEJBReceivers(ConfigBasedEJBClientContextSelector.java:158)

  at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.getCurrent(ConfigBasedEJBClientContextSelector.java:115)

  at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.getCurrent(ConfigBasedEJBClientContextSelector.java:47)

  at org.jboss.ejb.client.EJBClientContext.getCurrent(EJBClientContext.java:279)

  at org.jboss.ejb.client.EJBClientContext.requireCurrent(EJBClientContext.java:289)

  at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:178)

  at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)

  at com.sun.proxy.$Proxy2.processAdminTran(Unknown Source)

  at com.lidp.jem.handler.JEMMessageHandler.callServerListener(JEMMessageHandler.java:1124)

  at com.lidp.jem.handler.JEMMessageHandler.processThread(JEMMessageHandler.java:917)

  at com.lidp.listener.client.Client_Listener$1.run(Client_Listener.java:103)

  at java.lang.Thread.run(Unknown Source)

Here is the code from my client:

      try

       {

          RemoteEJBClient remoteEJBClient = new RemoteEJBClient();

          transProcessor = (TransProcessorINF)remoteEJBClient.lookupRemoteStatelessBean();

-->          adminReturned = transProcessor.processAdminTran(adminObject); 

       }

       catch (Exception e)

       {

It fails on the method call line.

Hopefully someone can give me some hints on what I might have to change with the migration from EAP 6.2 to Wildfly 9.

Any help is greatly appreciated.

[jaysensharma]

Please see [WARN  - Could not register a EJB receiver for connection to localhost:4447 ]   WildFly does not use this port unlike JBossAS7 (EAP6).

If you are using remoting based approach:

In WildFLy the protocol need to be   http-remoting://localhost:8080

props.put(Context.PROVIDER_URL, "http-remoting://localhost:8080");

Please see:

https://github.com/jaysensharma/MiddlewareMagicDemos/blob/master/WildFly/EJB/StatelessLoadTestInWilfFly9/src/StandaloneClient.java

If you are using EJB CLient API based approach then you may need to use the jboss-ejb-client.properties like following:

remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false
remote.connections=default
remote.connection.default.host=localhost
remote.connection.default.port = 8080
remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false

Also please have a look at: Remote JNDI Reference Update Draft - WildFly 9 - Project Documentation Editor

Regards

Jay SenSharma

[foutjo]

That worked Jay.   Thanks so much for your help.