L
lecuyer
Guest
If you look at the java openclient programming book, you will observe a number of properties that might help you manage the connections made by the client to the appserver. These properties can be set for the entire application or for a specific appobject, depending on your requirements. The properties most applicable to your problem are: PROGRESS.Session.connectionLifetime - The maximum number of seconds that a given connection can be used before it is destroyed. Connections whose lifetime exceeds the specified value are destroyed as they become available. Default is 5 minutes. PROGRESS.Session.idleConnectionTimeout - The amount of time, in seconds, that the client waits before it attempts to shut down idle network connections to the AppServer, based on client demand; that is, a connection that is not used longer than this interval is shut down. The default is 0, which means that connections are never disconnected because they are idle. PROGRESS.Session.maxConnections - The maximum number of connections that can be established for a given AppObject. The default is 0; that is, unlimited. PROGRESS.Session.minConnections - The minimum number of connections that can be established for a given AppObject. This defaults to zero. It should be noted that some connection trimming strategies do not allow the number of connections to go below this level. Take a look at the openclient programming book for more information on the options for setting these properties and how they affect the behavior of your application.
Continue reading...
Continue reading...