We are using WL8 to deploy our applications.Soon we are going to migrating to 10.x.
Here my problem is we have a connection pool in wl8 server whose allowed connections limit is 40.
Whenever it reaches the count of 40 it is bringing the managed server down.
So to eradicate this issue we are daily monitoring the connections count and restarting managed server as and when it reaches 30.
So,to minimize our efforts we thought to write a script which will calculate the connection count on hourly basis,and restart the managed server when the connection count reached to 30.
since you have mentioned that the migration has happened to WL 10.x . I am guessing that the issue is currently with WL10.x domain.
In normal case when the db pool reaches the max limit (in your case 40) it use to throw [Resource unavailable] exception when the connection request arrived . and then the db pool will be put into Overloaded state
but I'm not sure why it kills the wl server .
please check the server logs while the server is going down . to find the root cause for the shutdown . Wl server usualy says something like this in the logs
<shutdown requsted by <user> > / <JVM called shutdown hook>
the first one is normal shutdown issued by any user . the second one is a JVM overload issue (OOM/Stuck Thread...)
if possible trigger a thread dump during the issue .
Joined: Aug 23, 2012
Thanks for your responses.
We are yet to migrate this server to 10.x.
Surely i will go through the logs to identify the issue.
Here my intention is to get the connection pool active connections count through a script which will elaborate my coding skills.
We have another option to increase the connection pool max limit but we are trying to write a script rather identify the issue.
Infact,In this environment we have 1 admin and 6 managed server out of which we monitor only admin and one managed server which we are talking now.
subject: Connection pool bringing the managed server down.