SAP Knowledge Base Article - Preview

3158467 - Increasing number of threads waiting on de.hybris.platform.tx.DefaultAfterSaveListenerRegistry.enqueueChangesForAsyncNotification


  • Site and/or backend servers are slow or unresponsive.
  • Servers are continually restarting.
  • Thread dumps show an increasing amount of threads over time, all waiting on:
    "hybrisHTTP39" #391 daemon prio=5 os_prio=31 cpu=465.20ms elapsed=1632.64s allocated=68634K defined_classes=1 tid=0x00007fe76c8d3800 nid=0x40d03 waiting on condition  [0x0000700019f8b000]
       java.lang.Thread.State: WAITING (parking)
    at jdk.internal.misc.Unsafe.park(java.base@11.0.5/Native Method)
    - parking to wait for  <0x00000007d2319740> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
    at java.util.concurrent.locks.LockSupport.park(java.base@11.0.5/
    at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(java.base@11.0.5/
    at java.util.concurrent.ArrayBlockingQueue.put(java.base@11.0.5/
    at de.hybris.platform.tx.DefaultAfterSaveListenerRegistry.enqueueChangesForAsyncNotification(
    at de.hybris.platform.tx.DefaultAfterSaveListenerRegistry.publishChanges(
    at de.hybris.platform.tx.Transaction.notifyAfterSaveListeners(



All SAP Commerce Cloud versions with asynchronous notification mode enabled for after save events.



SAP Commerce Cloud all versions


hybris,aftersave,aftersaveevent,blocked , KBA , CEC-COM-CPS-PRF , Performance , CEC-COM-CPS-COR , SAP Commerce Core , 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.