Problem:

• Product Name: VisiBroker
• Product Version: 6.5 and above
• Product Component: Naming Service
• Platform/OS Version: All

When the JDataStore is unresponsive (i.e. abnormal shutdown, network congestion, packet drop), the socket peer connection on NameService side does not time out. It waits reading for data from the JDataStore after sending an SQL statement indefinitely. This article is applicable on both HA or non-HA JDataStore configurations and other Database vendors too.

Resolution:

In order to enforce time out between the Naming Service and the database service, a new property (vbroker.naming.queryTimeout) is introduced, which takes an an integer value for the time duration in seconds. The default is zero (0), which will wait indefinitely for data from the JDataStore. This property is added for CR9991.

prompt > nameserv -config nameserv.config -J-Dvbroker.naming.queryTimeout=10

This timeout value is passed to "Statement.setQueryTimeout()" when a client does a bind, resolve or rebind operations. This feature is effective on any Database vendor that supports query timeout setting. An SQLException will be thrown when setQueryTimeout() is not supported by the JDBC driver.