I would like to have an important piece of advice from ranchers on tuning our production WebLogic server - currently we are faced with the following scenario: We are performing load test on our server/application. Our application deployed on a managed server is not able to handle more than 650-700 sessions (cumulative count). Thereafter the server goes into 'Warning' state.
Exception thrown on the console is:
java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
Reason: 'ThreadPool has stuck threads'
We understand that the error has got something to do with tuning the server. It would very nice if you could throw some light towards resolving this seemingly simple but severe problem we are faced with.