Jun 012012
 Posted by on June 1, 2012 at 11:58 am Application Servers, FAQ, Oracle/BEA WebLogic Tagged with: ,  Add comments

In weblogic logs we see below errors many times while accessing application

input/output error: java.net.SocketException: Connection reset


Could not deserialize session data


These are some of the most common causes of the “connection reset” error:

The client browser was refreshed or closed. If the error message is reported because of this condition, it is often because there may be performance issues in the system. To solve the problem, find the bottleneck of the poor performance and eliminate it.
There’s a firewall between the client and WebLogic server, and the connection was dropped by the firewall. For this scenario, please set up the firewall properly. Network congestion makes the operation timeout. Relieve the network congestion and the problem should resolve.

© Incase of any copyright infringements please check copyrights page for faster resolutions.

Leave a Reply

Show Buttons
Hide Buttons