You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "James Strachan (JIRA)" <ji...@apache.org> on 2007/11/13 12:40:22 UTC
[jira] Created: (CAMEL-213) MQSeries doesn't seem to like the
JMSXAppID header being set on a JMS message - so we should exclude it
MQSeries doesn't seem to like the JMSXAppID header being set on a JMS message - so we should exclude it
-------------------------------------------------------------------------------------------------------
Key: CAMEL-213
URL: https://issues.apache.org/activemq/browse/CAMEL-213
Project: Apache Camel
Issue Type: Bug
Components: camel-jms
Reporter: James Strachan
Fix For: 1.3.0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-213) MQSeries doesn't seem to like the
JMSXAppID header being set on a JMS message - so we should exclude it
Posted by "James Strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40605 ]
James Strachan commented on CAMEL-213:
--------------------------------------
I just made another patch so that only valid Java identifier headers are output to the JMS message - to avoid further exceptions with MQSeries - see http://www.nabble.com/Camel-1.2-Websphere-MQ-6-issue-tf4793824s22882.html
> MQSeries doesn't seem to like the JMSXAppID header being set on a JMS message - so we should exclude it
> -------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-213
> URL: https://issues.apache.org/activemq/browse/CAMEL-213
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-jms
> Reporter: James Strachan
> Fix For: 1.3.0
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-213) MQSeries doesn't seem to like the
JMSXAppID header being set on a JMS message - so we should exclude it
Posted by "James Strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Strachan resolved CAMEL-213.
----------------------------------
Resolution: Fixed
I've fixed the code for the JMSXAppID header - see test case MQSeriesHeaderTest.
If there are any other MQ headers it doesn't like clients setting we can reopen this issue and fix them...
> MQSeries doesn't seem to like the JMSXAppID header being set on a JMS message - so we should exclude it
> -------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-213
> URL: https://issues.apache.org/activemq/browse/CAMEL-213
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-jms
> Reporter: James Strachan
> Fix For: 1.3.0
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-213) MQSeries doesn't seem to like the
JMSXAppID header being set on a JMS message - so we should exclude it
Posted by "James Strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40614 ]
James Strachan commented on CAMEL-213:
--------------------------------------
Just added another patch to conform to page 39 of the JMS 1.1 spec ignoring a bunch of other headers...
{code}
"JMSXUserID", "JMSXAppID",
"JMSXDeliveryCount", "JMSXProducerTXID", "JMSXConsumerTXID",
"JMSXRcvTimestamp", "JMSXState"
{code}
> MQSeries doesn't seem to like the JMSXAppID header being set on a JMS message - so we should exclude it
> -------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-213
> URL: https://issues.apache.org/activemq/browse/CAMEL-213
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-jms
> Reporter: James Strachan
> Fix For: 1.3.0
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.