Sometimes an application server can really be a piece of puzzle that is so hard to solve. Recently encountered this problem when starting up the application server. The server starts up and initialize the JDBC connection pool. However it did not manage to fully initialize the JDBC pool. It is suppose to initialize the pool with 300 connection but it hit a snag at 191. The DB did not allow it to as it has reach the allowable session limit.
A few minute later, the session is release and the application server continue to initialize the pool. It continue to initialize the pool from the start and added another 300 connection to the pool. It now had a total of 491 connection. So is this a bug?
23 Aug: Just to add on, the server did not complain that it has more than the configured connections. The DBA also registered the higher number of connection.
No comments:
Post a Comment