Weblogc BEA-000449 : Closing socket as no data read from it during the configured idle timeout of 5 secs

java weblogic-10.x
Mahesh Nair picture Mahesh Nair · Jun 4, 2010 · Viewed 73.6k times · Source

I have started seeing this message in my weblogic 10 log files. I am running an app with around 40-350 concurrent users. My questions are

  1. What does this error really mean
  2. How will it affect the users (if it does)
  3. What could be causing this

thanks

Answer

matt b picture matt b · Jun 4, 2010

What does this error really mean

Weblogic is closing a socket used to communicate with one of the server's clients because no data has been sent for more than five seconds, which is the value you have configured for Weblogic's idle timeout.

What could be causing this

Client programs connecting to your server, sending some data, and then either 1) not closing the connection or 2) disappearing.

Related questions

Viewing Deployed Apps in Weblogic Server

I am new to weblogic and I would like to find out how my files are arrange in Weblogic? I have used only Tomcat and this is the first time where I will deploy in a Weblogic Server. In Tomcat, …

Read More
Where is WebLogic Jar containing javax.servlet in 10.3?

I am trying to configure my path to include javax.servlet with WebLogic. WebLogic has split out the Jar files, so which one contains javax.servlet?

Read More
NameNotFoundException when calling a EJB in Weblogic 10.3

I have a EJB defined as this: package com.foo; @Stateless (mappedName="HelloWorld") public class HelloWorldBean implements HelloWorld, HelloWorldLocal .... When it's deployed to Weblogic (WL), it gets the name myBean. I'm not sure if this is important. I try to …

Read More