Websphere jdbc connection pool make the server done

Websphere jdbc connection pool make the server done

Symptom:
No repsone from WebSphere, no active apache thread and no active web container thread, all are busy waiting for a free jdbc connection but every connection are occupied. WebSphere jdbc connection pool is full, web container threads are hang up.

Solution:

1. Stop IBM http server using apachectl stop. Make sure there is no httpd process.
2. Stop WebSphere cluster and nodeagent.
3. Modify jdbc connection pool. Max=50, Min=5
4. Start WebSphere and apache.