Saturday 21 May 2016

Closing socket as no data read from it on 10.xx.xx.xx:14,525 during the configured idle timeout of 5 secs+OTM 637



Issue
+++
INFO | 2016/04/09 23:18:31 | <Apr 9, 2016 11:18:31 PM CDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 10.xx.xx.xx:14,525 during the configured idle timeout of 5 secs>
INFO | 2016/04/09 23:18:31 | <Apr 9, 2016 11:18:31 PM CDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 10.xx.xx.xx:14,524 during the configured idle timeout of 5 secs>
INFO | 2016/04/09 23:18:31 | <Apr 9, 2016 11:18:31 PM CDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 10.xx.xx.xx:61,991 during the configured idle timeout of 5 secs>
INFO | 2016/04/09 23:18:31 | <Apr 9, 2016 11:18:31 PM CDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 10.xx.xx.xx:61,990 during the configured idle timeout of 5 secs>

Solution
++++++++
As per the update received from the development team, those are just connections from the Weblogic to another server timing out because there was no activity.

No comments:

Post a Comment