Joseph Caristi created AXIS2-5950:
-------------------------------------
Summary: JMSOutTransportInfo does no correctly identify
destinationType for WebLogic JMS client
Key: AXIS2-5950
URL: https://issues.apache.org/jira/browse/AXIS2-5950
Project: Axis2
Issue Type: Bug
Components: JMS transport
Affects Versions: 1.7.9
Reporter: Joseph Caristi
Fix For: 1.7.10
The constructor for JMSOutTransportInfo assumes that the passed in Destination
will be either an instance of a Topic or a Queue. In the case of WebLogic, the
Destination object implements both interfaces. So in the following code, both
conditions are true, and you always end up with
JMSConstants.DESTINATION_TYPE_TOPIC even when you have a queue :
{code:java}
destinationType = dest instanceof Topic ? JMSConstants.DESTINATION_TYPE_TOPIC
: JMSConstants.DESTINATION_TYPE_QUEUE;
{code}
When this occurs, an error is generated:
javax.jms.InvalidDestinationException: [JMSClientExceptions:055144]Destination
must be a topic, "queue-name"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
