Common PeopleSoft Integration Broker Issues

 

 

Publication Contract stays in RETRY status.

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.

 

 

Publication Contract stays in WORKING status.

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.

 

 

Subscription Contract not created.

1. Message Subscription is inactive.

2. Channel routing rules not set up properly.

 

 

Subscription contract - Local Node Issue.

For a message published by the local node, subscription contract not created for local node even when Message Subscription is active and "Invoke for local publication" is checked.

The local node was not included in the routing rules for the channel.  To subscribe to its own publications, the local node must be included in the channel routing rules.

 

 

Subscription Contract stays in NEW status.

1. The Subscription Dispatcher has crashed or has been brought down.

2. Message Channel Node or System paused.

3. Message Definition not Active.

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

5. The Subscription contract is not at the top of the queue.  All Subscription Contracts with the same Channel/ Subchannel and subscription owner are in the same queue.

 

 

All publication Contracts remain in a NEW status.

The queue was blocked from a Publication Contact that was in a status of ERROR from two weeks prior.  User did not see the error on the message monitor because he was only looking at today.  User entered xx day in and the ERROR publication appeared.  Canceled the error and all subsequent publication contracts processed successfully.  

 

 

Subscription Contract stays in STARTED status.

The Subscription Handler has crashed or has been brought down.

 

 

Subscription Contract stays in WORKING status.

1. The Subscription Handler has crashed or has been brought down. Check in Application Messaging Gateway Administrator

2. Also look for any errors in App Serv Log

 

 

Subscription Contract in ERROR status.

1. Subscription PeopleCode errors

2. Application data errors.

 

 

Subscription Contract in TIMEOUT status.

1. Subscription PeopleCode errors

2. If the message works sometimes, and sometimes does not this may be a problem with the application server configuration.  Tune up your application server min/max values, or reconfigure your domain to a medium or large domain.  Also, changing the recycle count for these services from 0 to 25,000 or 10,000 may eliminate this problem.

 

 

Integration Broker:  Unable to ping a node.

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 <tools release> Application Messaging gateway".

 

 

Access denied, source node not found.

Known bug: Message Node caching not working.  If a new node is added, reboot appserver.

 

 

Integration Broker:  "Bad Gateway, General Exception error .." message when pinging node.

Check Oprid/ Password of node on Configuration Servlet page. (http://?/servlet/gateway.administration)