Why do you see “Max connections reached” errors in WebSphere?

Why does the system get frozen and I see “Maximum number of connections has been reached” error messages in WebSphere FFDC logs when running a IBM TRIRIGA server? Why is this happening? The system gets frozen and WebSphere FFDC logs ([WAS_install_root]/profiles/[profile]/logs/ffdc) report the following error:

[MM/DD/YY HH:MM:SS:mmm TTT] FFDC Exception:com.ibm.websphere.ce.j2c.ConnectionWaitTimeoutException SourceId:Max connections reached ProbeId:869 Reporter:com.ibm.ejs.j2c.PoolManager@98575e96
com.ibm.websphere.ce.j2c.ConnectionWaitTimeoutException: CWTE_NORMAL_J2CA1009
Maximum number of connections has been reached, and the connection request has been waiting longer than:ConnectionWaitTime. Two possible solutions : increase the max number of connections, or increase the:ConnectionWaitTime.:
Maximum Connections = :100
Current number of connections = :100
Connection Wait Timout = :180

Your IBM WebSphere server/JVM (IBM TRIRIGA server) has reached its JDBC Data Source Maximum Connection limit, and the system will stop responding to new processes requesting available connections to be used…

Check that the JDBC Data Source Connection Pool’s connections are set by server (WebSphere servers/JVMs). If the IBM TRIRIGA Best Practices for System Performance has been followed, all configuration necessary is in place. On page 18, under “3.1.3 Connection Pool”, it reads…

Continue reading