Common PeopleSoft Integration Broker Issues–Part 2

Integration Broker: Message Instance stays in STARTED status.

Possible cause: 

1. All Message Handlers have crashed or have been brought down. Processing will resume when Message handlers come brought back up 

2. The Message dispatcher processing the message is on another machine, and either the machine or the application server domain is down. 

Integration Broker: Message Instance stays in WORKING status.

Possible cause:

1. Message 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.

Publication Contract not created

Possible cause:

1. Channel routing rules not set up properly. 

Publication Contract stays in NEW status

Possible cause: 

1. Publication Dispatcher has crashed or has been brought down. 

2. Message Channel paused. 

3. Node paused 

4. Previous message had a status of RETRY, ERROR, or TIMEOUT.  

5. The Publication Contract is not at the top of the queue.  All Publication Contracts with the same Channel/ Subchannel and subscribing node are in the same queue