[
https://issues.apache.org/jira/browse/SYNAPSE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646127#action_12646127
]
Andreas Veithen commented on SYNAPSE-478:
-----------------------------------------
I had a closer look at the JMS specs and it appears that whether a message
property starting with JMSX or JMS_ is settable or not depends on the JMS
provider. I think that in the case where such a transport header is set
explicitly set (in client code or in a Synapse mediation), the user would
expect that the transport raises an error if the property is not settable.
Therefore I believe that simply ignoring exceptions thrown by
Message#setXxxProperty is not a valid approach.
Actually, I believe that the real problem here is that in a proxy service,
Synapse by default copies the transport headers from the incoming to the
outgoing message (even if different transports are used!). I remember that
recently other users reported problems that were related to this. In general
the default behavior easily leads to unexpected results and is highly confusing
for users not familiar with the internals of Synapse and the transports.
Note: Since there is a valid workaround for this issue (which is to explicitly
remove the transport headers causing the problem), I will lower its priority.
> Synapse exceptions with JBossMQ
> -------------------------------
>
> Key: SYNAPSE-478
> URL: https://issues.apache.org/jira/browse/SYNAPSE-478
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: 1.2
> Environment: JBoss 4.2.3GA
> Reporter: irantha suwandarathna
> Assignee: Andreas Veithen
> Attachments: commons_jms.patch, commons_jms.patch
>
>
> JBossMQ SpyMessage (javax.jms.Message instance) throw exceptions for (
> JMSXDeliveryCount, JMS_DESTINATION, JMS_JBOSS_REDELIVERY_COUNT,
> JMS_REDELIVERED ) properties set inside JMSUtils.setTransportHeaders method.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
