|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 2939 | minor | always | 09-16-08 10:36 | 09-17-08 18:35 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | urgent | OS Version: | |||
| Status: | closed | Product Version: | 3.1.6 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.1.7 | ||
|
|
|||||
| 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: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||