Bug 1121805 - Transaction timeouts with InventoryReportSerializer
Summary: Transaction timeouts with InventoryReportSerializer
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Core Server
Version: 4.12
Hardware: Unspecified
OS: Unspecified
unspecified vote
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
Depends On:
TreeView+ depends on / blocked
Reported: 2014-07-21 23:20 UTC by Elias Ross
Modified: 2014-07-21 23:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed:

Attachments (Terms of Use)

Description Elias Ross 2014-07-21 23:20:16 UTC
Description of problem:

As seen in my logs:

22:53:50,559 ERROR [org.rhq.enterprise.server.discovery.DiscoveryServerServiceImpl] (http-/ Fatal error occurred during merging of inventory report from agent [Agent[id=0,name=app011,address=null,port=0,remote-endpoint=null,last-availability-ping=null,last-availability-report=null]].: javax.ejb.EJBTransactionRolledbackException: Transaction rolled back
Caused by: javax.transaction.RollbackException: JBAS014585: Transaction 'TransactionImple < ac, BasicAction: 0:ffff11b0d076:-740e8efb:53cd577c:cf7790 status: ActionStatus.ABORTED >' was already rolled back
	at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:99) [jboss-as-ejb3-7.4.0.Final-redhat-4.jar:7.4.0.Final-redhat-4]
	... 159 more
22:53:50,573 INFO  [org.rhq.enterprise.server.util.concurrent.InventoryReportSerializer] (http-/ tid=829; agent=app011: releasing write lock after being locked for millis=620820
22:53:50,573 INFO  [org.rhq.enterprise.server.util.concurrent.InventoryReportSerializer] (http-/ tid=990; agent=app011: acquired write lock in millis=80836

What seems to happen is there is a database transaction for 'app011' that hangs, eventually aborts (after 10 minutes), and a secondary transaction that overlaps.

I'll update if I have more information.

Version-Release number of selected component (if applicable): 4.12

How reproducible: Unclear

Note You need to log in before you can comment on or make changes to this bug.