Configuring the Timeout for 64-bit Java Business Service Calls

The Siebel server makes an EAI HTTP call to the Config Agent Tomcat server, that then calls the Java Business Service. The default timeout for HTTP calls is 120000 milliseconds (2 minutes). But in some cases, this timeout may not be long enough for the Java Business Service to complete its work and for the Tomcat server to pass the results back to the Siebel Server. If a call to an instance of a Java Business Service might take more than 120000 milliseconds (2 minutes) you can tell the Siebel Server to wait a longer time before timing out using the JBSTimeout parameter.

Here are some examples of Java Business Services:

  • EAI JMS Transport
  • EAI XSLT Service
  • Customer-created Java Business Service

From Siebel CRM 19.5 Update release, you can pass the JBSTimeout parameter with a value greater than 120000 milliseconds to increase the wait time for the response from the Tomcat server. This is an input argument to the Java Business Service.

Method Argument Method Argument Value (in ms) Description
JBSTimeout 180000 The default is 120000 milliseconds for an HTTP call from the Siebel Server to the Tomcat server. A value of 180000 milliseconds (3 minutes) is longer than the default. This value would be appropriate for Java Business Service calls that you know will take just under three minutes.
Note: JBSTimeout is not the same as ReceiveTimeout. ReceiveTimeout is specific to JMS Receiver calls. JBSTimeout is specific to Java Business Service calls.