|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 5535 | minor | always | 09-27-13 10:17 | 10-03-13 14:03 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 4.0.37 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.38 | ||
|
|
|||||
| 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: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||