[JBoss7] Remote EJB3 calls from spawned thread

[ndario]

I have simple remote ejb client that calls remote stateless beans. There is security enabled on the server.

All is well for single threrad, authentication and authorization and remote call works:

final Properties jndiProperties = new Properties();

jndiProperties.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming");

jndiProperties.put(Context.SECURITY_PRINCIPAL, "XXX");

jndiProperties.put(Context.SECURITY_CREDENTIALS, "XXX");

jndiProperties.put("jboss.naming.client.ejb.context", true);

jndiProperties.put(Context.PROVIDER_URL, "remote://serverIP:4447");

jndiProperties.put("jboss.naming.client.connect.options.org.xnio.Options.SASL_POLICY_NOPLAINTEXT", "false");

jndiProperties.put(Context.INITIAL_CONTEXT_FACTORY, org.jboss.naming.remote.client.InitialContextFactory.class.getName());

Context context = new InitialContext(jndiProperties);

RemoteService rs = (RemoteService)context.lookup("ejb:app/app-ejb-1.0-SNAPSHOT/RemoteBean!com.app.services.remoting.RemoteService");

rs.myMethod();

So far so good, authentication is OK and remote call works.

However, If i make remote call from another thread, like from event handler in GUI application, I get:

java.lang.IllegalStateException: No EJB receiver available for handling [appName:app,modulename:app-ejb-1.0-SNAPSHOT,distinctname:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@12a55aa

I realised that this is security-related problem and reason for this is that "EJB security context" is thread-local-var and it is missing in all spawned threads. It is present in the main thread and remoting works. Am I right?

What am I supposed to do to make secured EJB remote calls from event handlers?

[jaikiran]

In that other thread, are you doing the lookup again and then invoking or are you just invoking on that bean proxy that you previously obtained?

Looking up and invoking in that other thread should work.

[ndario]

Thanks Jaikiran,

quite right, if I lookup and invoke in the thread, it works.

BUT, I also have to create a 'new InitialContext', and make lookup on it. So for every remote call I have to go through all "createContext-lookup-remoteCall-close" procedure?  Is it possible to make authentication cacheing on client?

What would be the best practice for secured remote calls?

Thanks.

[jaikiran]

In this specific case, there should be no reason why the proxy shouldn't be usable in a separate thread. The reason I asked you to try the lookup + invoke in a separate thread is because after looking at the remote-naming project code, I saw a potential bug which you have now confirmed. We'll need to fix that.

By the way, have you read this article which explains what approach to use for remote EJB lookups against AS7 https://docs.jboss.org/author/display/AS71/Remote+EJB+invocations+via+JNDI+-+EJB+client+API+or+remote-naming+project? remote-naming approach isn't the recommended one.

[ndario]

I did read "Remote EJB invocations via JNDI - EJB client API or remote-naming project", couple of times actually , and I was sure I am using "EJB client" API and not remote-naming. Is it not the case?

I believed that ejb:/ naming scheme is for EJB clients, I followed lookupRemoteStatelessCalculator() example. Am I missing something?

[olli24]

Hi there.

We are migrating from JBoss5 to JBoss7 and faced the same problem.

Calling an EJB method from a different Thread context, causing a java.lang.IllegalStateException: No EJB receiver available for node name

Under JBoss5 this has been working.

Can someone confirm that this issue is bug of JBoss7.1.1 which will be fixed?

So far I didn’t find anything in the Issue Tracker about this problem.

Or are there any InitialContext properties availble to allow this?

Thanks.

Update:

My problem is solved. See

https://community.jboss.org/thread/204139?start=0&tstart=0