Subscription Process Problems

Possible subscription process problems include:


Subscription contract is not created.
Subscription contract is in NEW status.
Subscription contract is in STARTED status.
Subscription contract is in WORKING status.
Subscription contract is in ERROR status.
Subscription contract is in EDIT status.

Sub Contract Is not Created
No handler exists for the service operation.
Service operation handler is missing method.
Queue routing rules not set up properly.

Sub Contract Is in NEW Status
Application Server down.
Pub/Sub processes not configured on Application Server domain.
The Subscription Dispatcher has crashed or has been brought down.
Receiving queue is paused.
Receiving node is paused.
Previous service operation had errors or timed out.
No row was inserted into PSAPMSGSUBPRCID, To insert a row enter the following SQL statement in your Query tool use the following statement:
insert into PSAPMSGSUBPRCID values(0) Sub Contract Is in STARTED Status
Subscription Handler is down.
Target component is not valid.

Sub Contract Is in WORKING Status
Subscription Handler crashed while processing message.

Sub Contract Is in ERROR Status
Queue property if Ordered enables subscription contracts to go in random order, which causes FULLSYNC service operations to error out when the transaction is subscribed before the header.
Service operation handler PeopleCode errors exist.
Application data errors exist.

Sub Contract Is in EDIT Status
Possible cause is that the XML was edited and is not yet resubmitted for processing.