]
Richard Achmatowicz commented on WFLY-5640:
-------------------------------------------
These load balancing tests work like this:
- start a cluster of two servers with a SLSB deployment on each server
- create an EJB client using a properties file which points to the first server
- fire invocations at the cluster and check that invocations are balanced between both
nodes
- create a new EJBClient using a properties file which points to the second server
- fire invocations at the cluster and check that invocations are balanced between both
nodes
The problem is that the test case is trying to use localhost:4547 to contact the second
server. This is the way a client would connect to a server in pre Wildfly 8 versions
before Undertow HTTP Upgrade was introduced. The client cannot connect to the second
server in this way and so no EJBReceivers which point to the server are found.
The fix is to change the port from 4547 to 8080.
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
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}