E-IB: Get "Destination node does not match the local node" on Duplicate Message that IN_ITMLOAD Publishes when Sending to External (non-PIA) Node (Doc ID 2025241.1)

Last updated on AUGUST 30, 2015

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.53 and later
Information in this document applies to any platform.

*** Last revision: 30-Aug-2015 ***

Symptoms

On PeopleTools 8.53, Integration Broker, using SCM Inventory 9.2 delivered "Item Loader" process IN_ITMLOAD to send out data to a non-Peoplesoft system.
The process uses the delivered service operation ITEM_SYNC, the operation has only one active outbound routing, and the routing is to the target external node XXXX.
The node is set up to use a suitable target connector: HTTPTARGET, JMSTARGET, or any other except PSFTTARGET (which is only to send to PeopleSoft app servers).

When the operation is triggered online individually, it works fine, a single message is sent over to the target node XXXX, successfully reaches it and is processed there.
However if it is triggered via IN_ITMLOAD, then, instead of a single outbound message, two messages / operations are generated with exactly the same payload data.
The first message successfully reaches the target its operation publication contract goes to status Done, but that of the second message fails with the below error:

Integration Broker Service: Destination node does not match the local node. (158,506)

That error blocks the message flow, each time the failing extra messaging service operation has to be menually cancelled/removed to allow the next ones to succeed.

On inspecting the gateway message log, IBInfo shows for the two messages the same destination node XXXX, but in connector info their connector class names differ:
Successful ones have ConnectorName as set up (JMSTARGET, HTTPTARGET, ...) with matching ConnectorClassName (JMSTargetConnector, HttpTargetConnector, ...).
The failing ones have the same ConnectorName per the setup, but its ConnectorClassName does not match, it is PeopleSoftTargetConnector, incorrect here.

For example:

Good:


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms