Re: Error with Webspher MQ and jms-bc

[Gert Vanthienen]

Esteban,

It looks like WebSphere V5R3 doesn't like the value we are setting in 
the correlation ID.  If you use the newer <jms:provider/> endpoint 
instead of this one, it should handle this correctly.  It will also 
allow you to plug in your own JmsProviderMarshaler implementation to 
fine-tune the message that is going to/from your JMS queue.

Regards,

Gert

Esteban Forzani wrote:
Hi,

I have the following configuration to the jms-bc:

<beans xmlns:jms="http://servicemix.apache.org/jms/1.0";
      xmlns:b="http://test.com/testing3";>

                <jms:endpoint service="b:jms-provider"
                        endpoint="endpoint"
                        role="provider"
                        destinationStyle="queue"
                        jmsProviderDestinationName="Q_REQUEST"
                        jmsProviderReplyToName="Q_RESPONSE"
                        processorName="standard"
                        defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
                        connectionFactory="#mqConnectionFactory"/>

       <bean id="mqConnectionFactory"
class="com.ibm.mq.jms.MQQueueConnectionFactory">
           <property name="transportType" value="1"/>
           <property name="queueManager" value="QMNGR"/>
           <property name="hostName" value="10.100.0.125"/>
           <property name="channel" value="SDAS"/>
           <property name="port" value="1414"/>
       </bean>

</beans>

The Webphere MQ is version 5.3 throws this error:

javax.jms.JMSException: MQJMS1044: String is not a valid hexadecimal number
10.100.146.202-11aefb3096b-4:38

If I comment the line 126 in StandardProviderProcessor.java, it works!!
The line is: msg.setJMSCorrelationID(exchange.getExchangeId());

Are there any configuration to solve this problem?

Thanks

Regards

Esteban