JMS Transport Uses Temporary Topics for replyDestinationType, irrespective of
transport.jms.ReplyDestinationType Value
----------------------------------------------------------------------------------------------------------------------
Key: AXIS2-4499
URL: https://issues.apache.org/jira/browse/AXIS2-4499
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: transports
Affects Versions: 1.5
Environment: - Axis2 1.5
- axis2-transport-jms-1.0-SNAPSHOT.jar
- axis2-transport-base-1.0-SNAPSHOT.jar
Reporter: Curtis Ling
Using the 1.0-SNAPSHOT jars from
https://repository.apache.org/index.html#view-repositories;snapshots-group
Using TIBCO BusinessWorks as a soap server, and a pojo java client. TIBCO
BusinessWorks is not able to return a reply to a temporary topic, and so
expects the replyTo destination to be a temporary queue.
When we set the replyDestinationType to "queue" (both in the endpoint URL and
the axis2.xml file), the jms transport ignores it and uses a temporary topic.
We've added some debug statements to the source code to ensure the issue wasn't
configuration related. We can see that the replyDestinationType is "queue",
but createTemporaryDestination() in JMSUtils.java doesn't respect the property.
As a suggestion, it might make sense for that method to examine the property,
and instantiate a new session (a QueueSession, in this case) if one is required.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
