Integration Broker Troubleshooting Guide

Integration Broker – 8.40 -- Troubleshooting Guide

Publication Process

Problem: Publication Contract not createdPossible Cause:1. No Publication PeopleCode exists or PeopleCode is incorrect. Check OnRouteSend

PeopleCode event from the message definition.2. Explicit routing specified instead of Implicit on Node definition.3. No outbound transactions specified on Remote Node defintion.4. Check the PSNODESDOWN table. Make sure there are no rows in it.

Problem: Publication Contract sits in NEW statusPossible Causes:1. Message Channel is PAUSED2. Publication Dispatcher has crashed or has been brought down.3. Node is PAUSED 4. Previous message had a status of RETRY, ERROR, or TIMEOUT. 5. After unsuccessful PING, please query to make sure that no row was added to

PSNODESDOWN; otherwise it will hold up the message queue.6. Incorrect Gateway URL defined on Message Node.7. See Solution ID 200778756 “Integration Broker: Master Solution for Messages stuck

in New status”

Problem: Publication Contract stays in RETRY statusPossible Causes:1. The remote node cannot be “pinged” successfully. The publication contract will be processed

when the remote node comes back up.2. No publication handler available, either because it’s crashed or it has been brought down

Problem: Publication Contract sits in WORKING statusPossible Causes:1. The publication handler processing the contract is on another machine and either the

machine or the domain is down. Processing should continue when the pub/sub system on the other machine comes back up.

2. Single threading on the application server is making things slow…if the Pub/Sub processes are running

3. Publication Handler has crashed, or been brought down.

Problem: Publication Contract is in TIMEOUT statusPossible Causes:1. Transaction is not setup in the target node definition. Check APPSRV.LOG file for probable

cause.2. Subscribing Node is Paused.3. Message Node URL is incorrect.4. No Subscription PeopleCode exists on Subscribing system, or Subscription PeopleCode is

incorrect.

PeopleSoft, Inc. Proprietary & Confidential Page 1 of 4Integration Broker 8.40 Troubleshooting Guide 04/19/23 5:23 PM

5. An exception occurred on the target application server (look in APPSRV.LOG file for details) verify the following:

a. Source node defined in target databaseb. Verify correct password on node, target and source (if using passwords)c. Message or Channel not defined in target databased. Incorrectly routed reply. Check Gateway for correct machine address of target nodee. No target local node definedf. Bad XML syntax

Problem: Publication Contract is in ERROR statusPossible Causes:1. Message Node URL is incorrect. Check the Primary URL value on the remote node

definition.2. Subscription PeopleCode is bad.

Subscription Process

Problem: Subscription Contract not created.Possible Causes:1. Message Subscription is inactive. Activate from message definition.2. Transactions not set up properly.

Problem: Subscription Contract sits in NEW statusPossible Causes:1. Application Server down.2. Pub/Sub processes not configured on App Server domain.3. The Subscription Dispatcher has crashed or has been brought down.4. Message definition not active.5. Message channel paused.6. Node paused.7. Previous Message had errors or timed out.8. If you’re missing a row in PSAPMSGSUBPRCID, do the following:

insert into PSAPMSGSUBPRCID values(0)9. If message is publishing locally, check the “Generate Subscription Process

Instance” checkbox in the Subscription properties.

Problem: Subscription Contract sits in STARTED statusPossible Causes:1. Subscription Handler down2. If there is a Component Interface called in the Subscription PeopleCode, make sure the

target component online is valid.

Problem: Subscription Contract sits in WORKING statusPossible Causes:1. No Subscription PeopleCode exists2. Subscription Handler crashed while processing message.


Problem: Subscription Contract in ERROR statusPossible Causes:1. Message channel property if ‘ORDERED’ will allow subscription contracts to go in random

order. This will cause FULLSYNC message to error out when the Transaction wassubscribed before the Header.

2. Subscription PeopleCode errors.3. Application Data errors.4. Verify autonumber sequence

Problem: Subscription Contract is in EDIT statusPossible Cause:1. Message was edited and has yet to be resubmitted for processing.

Problem: Subscription Contract is in RETRY statusPossible Causes:1. Subscription PeopleCode is empty. 2. Message Definition on target node is not active

Other Possible Problems

Problem: Cannot find message in Message MonitorPossible Causes:1. User does not have security for the message channel. Check Permission Lists.2. The Message Monitor criteria have filtered out the message.

Problem: Messages are being processed in an incorrect orderPossible Cause:1. The Channel has been partitioned, and the resulting subchannels do not match what was

assumed for the ordering of the messages.2. Unorderd processing is activated in the Channel definition.

Problem: Message Instance not createdPossible Cause:1. Message is inactive.2. Duplicate PubID on the publication database. Check appsrv.log for this error.

Problem: Message Instance stays in NEW status.Possible Causes:1. The Application server is down.2. Pub/Sub services not configured on Application Server domain.3. The Message Dispatcher has crashed or has been brought down.4. The Item is not at the top of the queue. All messages with the same Channel/ Subchannel

are in the same queue5. Channel is paused.


Problem: Message Instance stays in STARTED status.Possible Causes:1. All Message Handlers have crashed or have been brought down. Processing will resume

when Message handlers come brought back up2. The Message dispatcher processing the message is on another machine, and either the

machine or the application server domain is down.

Problem: Message Instance stays in WORKING status.Possible Causes:1. Message Broker Handler has crashed.2. The Message Handler processing the message is on another machine, and either the

machine or the application server domain is down. The Message handler working on the message is “blocked”. The service will timeout, and the Message Dispatcher will retry the message.

Problem: My Publish() PeopleCode finishes successfully, but there is no message in the Message Monitor.Possible Causes:1. The Message Definition is InActive.

Problem: Unable to ping a node.Possible Causes:1. The web server for the Gateway is down.2. The Gateway is not configured properly.3. The app server for the node is down.4. Verify URL is correct. Copy URL in browser address, should see:

PeopleSoft Integration GatewayPeopleSoft Listening Connector Status: ACTIVE

Problem: Message Channels delivered in PAUSED status.ACTION_REASONAIRLINE_TKTBUDGET_POSITIONEXPORT_COMPLIANCE_ORDER_STATUSMCTTSTPAY_AND_REMITPURCHASE_REQUISITIONQUALITY_DATA_SUBMITQUALITY_DATA_UPDATETREE_MAINT

Fix:Change the status to ‘RUNNING’ in order for the messages to process from ‘NEW’ to ‘WORKING’.


Documents

Integration Broker Troubleshooting Guide