E-IB: Get " Destination node does not match the local node.(158,506)" on One Operation with Apparently Good Setup, while Ping Node and Other Operations Work Fine
(Doc ID 1935959.1)
Last updated on JUNE 15, 2018
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.54 and later
Information in this document applies to any platform.
On PeopleTools 8.54, after recent upgrade from PeopleTools 8.51, most Integration Broker service operations keep working fine, just as before, but one started to fail steadily.
The asynchronous one-way outbound operation TIME_DEVICE_EMPL_ATT_FULLSYNC.VERSION_1, aimed to a third party system, on each attempt to publish goes to status Error.
The Publication Contract Error Messages page shows 2 subsequent entries of the same error (1st entry, a with context prefix, 2nd entry, just the error itself):
Gateway error log shows no matching entries, gateway message log shows message being sent to a PeopleSoft app sever via Jolt, and geting the error response from the app server.
IBInfo section of the operation request to the gateway shows ConnectorName HTTPTARGET as expected, but the ConnectorClassName value is PeopleSoftTargetConnector (?!).
Inactivation of the routing does not prevent the creation of publication contract, but the contract never reaches the status Done, and eventually ends up in status Timeout.
This started to happen after PeopleTools upgrade, as mentioned above.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!