Bug 861237 - ResourceManager.getLiveResourceAvailability fails due to PersistentObjectException: detached entity passed to persist: org.rhq.core.domain.configuration.definition.ConfigurationDefinition
ResourceManager.getLiveResourceAvailability fails due to PersistentObjectExce...
Product: JBoss Operations Network
Classification: JBoss
Component: CLI (Show other bugs)
JON 3.1.0
All All
high Severity high
: ---
: JON 3.1.2
Assigned To: Heiko W. Rupp
Mike Foley
Depends On: 861239
  Show dependency treegraph
Reported: 2012-09-27 17:45 EDT by Larry O'Leary
Modified: 2013-09-11 07:01 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 861239 (view as bug list)
Last Closed: 2013-09-11 07:01:18 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Proposed patch (5.80 KB, patch)
2012-11-14 10:46 EST, Heiko W. Rupp
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 224463 None None None 2012-09-27 17:55:51 EDT

  None (edit)
Description Larry O'Leary 2012-09-27 17:45:42 EDT
Description of problem:
Can not execute ResourceManager.getLiveResourceAvailability from CLI or Remote API due to:

Caused by: org.hibernate.PersistentObjectException: detached entity passed to persist: org.rhq.core.domain.configuration.definition.ConfigurationDefinition
	at org.hibernate.event.def.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:79)
	at org.hibernate.impl.SessionImpl.firePersistOnFlush(SessionImpl.java:644)
	at org.hibernate.impl.SessionImpl.persistOnFlush(SessionImpl.java:636)
	at org.hibernate.engine.CascadingAction$9.cascade(CascadingAction.java:323)
	at org.hibernate.engine.Cascade.cascadeToOne(Cascade.java:268)
	at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java:216)
	at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java:169)
	at org.hibernate.engine.Cascade.cascade(Cascade.java:130)
	at org.hibernate.event.def.AbstractFlushingEventListener.cascadeOnFlush(AbstractFlushingEventListener.java:131)
	at org.hibernate.event.def.AbstractFlushingEventListener.prepareEntityFlushes(AbstractFlushingEventListener.java:122)
	at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:65)
	at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26)
	at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000)
	at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338)
	at org.hibernate.ejb.AbstractEntityManagerImpl$1.beforeCompletion(AbstractEntityManagerImpl.java:515)
	... 101 more

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

How reproducible:

Steps to Reproduce:
1. Install JON system and add one or more resources to inventory
2. Locate a valid resource ID for a resource in inventory - probably 10001
3. Execute the following from the JON CLI:


Actual results:
        Wrapped java.lang.RuntimeException: [Warning] javax.transaction.RollbackException: [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Can't commit because the transaction is in aborted state (<Unknown source>#1)

Expected results:
The live availability for the resource with ID 10001 (in my case Platform).
Comment 1 Heiko W. Rupp 2012-11-14 10:46:06 EST
Created attachment 644969 [details]
Proposed patch

An additional entityManager.flush() makes the issue go away for me.
Comment 2 Heiko W. Rupp 2012-11-19 06:02:50 EST
Proposed patch is now in master as 23be83c54ea7c
Comment 3 Heiko W. Rupp 2012-11-19 09:02:04 EST
Pushed to the release branch as 94abac1c47b4c9f
Comment 4 Simeon Pinder 2012-11-21 16:56:15 EST
Moving to ON_QA as available for test with build : https://brewweb.devel.redhat.com//buildinfo?buildID=244662.
Comment 5 Filip Brychta 2012-11-26 07:51:15 EST
Verified on 3.1.2.ER2

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