[
https://jira.jboss.org/jira/browse/JBMESSAGING-1777?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1777:
-----------------------------------------
Hi,
From the trace I can see the bridge first clear all the properties
from the incoming message and then put them back in, when the exception occurred. That
means the 'JMSXDeliveryCount' was an existing property in the message from jboss
mq, but somehow after clearing, it cannot be set back into it.
can you also check
with JBoss MQ team why it is not allowed?
Howard
Error in addMessageIDInHeader while bridging from JBossMQ
---------------------------------------------------------
Key: JBMESSAGING-1777
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1777
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.3.GA
Environment: JBoss AS 5.1.0.GA
Reporter: Pedro Gontijo
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP10, 1.4.6.GA.SP1, 1.4.7.GA
When addMessageIDInHeader is set to true in a JBossMQ->JBM bridge scenerio the
following error occurs:
WARN [org.jboss.jms.server.bridge.Bridge] (Thread-27)
jboss.messaging:name=MyBridge,service=Bridge Failed to send + acknowledge batch, closing
JMS objects
javax.jms.JMSException: Illegal property name: JMSXDeliveryCount
at org.jboss.mq.SpyMessage.checkProperty(Unknown Source)
at org.jboss.mq.SpyMessage.setObjectProperty(Unknown Source)
at org.jboss.jms.server.bridge.Bridge.addMessageIDInHeader(Bridge.java:1481)
at org.jboss.jms.server.bridge.Bridge.sendMessages(Bridge.java:1391)
at org.jboss.jms.server.bridge.Bridge.sendBatchNonTransacted(Bridge.java:1261)
at org.jboss.jms.server.bridge.Bridge.sendBatch(Bridge.java:1375)
at org.jboss.jms.server.bridge.Bridge.access$1900(Bridge.java:68)
at org.jboss.jms.server.bridge.Bridge$BatchTimeChecker.run(Bridge.java:1638)
at java.lang.Thread.run(Thread.java:595)
As you can see the error is due JMSX properties, actually, because the
addMessageIDInHeader sets then in the MQ message (which is not allowed).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira