Symptom
- Checking the server default trace files, you see an error similar to the below:
"Caused by: com.sap.glx.core.kernel.api.TransitionLockingException: Unable to certify lock GalaxyCowLock$LockImpl@5ec0d04a[state=0x1c/11100, owner=com.sap.glx.core.kernel.execution.TransitionManagerImpl$BoundPrimaryTransaction@6bec8330[startTime=14713469147, persistent=true, internal=false, interactive=true, commited=false, completed=false, closed=false, ended=false, endtime=0]] in ticket com.sap.glx.core.kernel.execution.TransitionManagerImpl$BoundPrimaryTransaction@6bec8330[startTime=1471334669147, persistent=true, internal=false, interactive=true, commited=false, completed=false, closed=false, ended=false, endtime=0] for image Image:Task_0_theTask_358def35b591174e504ba7f71187f{d4594d7c-62eb-11e6-bc44-000003c0ffa/d498508-62eb-11e6-bfdd-00000c0ffa}(Instance_0_theTask_358def35b59117e504ba74f71187f1{d459d7c-62eb-11e6-bc44-000003c0ffa/d4594d7c-62eb-11e6-bc44-000003c0ffa}(...),20,false,false,false,false).
at com.sap.glx.core.dock.storage.impl.StorageManagerImpl.prepare(StorageManagerImpl.java:387)" - You may be experiencing issues with your BPM system such as stuck processes, error messages etc.
Read more...
Environment
- SAP NetWeaver Application Server for Java 7.1 and higher releases
- SAP Business Process Management
Product
SAP NetWeaver 7.1 ; SAP NetWeaver 7.2 ; SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP enhancement package 1 for SAP NetWeaver 7.3
Keywords
bpem, cow, lock, hanging, hang, hung, error 500, exception, tuning, UI5, BPM, inbox , KBA , BC-BMT-BPM-DSK , Process Desk , BC-BMT-BPM-SRV , Process Server , BC-BMT-BPM-MON , Process Monitoring , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.