Skip to Content
0

Error in SAP BPM process - Failed to reenter storage group

Feb 24 at 09:07 PM

164

avatar image

I have a bpmn process error.

Several processes I have the error as below.

What can I do?

Below, complete error trace:

com.sap.glx.core.dock.api.StorageException: Failed to reenter storage group a828ef4c-1302-11e8-c210-0000001f7aca
	at com.sap.glx.core.dock.storage.impl.StorageManagerImpl.reenter(StorageManagerImpl.java:1620)
	at com.sap.glx.core.dock.storage.impl.StorageManagerImpl.reenter(StorageManagerImpl.java:1347)
	at com.sap.glx.core.dock.storage.impl.StorageManagerImpl.locate(StorageManagerImpl.java:807)
	at com.sap.glx.core.dock.storage.impl.StorageManagerImpl.locate(StorageManagerImpl.java:700)
	at com.sap.glx.core.dock.storage.impl.StorageManagerImpl.locate(StorageManagerImpl.java:689)
	at com.sap.glx.core.internaladapter.async.AsyncQueueHandler.executeAction(AsyncQueueHandler.java:482)
	at com.sap.glx.core.internaladapter.async.AsyncQueueHandler.processSingleQueueEntry(AsyncQueueHandler.java:431)
	at com.sap.glx.core.internaladapter.async.AsyncQueueHandler.processQueueEntries(AsyncQueueHandler.java:381)
	at com.sap.glx.core.internaladapter.async.AsyncQueuePoller.poll(AsyncQueuePoller.java:206)
	at com.sap.glx.core.internaladapter.async.AsyncQueuePoller.run(AsyncQueuePoller.java:130)
	at com.sap.glx.core.resource.impl.common.WorkWrapper.run(WorkWrapper.java:58)
	at com.sap.glx.core.resource.impl.j2ee.J2EEResourceImpl$Sessionizer.run(J2EEResourceImpl.java:296)
	at com.sap.glx.core.resource.impl.j2ee.ServiceUserManager$ServiceUserImpersonator$1.run(ServiceUserManager.java:171)
	at java.security.AccessController.doPrivileged(Native Method)
	at javax.security.auth.Subject.doAs(Subject.java:335)
	at com.sap.glx.core.resource.impl.j2ee.ServiceUserManager$ServiceUserImpersonator.run(ServiceUserManager.java:168)
	at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
	at java.security.AccessController.doPrivileged(Native Method)
	at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
	at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.glx.core.kernel.api.TransitionRollbackException: Exception during prepare, rolling back
	at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.rollback(AbstractTransactionBase.java:702)
	at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_prepare(AbstractTransaction.java:197)
	at com.sap.glx.core.kernel.mmtx.AbstractTransaction.commit(AbstractTransaction.java:78)
	at com.sap.glx.core.dock.storage.impl.StorageManagerImpl.reenter(StorageManagerImpl.java:1611)
	... 19 more
Caused by: java.lang.IllegalStateException: Maximum exclusive lock count exceeded. State = 65535
	at com.sap.glx.core.util.UpgradeableReentrantReadWriteLock$UpgradeableReentrantSynchronizer.tryAcquire(UpgradeableReentrantReadWriteLock.java:94)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireNanos(AbstractQueuedSynchronizer.java:1224)
	at com.sap.glx.core.util.UpgradeableReentrantReadWriteLock$WriteLock.tryLock(UpgradeableReentrantReadWriteLock.java:382)
	at com.sap.glx.core.kernel.trigger.node.LockingTreeJoinNode$JoinRow.tryLock(LockingTreeJoinNode.java:151)
	at com.sap.glx.core.kernel.trigger.node.LockingTreeJoinNode.lockRow(LockingTreeJoinNode.java:387)
	at com.sap.glx.core.kernel.trigger.node.LockingTreeJoinNode.processUpdatesSingleSide(LockingTreeJoinNode.java:517)
	at com.sap.glx.core.kernel.trigger.node.LockingTreeJoinNode.process(LockingTreeJoinNode.java:436)
	at com.sap.glx.core.kernel.trigger.core.BFSController.processNode(BFSController.java:265)
	at com.sap.glx.core.kernel.trigger.core.BFSController.update(BFSController.java:225)
	at com.sap.glx.core.kernel.trigger.impl.TriggerNetworkManagerImpl$SequentialController.update(TriggerNetworkManagerImpl.java:734)
	at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_trigger(AbstractTransaction.java:222)
	at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_prepare(AbstractTransaction.java:193)
	... 21 more


10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

5 Answers

Gabriel Cassel
Feb 28 at 06:13 PM
0
Olá Marcos!


Are you facing this issue for a specific process?


Please check the full trace collecting in this way:


Troubleshooting Wizard trace (SAP Note ##1332726) from when reproducing the problem.


Once inside the TSHW application, click on "Manage Incidents" and then on "Create". Give a name of your preference to the incident (BPM, for example), and in the table below add the following locations with the corresponding trace severities to be collected:


    com.sap.glx                     ERROR
    com.sap.bpem                    ERROR
    com.sap.tc.bpem                 ERROR


Once you're done, click on "Close" and then on "Start Diagnostics". When you're done with recreating the problem, click on Stop Diagnostics, and export the trace. Attach the resulting file to the incident. 


Check in the trace the Caused by for this issue.


Kind regards,
Gabriel Cassel
SAP Product Support
Share
10 |10000 characters needed characters left characters exceeded
Marcos Augusto Vieira da Rocha Mar 03 at 01:14 PM
0

Hi Gabriel,

Yes, this is the only process with this error.

the mistakes that have appeared are the same as those I mentioned above.

all process in bpms are locked. None are processed as per the attached image. always stop at the same stage of the workflow.

all processes are stopped at an intermediary stage like this. see that it is not a human task, so it should not be stopped in it.

Please, help me.


Share
10 |10000 characters needed characters left characters exceeded
Gabriel Cassel
Mar 05 at 05:15 PM
0

Hi Marcos,

Have this process worked before?

I think this is an error with the modeling for such process.

Thanks,

Gabriel

Share
10 |10000 characters needed characters left characters exceeded
Marcos Augusto Vieira da Rocha Mar 06 at 02:04 AM
0

multiple processes start and end without error. others give this error.

I have not found something that causes the process to fail.

Share
10 |10000 characters needed characters left characters exceeded
Gabriel Cassel
Mar 26 at 12:41 PM
0

Hi!

This issue was fixed by applying the KBA: 2619623 - Stuck Process Instances - BPM Actions in status Queue

Thanks!

Gabriel

Share
10 |10000 characters needed characters left characters exceeded