Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1079366

Summary: Camel JMS binding and global transaction rollback logs 'Could not commit transaction' warning
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Václav Chalupa <vchalupa>
Component: SwitchYardAssignee: Rob Cernich <rcernich>
Status: CLOSED UPSTREAM QA Contact: Matej Melko <mmelko>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0.0 GACC: mvecera, oskutka, soa-p-jira
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:35:25 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:
Description Flags
reproducer none

Description Václav Chalupa 2014-03-21 13:34:58 UTC
Created attachment 877272 [details]
reproducer

Camel JMS inbound binding logs warning for every global transaction rollback:

WARN  [org.apache.camel.component.jms.DefaultJmsMessageListenerContainer] (Camel (camel-23) thread #56 - JmsConsumer[JmsBindingIssueInQ]) Setup of JMS message listener invoker failed for destination 'JmsBindingIssueInQ' - trying to recover. Cause: JTA transaction unexpectedly rolled back (maybe due to a timeout); nested exception is javax.transaction.RollbackException: ARJUNA016053: Could not commit transaction.



Final transaction processing is correct.

Simple reproducer attached.

Comment 8 Red Hat Bugzilla 2025-02-10 03:35:25 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.