Mantis Bugtracker

Viewing Issue Advanced Details Jump to Notes ] View Simple ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0002939 [Resin] minor always 09-16-08 10:36 09-17-08 18:35
Reporter ferg View Status public  
Assigned To ferg
Priority urgent Resolution fixed Platform
Status closed   OS
Projection none   OS Version
ETA none Fixed in Version 3.1.7 Product Version 3.1.6
  Product Build
Summary 0002939: database-based JMS in clustered environment
Description (rep by Vinay Reddy)

We have an issue with JMS.
We are using database managed JMS queues. We are able to put the message successfully into the JMS queue and able see the message(RESI_JMS_MESSAGE table) in the database.
We have another application(Resin instance) running on different JVM and its JMS is pointing to the same database as the first one. This application is not able to pick the messages put by the first application.
I am attaching the resin-web.xml for your reference.
This is very critical issue for us to move forward with our resin migration.
Steps To Reproduce
Additional Information
Attached Files

- Relationships

- Notes
09-17-08 18:35


- Issue History
Date Modified Username Field Change
09-16-08 10:36 ferg New Issue
09-17-08 18:35 ferg Note Added: 0003455
09-17-08 18:35 ferg Assigned To  => ferg
09-17-08 18:35 ferg Status new => closed
09-17-08 18:35 ferg Resolution open => fixed
09-17-08 18:35 ferg Fixed in Version  => 3.1.7

Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed.
25 unique queries executed.
Powered by Mantis Bugtracker