| Anonymous | Login | Signup for a new account | 12-17-2024 10:48 PST |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0002826 | [Resin] | minor | always | 08-07-08 09:42 | 09-11-09 18:10 | ||||
| Reporter | ferg | View Status | public | ||||||
| Assigned To | ferg | ||||||||
| Priority | normal | Resolution | fixed | Platform | |||||
| Status | closed | OS | |||||||
| Projection | none | OS Version | |||||||
| ETA | none | Fixed in Version | 4.0.2 | Product Version | 3.2.0 | ||||
| Product Build | |||||||||
| Summary | 0002826: BAM reliability and XA | ||||||||
| Description |
(rep by Chris Chen) How reliable is the BAM service? Does it provide a persistent subscription feature like JMS? In critical services where packets are sent and must be processed by a subscriber without losing that information, does BAM take care of this? Is there also a transaction feature to BAM where a message could either be put back into the queue to be retried if transaction fails and rolls back? |
||||||||
| Steps To Reproduce | |||||||||
| Additional Information | |||||||||
| Attached Files | |||||||||
|
|
|||||||||
 Relationships |
|
|
Notes |
|
|
(0004247) ferg 09-11-09 18:10 |
jms/2300 |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 08-07-08 09:42 | ferg | New Issue | |
| 09-11-09 18:10 | ferg | Note Added: 0004247 | |
| 09-11-09 18:10 | ferg | Assigned To | => ferg |
| 09-11-09 18:10 | ferg | Status | new => closed |
| 09-11-09 18:10 | ferg | Resolution | open => fixed |
| 09-11-09 18:10 | ferg | Fixed in Version | => 4.0.2 |
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed. 25 unique queries executed. |  |
