|
Problem(Abstract) |
In WebSphere® Application Server V4 or V5, a data source
can be tuned so that a firewall timeout will not drop connections. |
|
|
|
Resolving the
problem |
To maintain access to a WebSphere data source when a
firewall is present between WebSphere and the database server, set the
following properties on the data source:
For WebSphere Application Server V4 data sources (including V4 data
sources that are defined in WebSphere V5)
Idle Timeout = xxx
Orphan Timeout = xxx
Minimum Pool Size = 0
For WebSphere Application Server V5 data sources
Unused Timeout = xxx
Min Connections = 0
where xxx is half the value of the firewall timeout in seconds; for
example, if firewall timeout = 15 minutes = 900 seconds, then xxx = 450.
If a firewall is present between WebSphere V4 and the administrative
repository database, add these parameters to the admin.config file:
com.ibm.ejs.sm.adminServer.dborphanTimeout=xxx
com.ibm.ejs.sm.adminServer.dbidleTimeout=xxx
com.ibm.ejs.sm.adminServer.dbminimumPoolSize=0
where xxx is half the value of the firewall timeout in seconds; for
example, if firewall timeout = 15 minutes = 900 seconds, then xxx = 450.
With the properties set this way, WebSphere will timeout idle and
inactive connections before the firewall timeout is reached. Setting the
minimum connection pool size to zero allows WebSphere to timeout all
connections without being obligated to keep at least one in the pool. This
way, no connections remain to be killed by the firewall. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|