Broker 10.5 | webMethods Broker Documentation | webMethods Broker Messaging Programmer's Guide | webMethods Messaging Administration | Configuring Administered Objects | Configuring Time-out for JMS Client Connections
 
Configuring Time-out for JMS Client Connections
In the previous webMethods Broker versions, it was difficult to identify whether a JMS client connection timed-out due to non-availability of Broker or because of a busy socket connection. The JMS client connections would time-out when the time assigned to the com.webmethods.jms.brokerTimeoutparameter elapsed.
The three new JMS properties improve the management of JMS client connection time-out. Set the JMS client time-out properties mentioned in the table below in one of the following ways:
*Assign the properties to the watt.config.systemProperties property in the Settings > Extended page in Integration Server Administrator.
*Set the properties in the wmjms.properties file.
Property
Description
com.webmethods.jms.brokerTimeout
Specifies the maximum time in seconds a JMS client connection will wait for a reply from Broker, irrespective of the socket being busy or idle. The default value is 60 seconds.
Set this property to a high value considering the time required for a huge file transfer. For example, assuming that one of the IS triggers using the connection alias takes about 50 minutes to transfer a large file, set com.webmethods.jms.brokerTimeout=3600 (1 hour)
com.webmethods.jms.brokerIdleSocketTimeout
Specifies the maximum time in seconds a JMS client waits on an idle socket before timing out. The JMS client senses the connection issue when it receives an idle socket time-out exception. The default value is 60 seconds.
Set this property to a small value so that an idle socket time-out can be discovered at the earliest. For example, set com.webmethods.jms.brokerIdleSocketTimeout=30
com.webmethods.jms.brokerTimeoutPostConnectionClose
Specifies the maximum time in seconds a JMS client will wait for any operation to be complete on a connection marked for closure. The default value is 30 seconds.
For example, if com.webmethods.jms.brokerTimeoutPostConnectionClose=30, the cluster connection waits for 30 seconds to complete any file transfer operation in progress before closing the cluster connection.