Data Hub to Admin Server not Working - Production

[Former Member]

Windows servers in a Cluster environment. Data Hub on one server, Production Admin with Data Hub extension on another. Data is coming into the Data Hub server successfully but never making it over to the Production server and I see no error logging on either server.

Customer data is coming from the Admin server to the Data Hub server then to C4C. So, that connection seems to be working fine.

How can I test the Data Hub connection going to the Admin server?

Data Hub log (XML omitted): 2016-07-28 11:30:13,291 [DEBUG][http-apr-8080-exec-8][com.hybris.datahub.sapidocintegration.spring.HttpInboundService] Idocintegration - Received IDOC XML :

2016-07-28 11:34:06,270 [DEBUG][http-apr-8080-exec-8][com.hybris.datahub.sapidocintegration.IDOCMappingService] The parsing of the IDOC took 250 milliseconds. 1 IDOCs, 6 fragments, 105 values. 2016-07-28 11:34:06,707 [INFO ][http-apr-8080-exec-8][com.hybris.datahub.service.feed.DataFeedActor] Loading 6 items to 'DEFAULT_FEED' data feed 2016-07-28 11:34:06,723 [DEBUG][http-apr-8080-exec-8][com.hybris.datahub.pooling.impl.GlobalPoolStrategy] Searching for global pool for feed 0 - DEFAULT_FEED 2016-07-28 11:34:07,676 [DEBUG][defaultTaskExecutor-3][com.hybris.datahub.service.impl.DefaultEventPublicationService] Publishing data hub event : DataLoadingStartedEvent{actionId=818641, feedId=0, poolId=0, itemCount=6} 2016-07-28 11:34:07,817 [INFO ][http-apr-8080-exec-8][com.hybris.datahub.sapidocintegration.spring.HttpInboundService] The processing of the MATMAS04(MATMAS04) tag took 234526 milliseconds. 2016-07-28 11:34:07,817 [DEBUG][defaultTaskExecutor-4][com.hybris.datahub.service.impl.DefaultEventPublicationService] Publishing data hub event : DataLoadingCompletedEvent{actionId=818641, feedId=0, itemCount=6, status='COMPLETE'} 2016-07-28 11:34:07,832 [DEBUG][defaultTaskExecutor-4][com.hybris.datahub.c4c.service.impl.DefaultCompositionTrigger] DataLoadingCompletedEvent received for pool GLOBAL 2016-07-28 11:34:07,848 [DEBUG][defaultTaskExecutor-5][com.hybris.datahub.service.impl.DefaultEventPublicationService] Publishing data hub event : InitiateCompositionEvent{poolId=0} 2016-07-28 11:34:07,848 [INFO ][defaultTaskExecutor-4][com.hybris.datahub.sapcoreconfiguration.event.AutoComposeEventListener] Pool GLOBAL(0) registered for composition 2016-07-28 11:34:07,848 [DEBUG][defaultTaskExecutor-4][com.hybris.datahub.sapcoreconfiguration.callback.impl.CallbackTriggerTimerImpl] Callback registered for trigger callback: com.hybris.datahub.sapcoreconfiguration.event.AutoComposeEventListener@2e262037 2016-07-28 11:34:07,848 [DEBUG][defaultTaskExecutor-4][com.hybris.datahub.sapcoreconfiguration.callback.impl.CallbackTriggerTimerImpl] Current callbacks: [com.hybris.datahub.sapcoreconfiguration.event.AutoComposeEventListener@2e262037] 2016-07-28 11:34:07,848 [DEBUG][defaultTaskExecutor-4][com.hybris.datahub.sapcoreconfiguration.callback.impl.CallbackTriggerTimerImpl] Start trigger thread 2016-07-28 11:34:07,848 [DEBUG][defaultTaskExecutor-4][com.hybris.datahub.sapcoreconfiguration.callback.impl.CallbackTriggerTimerImpl] Trigger Thread created with sleep time: 10000 2016-07-28 11:34:07,895 [DEBUG][Thread-10][com.hybris.datahub.sapcoreconfiguration.callback.impl.CallbackTriggerTimerImpl] Trigger Thread starts notifying callbacks [com.hybris.datahub.sapcoreconfiguration.event.AutoComposeEventListener@2e262037] in 10000 msec 2016-07-28 11:34:17,901 [DEBUG][Thread-10][com.hybris.datahub.sapcoreconfiguration.callback.impl.CallbackTriggerTimerImpl] Trigger Thread starts notifying callbacks 2016-07-28 11:34:17,901 [DEBUG][Thread-10][com.hybris.datahub.sapcoreconfiguration.callback.impl.CallbackTriggerTimerImpl] Call trigger for 1 callbacks 2016-07-28 11:34:17,901 [DEBUG][Thread-10][com.hybris.datahub.sapcoreconfiguration.callback.impl.CallbackTriggerTimerImpl] Call trigger for callback: com.hybris.datahub.sapcoreconfiguration.event.AutoComposeEventListener@2e262037 2016-07-28 11:34:17,901 [INFO ][Thread-10][com.hybris.datahub.sapcoreconfiguration.event.AutoComposeEventListener] Initiate composition for pool: GLOBAL 2016-07-28 11:34:17,901 [DEBUG][defaultTaskExecutor-6][com.hybris.datahub.service.impl.DefaultEventPublicationService] Publishing data hub event : InitiateCompositionEvent{poolId=0} 2016-07-28 11:34:17,901 [DEBUG][Thread-10][com.hybris.datahub.sapcoreconfiguration.callback.impl.CallbackTriggerTimerImpl] Callback unregistered for trigger callback: com.hybris.datahub.sapcoreconfiguration.event.AutoComposeEventListener@2e262037 2016-07-28 11:34:17,901 [DEBUG][Thread-10][com.hybris.datahub.sapcoreconfiguration.callback.impl.CallbackTriggerTimerImpl] Current callbacks: [] 2016-07-28 11:34:17,901 [DEBUG][Thread-10][com.hybris.datahub.sapcoreconfiguration.callback.impl.CallbackTriggerTimerImpl] Disable trigger callback: com.hybris.datahub.sapcoreconfiguration.event.AutoComposeEventListener@2e262037 2016-07-28 11:34:17,916 [DEBUG][Thread-10][com.hybris.datahub.sapcoreconfiguration.callback.impl.CallbackTriggerTimerImpl] Disable Trigger Thread 2016-07-28 11:34:17,916 [DEBUG][Thread-10][com.hybris.datahub.sapcoreconfiguration.callback.impl.CallbackTriggerTimerImpl] Trigger Thread disabled and finished

[former_member224482]

What is an "Admin Server" ?
I am also not aware of any integration with C4C using IDOCs on the Data Hub.

[Former Member]

The Admin server is the cockpit server. There are no C4C iDocs. Customer data is sent from hybris to the data hub and then to C4C.

[former_member224482]

There certainly are IDOCs. In the provided log com.hybris.datahub.sapidocintegration is a class used only for processing IDOC from ERP.

 The processing of the MATMAS04(MATMAS04) tag took 234526 milliseconds.

[Former Member]

My reply was to your statement "I am also not aware of any integration with C4C using IDOCs on the Data Hub". We are not sending C4C data into hybris. We are getting C4C data from hybris to the ERP - i.e. C4C.

[Former Member]

I am seeing the following in the Admin logs. They are related to the y2ysync of itemChangesProcessor. Could this be the cause of the problem?

INFO | jvm 1 | main | 2016/07/28 09:37:41.987 | ERROR [Task-master-poll] [DefaultTaskService] Calling error handler of task marked running on node 0: 8840873378742 INFO | jvm 1 | main | 2016/07/28 09:37:42.205 | ERROR [Task-master-poll] [DefaultTaskService] Calling error handler of task marked running on node 0: 8840873444278 INFO | jvm 1 | main | 2016/07/28 09:37:42.205 | ERROR [Task-master-poll] [DefaultTaskService] Calling error handler of task marked running on node 0: 8840873509814 INFO | jvm 1 | main | 2016/07/28 09:37:42.205 | ERROR [Task-master-poll] [DefaultTaskService] Calling error handler of task marked running on node 0: 8840873542582 INFO | jvm 1 | main | 2016/07/28 09:37:42.205 | ERROR [Task-master-poll] [DefaultTaskService] Calling error handler of task marked running on node 0: 8840873608118 INFO | jvm 1 | main | 2016/07/28 09:37:42.205 | ERROR [Task-master-poll] [DefaultTaskService] Calling error handler of task marked running on node 0: 8840873640886 INFO | jvm 1 | main | 2016/07/28 09:37:42.205 | ERROR [Task-master-poll] [DefaultTaskService] Calling error handler of task marked running on node 0: 8840873673654 INFO | jvm 1 | main | 2016/07/28 09:37:42.205 | ERROR [Task-master-poll] [DefaultTaskService] Calling error handler of task marked running on node 0: 8840873706422 INFO | jvm 1 | main | 2016/07/28 09:37:42.330 | ERROR [Task-master-poll] [DefaultTaskService] Calling error handler of task marked running on node 0: 8840873739190 INFO | jvm 1 | main | 2016/07/28 09:37:42.330 | ERROR [Task-master-poll] [DefaultTaskService] Calling error handler of task marked running on node 0: 8840873771958enter code here