[
https://issues.jboss.org/browse/WFLY-11142?page=com.atlassian.jira.plugin...
]
Jan Blizňák commented on WFLY-11142:
------------------------------------
[~kabirkhan] Only one direction si fixed with artemis upgrade:
WF13.0.0.Final client(artemis 1.5.5.jbossorg-012) against WF14.0.1.Final server (artemis
2.6.3.jbossorg-001) is broken, as reported in this jira
WF13.0.0.Final client(artemis 1.5.5.jbossorg-012) against WF15.0.0.CR1-SNAPSHOT server
(artemis 2.6.3.jbossorg-013) is working now, fixed by WFLY-11143
WF14.0.1.Final client(artemis 2.6.3.jbossorg-001) against WF13.0.0.Final server(artemis
1.5.5.jbossorg-012) is broken, as reported in this jira
WF15.0.0.CR1-SNAPSHOT client (artemis 2.6.3.jbossorg-013) against WF13.0.0.Final
server(artemis 1.5.5.jbossorg-012) *is still broken*
Regression in SOAP over JMS when WF13 and WF14 are communicating
----------------------------------------------------------------
Key: WFLY-11142
URL:
https://issues.jboss.org/browse/WFLY-11142
Project: WildFly
Issue Type: Bug
Components: JMS, Web Services
Affects Versions: 14.0.0.Final
Reporter: Jan Blizňák
Assignee: Jeff Mesnil
Priority: Major
There is a regression visible in JBossWS testsuite in SOAP over JMS test when client side
and server side are WF13 and WF14 or vice-versa, in other words it is affecting backward
and forward compatibility.
The cause was identified as Artemis upgrade from 1.5.5 to 2.6.3, there is ongoing
investigation for gathering more details.
Exception in case of new client and old server:
{code:java}
Exception while processing jms message in cxf. Rolling back:
javax.jms.JMSRuntimeException: Invalid address queue://jms.queue.testQueue
at
org.apache.activemq.artemis.jms.client.ActiveMQDestination.fromAddress(ActiveMQDestination.java:119)
[artemis-jms-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
at
org.apache.activemq.artemis.jms.client.ActiveMQMessage.getJMSReplyTo(ActiveMQMessage.java:356)
[artemis-jms-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
at
org.apache.cxf.transport.jms.JMSMessageHeadersType.getDestName(JMSMessageHeadersType.java:363)
[cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
at
org.apache.cxf.transport.jms.JMSMessageHeadersType.read(JMSMessageHeadersType.java:358)
[cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
at
org.apache.cxf.transport.jms.JMSMessageHeadersType.from(JMSMessageHeadersType.java:335)
[cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
at org.apache.cxf.transport.jms.JMSMessageUtils.asCXFMessage(JMSMessageUtils.java:64)
[cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
at org.apache.cxf.transport.jms.JMSDestination.onMessage(JMSDestination.java:237)
[cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
at
org.apache.cxf.transport.jms.util.PollingMessageListenerContainer$Poller.run(PollingMessageListenerContainer.java:84)
[cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[rt.jar:1.8.0_181]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[rt.jar:1.8.0_181]
at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_181]
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)