[
https://wso2.org/jira/browse/ESBJAVA-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18078#action_18078
]
Jason Dwyer commented on ESBJAVA-542:
-------------------------------------
just tried a hacky patch on the JMSSender to check for the 'Content-Type'
header before setting the property, then ran through it only to find the next
header is 'Transfer-Encoding', which the ibm jms classes also dont like.
it appears the use of the '-' character is the problem here, and so any header
coming in that is attempted to be set as a property that contains this
character is going to be a problem.
i dont know if the ibm classes are strictly adhering to the jms spec, or if the
ibm way of doing it is different from everyone else, or if the spec forbids
the '-' character, but running the initial configuration against synapse 1.2
using the apache mq jms system works without a problem
> 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_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
