Legolas Woodland wrote:
Hi
Thank you for reading my post.
I defined a datasource and connection pooling in my web application.
maximum size of pool is 32 ,
after some times that i deploy-undeploy the application in development
environment ,
derby console windows show which after starting shows connection numbers
, show some very high numbers
for example :
....
Connection number: 96.
Connection number: 97.
Connection number: 98.
Connection number: 99.
Connection number: 100.
Connection number: 101.
Connection number: 102.
does it means that i have 102 connection open over my database ?
If so , what is connection pool job ?
No, I don't think so. The message you refer to is printed every time a
connection is made, but nothing is printed when a connection is closed.
So, a total of 102 connections have been made to your database server
since it was started, but you cannot tell the number of active
connections from these messages (unless you know the connection-making
logic of your application).
When you redeploy your application, the connection pool is most likely
"invalidated", and new connections must be made (I guess you are using
some kind of application server?).
I am not sure if there is a way to determine the number of alive
connections to Derby. Can someone help us out on that?
Thanks,
--
Kristian
