Problem:
- Product Name: VisiBroker for Java
- Product Version: 4.5.1 P6, & 5.2.1
- Product Component: Client-side Connection Management
- Platform/OS Version: All
In order for a Visibroker 4.5.1 client to release a stub reference and its underlying connection the following three conditions must be met:
- The property vbroker.ce.iiop.ccm.connectionCacheMax should be set to 0 so that no unused connections are cached by the ORB.
- The stub reference should be set to null.
- The property vbroker.ce.iiop.ccm.connectionMaxIdle should be set to an appropriate value so that the underlying connection will be closed when it becomes idle.
This behavior has changed since VBJ 4.5.1.P6 and onward.
Resolution:
VBJ 4.5.1 Patch 6 and all subsequent releases introduced the following changes:
- The property vbroker.ce.iiop.ccm.connectionCacheMax=0 is no longer needed in this case. Instead, users can simply set the property vbroker.ce.iiop.ccm.connectionMax to appropriate connection limit to control the total number of client-side connections that are cached.
- The property vbroker.ce.iiop.ccm.connectionMaxIdle assumes units in seconds, not milliseconds.
- The stub no longer needs to be nulled out explicitly in order to release the underlying connection. However it is still necessary to set the stub reference to null in order for the stub to be garbage collected.
Support Case: 559644
#Security
#VisiBroker
