Bug 1090037
| Summary: | JMS binding with HornetQ cannot enlist to global transaction propagated over SCA binding, XTS enabled | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Fuse Service Works 6 | Reporter: | Václav Chalupa <vchalupa> | ||||||
| Component: | SwitchYard | Assignee: | Tomohisa Igarashi <toigaras> | ||||||
| Status: | CLOSED UPSTREAM | QA Contact: | Matej Melko <mmelko> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.0.0 GA | CC: | mvecera, oskutka, rcernich | ||||||
| Target Milestone: | --- | Keywords: | Documentation | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Known Issue | |||||||
| Doc Text: |
Cause:
Use jca and camel-jms binding mixed for same HornetQ instance in one application
Consequence:
cannot enlist in transaction if the application is invoked through SCA binding with transaction propagation enabled
Fix:
Use same binding for same resource manager
Result:
The transaction is sucessfully processed
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2025-02-10 03:35:40 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Basically using different binding for same RM is not a good idea. It may cause performance degradation by the unneccesary two-phase commit even if it works functionally. So workaround is to use same binding for the same RM. Once HORNETQ-1426 is fixed, those will be recognized as same RM even if you use JCA and Camel JMS mixed, which solves this issue and omits unneccesary two-phase commit. Andy Taylor <ataylor> updated the status of jira HORNETQ-1426 to Resolved Hey Tomo, are we going to resolve this by documenting the workaround? Sounds like that's where we're at. Let me know. Thanks in advance. Rob, yes I believe so. This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |
Created attachment 915889 [details] Comment (This comment was longer than 65,535 characters and has been moved to an attachment by Red Hat Bugzilla).