| Anonymous | Login | Signup for a new account | 12-17-2024 10:44 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 | ||||
| 0001173 | [Resin] | minor | always | 06-05-06 14:11 | 06-27-06 14:25 | ||||
| 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 | 3.0.20 | Product Version | |||||
| Product Build | |||||||||
| Summary | 0001173: XA suspend issue | ||||||||
| Description |
(rep by Shane Cruz) We are trying to upgrade to ActiveMQ 4.0 and are having issues getting redeliveries to work when using Resin’s transaction manager. See: http://issues.apache.org/activemq/browse/AMQ-731 [^] According to the ActiveMQ developers (see issue above), the Resin transaction implementation is incorrect because “suspend is only supposed to remove the thread/tx association and not change what resources are enrolled in the transaction.” Do you agree with this statement? Most of the details are in the AMQ JIRA issue, so I have not duplicated them here. |
||||||||
| Steps To Reproduce | |||||||||
| Additional Information | |||||||||
| Attached Files | |||||||||
|
|
|||||||||
 Relationships |
|
|
Notes |
|
|
(0001323) ferg 06-27-06 14:24 edited on: 06-27-06 14:25 |
Checked with the JTA spec. It pretty clearly requires delisting on suspension, i.e. Resin's behavior looks correct: "3.2.3 Suspending and Resuming a Transaction The application server is responsible for ensuring that the resources in use by the application are properly delisted from the suspended transaction. A resource delist operation triggers the Transaction Manager to inform the resource manager to disassociate the transaction from the specified resource object (XAResource.end(TMSUSPEND)). When the application's transaction context is resumed, the application server ensured that the resource in use by the application is again enlisted with the transaction. Enlisting a resource as a result of resuming a transaction triggers the Transaction Manager to inform the resource manager to re-associate the resource object with the resumed transaction (XAResource.start(TMRESUME))." |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 06-05-06 14:11 | ferg | New Issue | |
| 06-27-06 14:24 | ferg | Note Added: 0001323 | |
| 06-27-06 14:25 | ferg | Assigned To | => ferg |
| 06-27-06 14:25 | ferg | Status | new => closed |
| 06-27-06 14:25 | ferg | Resolution | open => fixed |
| 06-27-06 14:25 | ferg | Fixed in Version | => 3.0.20 |
| 06-27-06 14:25 | ferg | Note Edited: 0001323 | |
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed. 25 unique queries executed. |  |
