[
https://issues.jboss.org/browse/JBMESSAGING-1849?page=com.atlassian.jira....
]
Doug Grove updated JBMESSAGING-1849:
------------------------------------
Steps to Reproduce:
Place the test-queue-service.xml file into the deploy/messaging folder - this creates the
test queue
Place the byte-message-invalid-redelivery-1.0-SNAPSHOT.jar into the deploy folder - this
deploys the test ejb
Place the byte-message-invalid-redelivery-1.0-SNAPSHOT-CLIENT.jar into the client folder
From the client folder, run the client: java -jar
byte-message-invalid-redelivery-1.0-SNAPSHOT-CLIENT.jar
With DefaultRedeliveryDelay=0, errors will be seen on the console.
Byte messages redelivered incorrectly if DefaultRedeliveryDelay=0
used
----------------------------------------------------------------------
Key: JBMESSAGING-1849
URL:
https://issues.jboss.org/browse/JBMESSAGING-1849
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.7.GA
Reporter: Doug Grove
Priority: Minor
Attachments: byte-message-invalid-redelivery-1.0-SNAPSHOT-CLIENT.jar,
byte-message-invalid-redelivery-1.0-SNAPSHOT.jar, test-queue-service.xml
If DefaultRedeliveryDelay is set to 0 in messaging-service.xml (which is the default
value) and the first delivery attempt fails, then all subsequent redeliveries (up to
DefaultMaxDeliveryAttempts) are wrong. The result in redelivery is that the byte array
returned from BytesMessage.readBytes(byte[]) contains only zeros (the length of the array
is correct). Setting DefaultRedeliveryDelay to a value of 1 produces the expected
behavior.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira