1 2 3 Previous Next 33 Replies Latest reply on Nov 13, 2012 7:49 AM by jaikiran Branched from an earlier discussion.

EJBCLIENT-34 fails for invocations on EJB 2.x views returned by home interface

jonatan.guillen Nov 1, 2012 6:57 AM

I compile 1.0.13.Final version and when execute the lookup I have and error:

DEBUG logging - Logging Provider: org.jboss.logging.Log4jLoggerProvider

DEBUG EJBClientPropertiesLoader - Looking for jboss-ejb-client.properties using classloader sun.misc.Launcher$AppClassLoader@35ce36

DEBUG ConfigBasedEJBClientContextSelector - EJB client context org.jboss.ejb.client.EJBClientContext@15b7986 will have no EJB receivers associated with it since there was no EJB client configuration available to create the receivers

DEBUG PropertiesBasedEJBClientConfiguration - endpoint.create.options. has the following options {}

DEBUG PropertiesBasedEJBClientConfiguration - remote.connectionprovider.create.options. has the following options {org.xnio.Options.SSL_ENABLED=>false}

DEBUG PropertiesBasedEJBClientConfiguration - remote.connection.default.connect.options. has the following options {org.xnio.Options.SASL_POLICY_NOANONYMOUS=>false}

DEBUG PropertiesBasedEJBClientConfiguration - remote.connection.default.channel.options. has the following options {}

DEBUG PropertiesBasedEJBClientConfiguration - Connection org.jboss.ejb.client.PropertiesBasedEJBClientConfiguration$RemotingConnectionConfigurationImpl@56a499 successfully created for connection named default

DEBUG PropertiesBasedEJBClientConfiguration - No clusters configured in properties

INFO xnio - XNIO Version 3.0.4.GA-redhat-1

INFO nio - XNIO NIO Implementation Version 3.0.4.GA-redhat-1

INFO remoting - JBoss Remoting version 3.2.8.GA-redhat-1

DEBUG nio - Started channel thread 'Remoting "config-based-ejb-client-endpoint" read-1', selector sun.nio.ch.WindowsSelectorImpl@100ab23

DEBUG nio - Started channel thread 'Remoting "config-based-ejb-client-endpoint" write-1', selector sun.nio.ch.WindowsSelectorImpl@11121f6

DEBUG RemotingConnectionEJBReceiver - Channel Channel ID a547e887 (outbound) of Remoting connection 00f0c0d3 to /192.168.6.192:4447 opened for context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1cbfe9d, receiver=Remoting connection EJB receiver [connection=Remoting connection <a31e1b>,channel=jboss.ejb,nodename=node01]} Waiting for version handshake message from server

INFO remoting - EJBCLIENT000017: Received server version 1 and marshalling strategies [river]

INFO remoting - EJBCLIENT000013: Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1cbfe9d, receiver=Remoting connection EJB receiver [connection=Remoting connection <a31e1b>,channel=jboss.ejb,nodename=node01]} on channel Channel ID a547e887 (outbound) of Remoting connection 00f0c0d3 to /192.168.6.192:4447

DEBUG RemotingConnectionEJBReceiver - Received module availability report for 20 modules

DEBUG RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='', moduleName='mod1', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1cbfe9d, receiver=Remoting connection EJB receiver [connection=Remoting connection <a31e1b>,channel=jboss.ejb,nodename=node01]}

DEBUG RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='', moduleName='mod2', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1cbfe9d, receiver=Remoting connection EJB receiver [connection=Remoting connection <a31e1b>,channel=jboss.ejb,nodename=node01]}

DEBUG RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='', moduleName='mod3', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1cbfe9d, receiver=Remoting connection EJB receiver [connection=Remoting connection <a31e1b>,channel=jboss.ejb,nodename=node01]}

DEBUG RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='', moduleName='mod4', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1cbfe9d, receiver=Remoting connection EJB receiver [connection=Remoting connection <a31e1b>,channel=jboss.ejb,nodename=node01]}

DEBUG RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='', moduleName='mod5', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1cbfe9d, receiver=Remoting connection EJB receiver [connection=Remoting connection <a31e1b>,channel=jboss.ejb,nodename=node01]}

DEBUG RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='', moduleName='mod6', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1cbfe9d, receiver=Remoting connection EJB receiver [connection=Remoting connection <a31e1b>,channel=jboss.ejb,nodename=node01]}

DEBUG RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='', moduleName='mod7', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1cbfe9d, receiver=Remoting connection EJB receiver [connection=Remoting connection <a31e1b>,channel=jboss.ejb,nodename=node01]}

DEBUG RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='', moduleName='mod8', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1cbfe9d, receiver=Remoting connection EJB receiver [connection=Remoting connection <a31e1b>,channel=jboss.ejb,nodename=node01]}

DEBUG RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='', moduleName='mod9', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1cbfe9d, receiver=Remoting connection EJB receiver [connection=Remoting connection <a31e1b>,channel=jboss.ejb,nodename=node01]}

DEBUG RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='', moduleName='mod10', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1cbfe9d, receiver=Remoting connection EJB receiver [connection=Remoting connection <a31e1b>,channel=jboss.ejb,nodename=node01]}

DEBUG RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='', moduleName='mod11', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1cbfe9d, receiver=Remoting connection EJB receiver [connection=Remoting connection <a31e1b>,channel=jboss.ejb,nodename=node01]}

DEBUG RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='', moduleName='mod12', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1cbfe9d, receiver=Remoting connection EJB receiver [connection=Remoting connection <a31e1b>,channel=jboss.ejb,nodename=node01]}

DEBUG RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='', moduleName='mod13', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1cbfe9d, receiver=Remoting connection EJB receiver [connection=Remoting connection <a31e1b>,channel=jboss.ejb,nodename=node01]}

DEBUG RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='', moduleName='mod14', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1cbfe9d, receiver=Remoting connection EJB receiver [connection=Remoting connection <a31e1b>,channel=jboss.ejb,nodename=node01]}

DEBUG RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='', moduleName='mod15', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1cbfe9d, receiver=Remoting connection EJB receiver [connection=Remoting connection <a31e1b>,channel=jboss.ejb,nodename=node01]}

DEBUG RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='', moduleName='mod16', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1cbfe9d, receiver=Remoting connection EJB receiver [connection=Remoting connection <a31e1b>,channel=jboss.ejb,nodename=node01]}

DEBUG RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='', moduleName='mod17', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1cbfe9d, receiver=Remoting connection EJB receiver [connection=Remoting connection <a31e1b>,channel=jboss.ejb,nodename=node01]}

DEBUG RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='', moduleName='mod18', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1cbfe9d, receiver=Remoting connection EJB receiver [connection=Remoting connection <a31e1b>,channel=jboss.ejb,nodename=node01]}

DEBUG RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='', moduleName='mod19', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1cbfe9d, receiver=Remoting connection EJB receiver [connection=Remoting connection <a31e1b>,channel=jboss.ejb,nodename=node01]}

DEBUG RemotingConnectionEJBReceiver - Registering module EJBModuleIdentifier{appName='', moduleName='mod20', distinctName=''} availability for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1cbfe9d, receiver=Remoting connection EJB receiver [connection=Remoting connection <a31e1b>,channel=jboss.ejb,nodename=node01]}

DEBUG ChannelAssociation - Unsupported message received with header 0xffffffff

DEBUG ConfigBasedEJBClientContextSelector - Registered 1 remoting EJB receivers for EJB client context org.jboss.ejb.client.EJBClientContext@1cbfe9d

INFO client - JBoss EJB Client version 1.0.13.Final

DEBUG EJBClientContext - org.jboss.ejb.client.RandomDeploymentNodeSelector@1b000e7 deployment node selector selected node01 node for appname=,modulename=mod12,distinctname=

Exception in thread "main" java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:mod12, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@1950198

at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:674)

at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116)

at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)

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

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

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

at $Proxy1.read(Unknown Source)

at com.test.NewRemoteClient.epCall(NewRemoteClient.java:49)

at com.test.NewRemoteClient.main(NewRemoteClient.java:34)

DEBUG RemotingCleanupHandler - Closing Remoting connection <a31e1b>

DEBUG ChannelAssociation - Closing channel Channel ID a547e887 (outbound) of Remoting connection 00f0c0d3 to /192.168.6.192:4447

INFO remoting - EJBCLIENT000016: Channel Channel ID a547e887 (outbound) of Remoting connection 00f0c0d3 to /192.168.6.192:4447 can no longer process messages

DEBUG ChannelAssociation - Registering a re-connect handler org.jboss.ejb.client.remoting.EJBClientContextConnectionReconnectHandler@bcda2d for broken channel Channel ID a547e887 (outbound) of Remoting connection 00f0c0d3 to /192.168.6.192:4447 in EJB client context org.jboss.ejb.client.EJBClientContext@1cbfe9d

DEBUG RemotingConnectionEJBReceiver - Closing channelChannel ID a547e887 (outbound) of Remoting connection 00f0c0d3 to /192.168.6.192:4447

DEBUG RemotingCleanupHandler - Closing endpoint "config-based-ejb-client-endpoint" <2af081>

1. Re: Testing EJBCLIENT-34

jaikiran Oct 31, 2012 10:59 AM (in response to jonatan.guillen)

What does your code look like?
Actions
2. Re: Testing EJBCLIENT-34

jonatan.guillen Oct 31, 2012 11:04 AM (in response to jaikiran)

final Properties jndiProps = new Properties();
jndiProps.put("org.jboss.ejb.client.scoped.context", true);
jndiProps.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming");
final String connectionName = "default"
jndiProps.put("remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED", "false");
jndiProps.put("remote.connections", connectionName);
jndiProps.put("remote.connection." + connectionName + ".host", "192.168.6.192");
jndiProps.put("remote.connection." + connectionName + ".port", "4447");
jndiProps.put("remote.connection." + connectionName + ".username", "user");
jndiProps.put("remote.connection." + connectionName + ".password", "pass");
jndiProps.put("remote.connection." + connectionName + ".connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS", "false");

final Context context = new InitialContext(jndiProps);
String moduleName = "mod12";
String beanName = "bean12";
String viewClassName = Ejb12Home.class.getName();
final Ejb12Home ejbHome = (Ejb12Home) context.lookup("ejb:/"+ moduleName + "/" + beanName + "!" + viewClassName);

Ejb12Remote remote = ejbHome.create();

Use of the Ejb12Remote.
Actions
3. Re: Testing EJBCLIENT-34

jaikiran Oct 31, 2012 11:39 AM (in response to jonatan.guillen)

Are you sure that's the exact code? It doesn't match the stacktrace you posted. The stacktrace shows some call to read() method which isn't shown in the code you posted.
Actions
4. Re: Testing EJBCLIENT-34

jonatan.guillen Oct 31, 2012 11:43 AM (in response to jaikiran)

Yes, with

Ejb12Remote remote = ejbHome.create();

I execute the function read.

remote.read(--,--);

It's a operation of my EJB.
Actions
5. Re: Testing EJBCLIENT-34

jaikiran Oct 31, 2012 10:19 PM (in response to jonatan.guillen)

I see what's going on. It appears to be broken for EJB 2.x views. I'll add a fix soon. Thanks for reporting. In the meantime, if your application has EJB 3.x views, then give those a try, those should be functional.
Actions
6. Re: Testing EJBCLIENT-34

jaikiran Nov 1, 2012 7:00 AM (in response to jaikiran)

Here's the JIRA for the bug https://issues.jboss.org/browse/EJBCLIENT-51. I've also pushed a snapshot (1.0.14.Final-SNAPSHOT) https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/jboss-ejb-client/1.0.14.Final-SNAPSHOT/jboss-ejb-client-1.0.14.Final-20121101.105040-1.jar containing a fix for this. Can you update your client classpath to use that jar and give it a try? Let us know if it fixes your issue.
Actions
7. Re: Testing EJBCLIENT-34

jonatan.guillen Nov 5, 2012 2:24 AM (in response to jaikiran)

It works, Thanks.
When can I get access to a nightly build?
Actions
8. Re: Testing EJBCLIENT-34

jonatan.guillen Nov 5, 2012 6:18 AM (in response to jonatan.guillen)

Sometimes I get this log:

11:21:48,134 INFO [org.jboss.ejb.client.naming] (EJB default - 6) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@6876f6 since the current EJB client context selector can't handle scoped contexts
Actions
9. Re: Testing EJBCLIENT-34

jaikiran Nov 5, 2012 9:10 AM (in response to jonatan.guillen)

I expect this fix to be in the nightly build soon maybe this week or next.
Actions
10. Re: Testing EJBCLIENT-34

jaikiran Nov 5, 2012 9:11 AM (in response to jonatan.guillen)

Jonatan Guillen wrote:

Sometimes I get this log:

11:21:48,134 INFO [org.jboss.ejb.client.naming] (EJB default - 6) Cannot create a scoped EJB client context for JNDI naming context org.jboss.ejb.client.naming.ejb.EjbNamingContext@6876f6 since the current EJB client context selector can't handle scoped contexts
Sometimes? Can you add a bit more details about the client application - whether it's standalone and how it's using this feature?
Actions
11. Re: EJBCLIENT-34 fails for invocations on EJB 2.x views returned by home interface

jonatan.guillen Nov 6, 2012 6:10 AM (in response to jonatan.guillen)

It's use this feature to communications:
Jboss to Jboss
Tomcat to Jboss

Although this log appears, the answer is correct.
Actions
12. Re: EJBCLIENT-34 fails for invocations on EJB 2.x views returned by home interface

jaikiran Nov 6, 2012 6:42 AM (in response to jonatan.guillen)

Jonatan Guillen wrote:

It's use this feature to communications:
Jboss to Jboss
Tomcat to Jboss

Although this log appears, the answer is correct.
Are you sure, the Tomcat classpath has the latest EJB client jar which supports this feature? Also I'm not sure what you mean by the logs appears but the answer is correct.
Actions
13. Re: EJBCLIENT-34 fails for invocations on EJB 2.x views returned by home interface

jonatan.guillen Nov 6, 2012 7:05 AM (in response to jaikiran)

The communication between Tomcat and Jboss works good. The logs appear in the communication between Jboss.
With the last answer I meant that everything works fine. The only thing that worries me are these logs.
Actions
14. Re: EJBCLIENT-34 fails for invocations on EJB 2.x views returned by home interface

jaikiran Nov 6, 2012 7:31 AM (in response to jonatan.guillen)

Jonatan Guillen wrote:

The logs appear in the communication between Jboss.
With the last answer I meant that everything works fine. The only thing that worries me are these logs.
Are you sure both those JBoss AS versions are having the EJBCLIENT-34 feature implemented (i.e. using the correct nightly builds). If you are seeing those logs then there's some issue for sure. If you find it working even with those logs, it might be by chance. Can you add a bit more details including the exact code being used on the client (which itself is a AS7 instance)?
Actions

1 2 3 Previous Next

Go to original post