[jboss-jira] [JBoss JIRA] (WFLY-5640) No EJB receiver available for handling
[
https://issues.jboss.org/browse/WFLY-5640?page=com.atlassian.jira.plugin....
]
Ivan Straka edited comment on WFLY-5640 at 1/29/16 5:14 AM:
------------------------------------------------------------
Still failing.
I did some investigation yesterday and I figured out what the problem is.
https://github.com/wildfly/wildfly/tree/master/testsuite/integration/clus...
This should be set to 8180. Node1 is listening on this port. If you look into the
configuration, you will find out that node0 is listening on 8080. Thats why you
weren't able to reproduce it locally (neither were I). Due to the same ip addresses of
node0 and node1 8080 was valid (node 0 is listening on 8080), on the other hand, if ip
addresses are not same, noone is listening on node1_ip : 8080
I am just about to do a PR to WF.
was (Author: istraka):
Still failing.
I did some investigation yesterday and I figured out what the problem is.
https://github.com/jbossas/jboss-eap7/blob/7.x/testsuite/integration/clus...
This should be set to 8180. Node1 is listening on this port. If you look into the
configuration, you will find out that node0 is listening on 8080. Thats why you
weren't able to reproduce it locally (neither were I). Due to the same ip addresses of
node0 and node1 8080 was valid (node 0 is listening on 8080), on the other hand, if ip
addresses are not same, noone is listening on node1_ip : 8080
I am just about to do a PR to EAP.
No EJB receiver available for handling
--------------------------------------
Key: WFLY-5640
URL: https://issues.jboss.org/browse/WFLY-5640
Project: WildFly
Issue Type: Bug
Components: Clustering, EJB, Test Suite
Affects Versions: 10.0.0.CR4
Environment: hp-ux 11v3 - hpjdk1.8
solaris 10,11 - x86 and x86_64, rhel 6 - x86 and x86_64, rhel 7 x86_64 - openjdk1.8,
ibmjdk1.8, oraclejdk1.8
Reporter: Ivan Straka
Assignee: Richard Achmatowicz
Fix For: 10.0.0.CR5
Attachments: logs
There are two tests failing in exteded tests in clusteringejb2 package in AS TS.
org.jboss.as.test.clustering.extended.ejb2.stateless.RemoteStatelessFailoverTestCase(SYNC-tcp-extended)#testLoadbalanceSpecifiedByDescriptor
org.jboss.as.test.clustering.extended.ejb2.stateless.RemoteStatelessFailoverTestCase(SYNC-tcp-extended)#testLoadbalanceAnnotatedBean
both with exception
{code}
Error Message
EJBCLIENT000025: No EJB receiver available for handling [appName:,
moduleName:stateless-ejb2-failover-test, distinctName:] combination for invocation context
org.jboss.ejb.client.EJBClientInvocationContext@54acff7d
Stacktrace
java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling
[appName:, moduleName:stateless-ejb2-failover-test, distinctName:] combination for
invocation context org.jboss.ejb.client.EJBClientInvocationContext@54acff7d
at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:798)
at
org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:112)
at
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
at
org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
at com.sun.proxy.$Proxy28.create(Unknown Source)
at
org.jboss.as.test.clustering.extended.ejb2.stateless.RemoteStatelessFailoverTestCase.loadbalance(RemoteStatelessFailoverTestCase.java:262)
at
org.jboss.as.test.clustering.extended.ejb2.stateless.RemoteStatelessFailoverTestCase.testLoadbalanceAnnotatedBean(RemoteStatelessFailoverTestCase.java:224)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)