0005535: JMS double message on restart

Viewing Issue Advanced Details [ Jump to Notes ]

[ View Simple ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0005535

[Resin]

minor

always

09-27-13 10:17

10-03-13 14:03

Reporter

ferg

View Status

public

Assigned To

ferg

Priority

normal

Resolution

fixed

Platform

Status

closed

Projection

none

OS Version

ETA

none

Fixed in Version

4.0.38

Product Version

4.0.37

Product Build

Summary

0005535: JMS double message on restart

Description

(rep by Scott Weatbrook)
I believe I found a bug in Resin 4.0.37 but you'll have to determine this.

We are using JMS as such:

<jms-queue name="eventNotificationQueue" jndi-name="eventNotificationQueue" uri="file:path=WEB-INF/messaging"/>
<jms-connection-factory uri="resin:"/>
<ejb-message-bean class="inpowered.common.notification.EventConsumer">
<destination>#{eventNotificationQueue}</destination>
</ejb-message-bean>

and whenever we restart the server it will re-process the latest message in the queue.

The message bean is setup to email our clients and they keep getting duplicate emails of events that have happened in the system because of this.

1. Is there something I'm doing wrong in the setup?
2. Is this a Resin bug?
3. Is the code supposed to do anything to flag the message as having already been sent? If so, how?
3. We have a workaround by using the in-memory queue but we would like to still use the file queue as the documentation suggests.

Steps To Reproduce

Additional Information

Attached Files

Relationships

Notes
(0006330) ferg 10-03-13 14:03	ejb/703e

Issue History
Date Modified	Username	Field	Change
09-27-13 10:17	ferg	New Issue
10-03-13 14:03	ferg	Note Added: 0006330
10-03-13 14:03	ferg	Assigned To	=> ferg
10-03-13 14:03	ferg	Status	new => closed
10-03-13 14:03	ferg	Resolution	open => fixed
10-03-13 14:03	ferg	Fixed in Version	=> 4.0.38

Mantis 1.0.0rc3[^]

28 total queries executed.
25 unique queries executed.