[
https://wso2.org/jira/browse/ESBJAVA-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dwyer updated ESBJAVA-542:
--------------------------------
Attachment: synapse-1.2-jasond.patch
rolls up previous patch plus a new bit in JMSSender.
this patch now gets the reply to destination from jndi, and sets the replyTo
property on the message.
this is only tested in a specific use case against MQSeries JMS using jndi
lookups.
it may well provide some impetus to refactor the underlying jms code to
determine absolute property declarations ( like with ActiveMQ) vs true jndi
lookups. ( JMSSender.sendMessage() is 200 lines long....)
the following sequence in synapse.xml _appears_ to be working when looking up
the underlying queues through jndi:
<sequence name="jms_sequence">
<property name="transport.jms.ReplyDestinationType" value="queue"/>
<send>
<endpoint>
<address
uri="jms:/getCustomerNameRequestQueue?transport.jms.ConnectionFactory=defaultJmsSender&transport.jms.ReplyDestination=getCustomerNameResponseQueue&transport.jms.ReplyDestinationType=queue"
format="pox"/>
</endpoint>
</send>
<out>
<send/>
</out>
</sequence>
> JMSSender for ibm Websphere MQ fails when setting 'Content-Type' header in
> http proxy for jms transport switch
> --------------------------------------------------------------------------------------------------------------
>
> Key: ESBJAVA-542
> URL: https://wso2.org/jira/browse/ESBJAVA-542
> Project: WSO2 ESB
> Issue Type: Bug
> Components: Endpoints Management
> Environment: java 6, lunux, ibm MQ series (websphere MQ) v 6.0.3
> Reporter: Jason Dwyer
> Assignee: Asankha Perera
> Attachments: synapse-1.2-jasond.patch, synapse_and_mq.txt
>
>
> when setting up a http proxy to do transport switch to jms using ibm
> websphere MQ, an exception is thrown because the ibm jms classes wont accept
> setting the property for 'Content-Type':
> {code}
> 2008-07-10 15:59:36,245 [127.0.0.1-granite] [HttpServerWorker-1] ERROR
> JMSSender Error creating a JMS message from the axis message context
> javax.jms.MessageFormatException: MQJMS1058: Invalid message property name:
> Content-Type
> at
> com.ibm.jms.JMSMessage.newMessageFormatException(JMSMessage.java:4772)
> at com.ibm.jms.JMSMessage.setStringProperty(JMSMessage.java:5771)
> at
> org.apache.synapse.transport.jms.JMSSender.createJMSMessage(JMSSender.java:424)
> at
> org.apache.synapse.transport.jms.JMSSender.sendMessage(JMSSender.java:207)
> at
> org.apache.synapse.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:120)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448)
> at
> org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.send(DynamicAxisOperation.java:190)
> at
> org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.executeImpl(DynamicAxisOperation.java:174)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
> at
> org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:288)
> at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:57)
> at
> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:222)
> at
> org.apache.synapse.endpoints.AddressEndpoint.send(AddressEndpoint.java:195)
> at
> org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:179)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
> at
> org.apache.synapse.transport.nhttp.ServerWorker.processPost(ServerWorker.java:253)
> at
> org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:194)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> at java.lang.Thread.run(Thread.java:619)
> {code}
> i've put some further detail in the forum: http://wso2.org/forum/thread/3805
> where asankha has been helpful, and suggested logging this here.
> i'll attach some setup details to help re-produce the issue as well ( the
> attachment is part of my own setup notes, hope it makes sense..)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
