After upgrade to 10.5.x both MOM & Collector logs contain "SEVERE: Could not synchronize database state with session org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect)"

Document ID : KB000006220
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

After upgrade to 10.5.x both MOM & Collector logs contain repeated messages:

org.hibernate.event.def.AbstractFlushingEventListener performExecutions 

SEVERE: Could not synchronize database state with session 

org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [com.timestock.tess.data.objects.Monitor#700000000000002563] 

 

If enable DEBUG this line is also visible before the SEVERE message:

[DEBUG] [pool-19-thread-1] [Manager.com.wily.apm.tess.isengard.EMBizRecordingServiceBean] disabling agent monitor in db...

Environment:
APM 10.5.x
Cause:

The messages are due to MOM & Collector threads both trying to update the APM database when an agent disconnects. One operation fails with StaleObjectStateException because the other thread has already succeeded. There is no loss of functionality.

The symptoms only occur when the CEM Business Transaction agent recording feature is enabled on the agent via the bizrecording.pbd file.

Resolution:

There are 2 options:

1. Ignore the messages (there is no loss in functionality)

2. Disable the agent recording feature in the agent profile by setting this property to false (the default is true)

introscope.agent.bizRecording.enabled=false

Additional Information:

Implementing Agents > Java Agent > Java Agent Properties> Agent Recording (Business Recording) Property

Extending > Transaction Definition > Introscope Agent Recording > Enable agent recording > Enabling agent recording in the agent profile