[ 
https://issues.apache.org/jira/browse/AXIS2-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Veithen moved TRANSPORTS-25 to AXIS2-5546:
--------------------------------------------------

          Component/s:     (was: JMS)
                       JMS
    Affects Version/s:     (was: 1.0.0)
                       1.0.0
                  Key: AXIS2-5546  (was: TRANSPORTS-25)
              Project: Axis2  (was: Axis2 Transports)
    
> In-out operation is not working with IBM Websphere MQ
> -----------------------------------------------------
>
>                 Key: AXIS2-5546
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5546
>             Project: Axis2
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 1.0.0
>         Environment: Operating System - Windows XP Professional
> Tomcat v6.0.28
> IBM Websphere MQ v7.0.1.2
> Axis2 v1.5.1
> JMS Transport version 1.0.0 
>            Reporter: Rajeev Verma
>            Priority: Minor
>
> We are getting a ClassCastException (can not cast com.ibm.mq.jms.MQConnection 
> to javax.jms.QueueConnection) with JMS Transport for in-out operation when 
> message is sent to reply destination. Error occurs inside createJMSSender 
> method of JMSOutTransportInfo class when the connection object is type casted 
> in QueueConnection:
>        if (connection != null) {
>             if (destType == JMSConstants.QUEUE) {
>                 session = ((QueueConnection) connection).
>                         createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
>                 producer = ((QueueSession) session).createSender((Queue) 
> destination);
>             } else {
>                 session = ((TopicConnection) connection).
>                         createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
>                 producer = ((TopicSession) session).createPublisher((Topic) 
> destination);
>             }
>         }
> As a work around, I modified the configuration to use the domain specific 
> object com.ibm.mq.jms.MQQueueConnectionFactory instead of 
> com.ibm.mq.jms.MQConnectionFactory and it workd fine. 
> There is a need to change JMS transport to support JMS 1.1 specification in 
> receiver as well sender consistently.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to