Message Timeout in Peoplesoft

Question

In configuration PSAPPSRV timeout is set to 300 seconds. There are instances when for an inbound syncrequest the processing time in Peoplesoft might take more than 300 seconds. Since IG doesnt receive a response within 300 seconds it reposts the same message again to Peoplesoft (with a different message transaction_id). Is there a way to stop these messages from being reposted? I do not want to change the timeout specified in the configuration file. I just want to stop these messages from being re-posted
SO Used: Inbound Synchronous
Message Type: Non-Rowset (transformed)
PT version : 8.51.10

Answer 1

Hi,
See this doc which explains how you can override the timeout on runtime for a specific service operation
E-IB: How to Override Default Timeout for Integration Broker Synchronous Service Operations (Messages) [ID 658690.1]
Also see PeopleBooks > Enterprise PeopleTools 8.51 PeopleBook: Integration Broker > Sending and Receiving Messages > Generating and Sending Messages > Overriding Synchronous Timeout Intervals at Runtime
This PeopleBooks uses the SyncServiceTimeout property of the IBInfo Class.
PeopleBooks > Enterprise PeopleTools 8.51 PeopleBook: PeopleCode API Reference > Message Classes
Snipet from PeopleBooks:
SyncServiceTimeout
Description
This property takes a time (in seconds). This time overrides the default HTTP timeout that is used for all requests. If you set this property, you can use this to read back the time, that is, set the time before the SyncRequest is executed, then see when it is changed in an implementation of the OnSend method.
Note. This property is only for synchronous requests.
Generally, you use SyncServiceTimeout to dynamically set the timeout value for a specific transaction. The http header file is modified to take this new parameter. In addition this value is sent to the gateway to be used for the http timeout. Use this so that a long running transaction will not timeout. In addition, you don't have to wait through the default period for a specific transaction to timeout.
The following is a typical example of using this property:
&MSG.SetXmlDoc(&xmlReq);
&MSG.IBInfo.LoadConnectorPropFromNode(Node.EAI)
&MSG.IBInfo.SyncServiceTimeout = 360000;
&MSG.IBInfo.ConnectorOverride = true;
&MSG_Resp = SyncRequest(&MSG, Node.EAI);
&xmlResponseDoc = &MSG.GetXmlDoc();
Setting the XML directly is not valid. You need to use the message object to set the value. In order for this to work you must override the connector properties, which means you must set up the connector properties for this transaction, using one of the load methods (such as LoadConnectorPropFromNode, LoadConnectorPropFromTrx, and so on.)
This property is read-write.