<Warning> <Socket> <BEA-000449> <Closing socket as no data read from it during the configured idle timeout of 5 secs>
This is because I sometimes have multiple browsers/windows open of same application connections due to stopping and start the server each time opens a new window. Closing down all browsers/windows related to the application connection can avoid the problem.
If you want to follow this solution. Go to Admin console -> Click on Domain->Configuration->Log Filters->create new Log filter.
I added this line in expression "(MESSAGE !='Closing socket as no data read from it during the configured idle timeout of 5 secs')"
Go to your server-(for each server you have to set it individually)->Logging->Advanced->Select this log filter for Standard Out or log file.
Set the following details.
Action Capacity tuning of the server is required.
=====
Please set the parameter -Dweblogic.client.socket.ConnectTimeout=XXX, in
startupscript of the
AdminServer, and all the managed servers under JAVA_OPTIONS and check whether
it is showing the same behaviour or not, where "XXX" is the value in ms.
-Dweblogic.client.socket.ConnectTimeout=500
I hope you already set this tuning.
====
Set the duration to a higher value-
Managed Server > Protocols > HTTP > Duration: 60 seconds
The amount of time the server waits before closing an inactive HTTP connection.
good News for this issue.
I found one BUG for this issue 9392977
Please check further details from Support Team on this issue.
Regards,
Kal.
Edited by: kalyan Pasupuleti on Jul 12, 2011 12:34 PM