[
https://issues.apache.org/jira/browse/AXIS2-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiranya Jayathilaka updated AXIS2-5536:
---------------------------------------
Attachment: AXIS2-5536.patch
Implementing a fix so that when Session object doesn't implement QueueSession
or TopicSession, we look at the replyDestinationType parameter. Defaults to
temp queue when all else fails.
> JMS Transport Uses Temporary Topics for replyDestinationType, irrespective of
> transport.jms.ReplyDestinationType Value
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-5536
> URL: https://issues.apache.org/jira/browse/AXIS2-5536
> Project: Axis2
> Issue Type: Bug
> Components: JMS transport
> Affects Versions: Transports 1.0.0
> Environment: - Axis2 1.5
> - axis2-transport-jms-1.0-SNAPSHOT.jar
> - axis2-transport-base-1.0-SNAPSHOT.jar
> Reporter: Curtis Ling
> Attachments: AXIS2-5536.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
