Yet another hanging java.net.SocketInputStream.socketRead0... | performance stories

Yet another hanging java.net.SocketInputStream.socketRead0… | performance stories

Yet another hanging java.net.SocketInputStream.socketRead0… by perfstories I’m going to tell you about one more emergency in our production environment. So, we have a server with Glassfish, with 2 jdbc Oracle connection pools. One of these pools was usable, another wasn’t. Just was kept as a reminder of something ;). All external requests to this server were remote jdbc calls. The symptoms of this emergency were: It was impossible to ping usable jdbc pool (GF console -> Resources -> JDBC -> Connection Pools -> General -> ping). I mean ping request was just hanging; Oracle DBAs saw no problems with sessions, connections, etc.; Unusable pool could be pinged easily; The servers, which were using this server, hung up in a special way: their http request handlers pools exhausted gradually, then the servers appeared hanging for some time, then were in working state again, then again from the beginning (exhausted, hung, working). I had thread dumps as usual,

Read full article from Yet another hanging java.net.SocketInputStream.socketRead0… | performance stories