RawItems in pending status is not composed after datahub restart

[Former Member]

We have restarted and redeployed our datahub server, and processing of items have stopped.

In backoffice datahub view we can see a lot of raw items pending, and the number is not decreasing - nothing is processed.

Using "https://env-url/datahub-webapp/v1/compositions?q=status:PENDING" shows a lot of compositions in pending state. They are not picked up, which might be related.

We have autocompose and autopublish activated, so processing should stutomatically, but it don't. Even posting a manual compose command, doesn't have any effect.

We are running Datahub version 6.6, receiving IDoc's through standard IDoc integration. The problem is related to GLOBAL pool.

Anyone experienced something similar, and have a suggestion for solution?

[former_member333910]

Data Hub integrity check should automatically begin compositions after restart when there are Raw Items in a PENDING state.

Does the Data Hub log show any errors? Did any extensions fail to load during startup? Are you running Data Hub in Standard or InMemory mode?

You have Compositions in PENDING but is there one stuck IN_PROGRESS?

I suspect the log will reveal something that will help us understand the root cause of your problem.

[Former Member]

We are running in standard mode, and we actually had some compositions stuck IN_PROGRESS.

Which is why we redeployed and restarted.

Logs says that IN_PROGRESS compositions where rolled back after restart. That took some time, but went on without any problems.

All extensions seems to be loaded fine, and so far we did not see any errors or exceptions in the log.

During the night we got some data processed through SAPCUSTOMER_INBOUND_POOL but everything related to GLOBAL pool seems stuck.

[former_member333910]

Hi Thomas, based on what your are describing I'd need the Data Hub logs to provide any additional analysis. I suggest you open a support ticket so that we can assist you further.

You mention you are running 6.6 but don't specify the specific version. Just a reminder to always use the latest patch version.