SAP Knowledge Base Article - Preview

2856779 - High DB commit on DB due to high thread count on datahub node

Symptom

High thread count on Datahub nodes. All 200 tomcat threads were busy for a long time performing some operations on DB

Lot of threads stuck at the below stack trace related to hybris_sequence table:

- locked <0x00000004fb328ad8> (a com.hybris.datahub.service.sequence.impl.DefaultSequenceService$Sequence)
at com.hybris.datahub.persistence.jpa.util.impl.DefaultIdGenerationService.generateSequenceId(Ljava/lang/String;)J(DefaultIdGenerationService.java:26)
at com.hybris.datahub.persistence.jpa.util.JPABeanFactory.createBean(Ljava/lang/Class;)Lcom/hybris/datahub/persistence/jpa/mapping/HybrisManagedEntity;(JPABeanFactory.java:59)
at com.hybris.datahub.repository.jpa.impl.AbstractGenericJpaRepository.createNew()Ljava/lang/Object;(AbstractGenericJpaRepository.java:50)
at com.hybris.datahub.service.impl.DefaultDataLoadingModificationService.createNewAction(Lcom/hybris/datahub/runtime/domain/DataHubFeed;Ljava/lang/Long;)Lcom/hybris/datahub/runtime/domain/DataLoadingAction;(DefaultDataLoadingModificationService.java:65)


Read more...

Environment

SAP Commerce

Product

SAP Commerce Cloud 1.0

Keywords

High DB Commit DB Commit Datahub hybris_sequence DefaultSequenceService , KBA , CEC-COM-HUB , SAP Commerce Data Hub , 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.