The target system HybrisCore at http://10.17.3.186:9001/datahubadapter is unavailable for target system publication id 136454

[Former Member]

Hi Experts ,

We have getting below issues in production environment as below :

The target system HybrisCore at http://10.17.3.186:9001/datahubadapter is unavailable for target system : The target system HybrisCore at http://10.17.3.186:9001/datahubadapter is unavailable for target system publication id 136454 and pool SAPORDER_INBOUND_POOL: java.net.SocketException: Connection reset

Can anyone please provide the details what could be the root cause and why it's happening.

Thanks in advance .

Regards,

[Slava · Accepted solution]

That means DataHub is trying to publish data to http://10.17.3.186:9001/datahubadapter and can't connect to it. Possible reasons:

1. There is no commerce-suite running on http://10.17.3.186:9001 (it's stopped or is deployed at a different host, or the host is not reachable due to network/firewall configuration) . See "Configuring Inbound Communication" in https://help.hybris.com/1811/hcd/e7dde442e14848d49bd021a2361f5d4b.html

2. Commerce suite is running but http is disabled or redirects to https and https is not correctly configured on the DataHub side. See https://help.hybris.com/1811/hcd/1dec8042f1944a9fb090967ebe770ceb.html

3. The connection is secured but user are not correctly configured for this call. See the document in item number 1.

[Former Member · Accepted solution]

Hi Slava ,

Thanks for your valueble inputs here .

But my concers is to find exact root cause of the issues .

Can we reproduced this issues in dev or stage environment so that i can sure about root cause of this issues .

Please find attached logs .

Thanks in advance .

Regards,link text

12312-unavaliable-datahub-adapter.txt

[Slava · Accepted solution]

Satish,

I can't point to exact root cause. I listed 3 items in my answer, which make the 3 (more like 5 actually) possible root causes. So, you have to verify all those conditions and find which one is causing the problem.

You can easily reproduce the problem in the stage environment. Create a Data Hub instance configure it and then simply stop the hybris system. You will get exactly same error but it does not mean it's the root cause in your production environment.

I recommend start troubleshooting those possible reasons one-by-one. For example,

1. make sure production hybris system is running,

2. make sure the IP is correct for the hybris platform.

3. check whether http://10.17.3.186:9001 is reachable from the Data Hub box (if possible you can even use a browser for that)

4. if it's reachable, make sure datahubadapter is deployed and correctly running in the platform, see Extensions tab in the hac.

One of those steps probably will fail. Depending on the failure, fix the problem.

[Former Member · Accepted solution]

Hi ,

Thanks for your update.