Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WFLY-3193] Upgrade generic JMS RA 1.0.4.Final #6105

Conversation

jmesnil
Copy link
Member

@jmesnil jmesnil commented Mar 31, 2014

revert the use of the TransactionSynchronizationRegistryLookup as the
generic JMS RA will always delegate the transacted behaviour of the JMS
session to the Java EE container

JIRA: https://issues.jboss.org/browse/WFLY-3193

revert the use of the TransactionSynchronizationRegistryLookup as the
generic JMS RA will always delegate the transacted behaviour of the JMS
session to the Java EE container

JIRA: https://issues.jboss.org/browse/WFLY-3193
@wildfly-ci
Copy link

Build 3111 is now running using a merge of 764afbf

@wildfly-ci
Copy link

Build 3111 outcome was FAILURE using a merge of 764afbf
Summary: Tests failed: 1 (1 new), passed: 5643, ignored: 78 Build time: 1:40:56

Build problems:

Failed tests detected

java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:registry, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@15753fb
java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:registry, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@15753fb
    at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:749)
    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.sendRequestWithPossibleRetries(EJBInvocationHandler.java:253)
    at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:198)
    at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:181)
    at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144)
    at com.sun.proxy.$Proxy29.getNodes(Unknown Source)
    at org.jboss.as.test.clustering.cluster.registry.RegistryTestCase.test(RegistryTestCase.java:60)

Failed tests

org.jboss.as.test.clustering.cluster.registry.RegistryTestCase(SYNC-tcp).test: java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:registry, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@15753fb
    at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:749)
    at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116)

@ctomc
Copy link
Contributor

ctomc commented Mar 31, 2014

retest this please

@wildfly-ci
Copy link

Build 3119 is now running using a merge of 764afbf

@wildfly-ci
Copy link

Build 3119 outcome was SUCCESS using a merge of 764afbf
Summary: Tests passed: 5644, ignored: 78 Build time: 1:52:01

@bstansberry
Copy link
Contributor

Merged.

@bstansberry bstansberry closed this Apr 3, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants