search cancel

The messagegtw in prod is not working. I'm getting a data_engine connection error.

book

Article ID: 190243

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Below is the error from the messagegtw log:
May 06 11:14:02:963 [/UIM_ServiceNow, messagegtw] NisDBConnectionHandler.initDatasource:77: retrieving the connection string from: /xxxxxxxx/xxxxxxxx/us1xxxxxxx55/data_engine
May 06 11:14:02:973 [/UIM_ServiceNow, messagegtw] Failed to parse connection string as : Received status (4) on response (for sendRcv) for cmd = 'nametoip' name = '/xxxxxxxx/xxxxxxxx/us1xxxxxxx55/data_engine'
May 06 11:14:12:975 [/UIM_ServiceNow, messagegtw] Failed to parse connection string as : Received status (4) on response (for sendRcv) for cmd = 'nametoip' name = '/xxxxxxxx/xxxxxxxx/us1xxxxxxx55/data_engine'
May 06 11:14:12:975 [/UIM_ServiceNow, messagegtw] (4) not found, Received status (4) on response (for sendRcv) for cmd = 'nametoip' name = '/xxxxxxxx/xxxxxxxx/us1xxxxxxx55/data_engine'
 at com.nimsoft.nimbus.NimSessionBase.sendRcv(NimSessionBase.java:610)
 at com.nimsoft.nimbus.NimSessionBase.sendRcv(NimSessionBase.java:561)
 at com.nimsoft.nimbus.NimSessionBase.getHostAndPortForName(NimSessionBase.java:426)
 at com.nimsoft.nimbus.NimNamedClientSession.<init>(NimNamedClientSession.java:28)
 at com.nimsoft.nimbus.NimObjectSender.connectNamed(NimObjectSender.java:78)
 at com.nimsoft.nimbus.NimRequest.sendImpersonate(NimRequest.java:253)
 at com.nimsoft.nimbus.NimRequest.send(NimRequest.java:219)
 at com.nimsoft.nimbus.lookup.DataEngineLookup.getConnectionStringsFromDataEngine(DataEngineLookup.java:128)
 at com.nimsoft.nimbus.lookup.DataEngineLookup.getConnectionStringsFromDataEngine(DataEngineLookup.java:94)
 at com.nimsoft.cet.utility.DataEngineUtil.getConnectionInfo(DataEngineUtil.java:103)
 at com.ca.uim.agileops.gateways.common.nisdb.NisDBConnectionHandler.initDatasource(NisDBConnectionHandler.java:79)
 at com.ca.uim.agileops.gateways.common.nisdb.NisDBConnectionHandler.<init>(NisDBConnectionHandler.java:38)
 at com.ca.uim.agileops.gateways.common.nisdb.NisDBConnectionHandler.getInstance(NisDBConnectionHandler.java:21)
 at com.ca.uim.agileops.gateways.common.UimMessageListener.processIncomingMessages(UimMessageListener.java:271)
 at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at com.nimsoft.nimbus.NimSubscribe.callbackBulkProxy(NimSubscribe.java:426)
 at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at com.nimsoft.nimbus.NimServerSession$NimServerSessionThread.performCallback(NimServerSession.java:216)
 at com.nimsoft.nimbus.NimServerSession$NimServerSessionThread.handleMessage(NimServerSession.java:169)
 at com.nimsoft.nimbus.NimServerSession$NimServerSessionThread.run(NimServerSession.java:123)
 
May 06 11:14:12:976 [/UIM_ServiceNow, messagegtw] Not able to callback for hubpost_bulk. Reason is: java.lang.reflect.InvocationTargetException

Environment

Release : 20.1

Component : UIM - MESSAGEGTW

Cause

- messagegtw data_engine configuration value

Resolution

On the machine where messagegtw was running, select the controller probe and press Ctrl-P to open the probe utility.

Run the nametoip callback and entered what was configured in the messagegtw for the data_engine address on the Primary hub.

   /XXX_UIM_PRD/XXX_Prd_Pri_WT1/aa1snnnnnn55/data_engine

but it failed.

Checked the data_engine address on the Primary but the case for the hostname was different (UPPERCASE).

   /XXX_UIM_PRD/XXX_Prd_Pri_WT1/AA1SNNNNNN55/data_engine

Therefore, changed the data_engine address to that value for the nametoip callback value in the Probe utility and it then succeeded (OK).

Updated the data_engine address in the messagegtw and restarted it and the connection was successful to the data_engine on the Primary.

Issue resolved.