This week's book giveaway is in the Agile forum.
We're giving away four copies of Head First Agile and have Andrew Stellman & Jennifer Greene on-line!
See this thread for details.
Win a copy of Head First Agile this week in the Agile forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Connection Reset By Peer Errors  RSS feed

chanzeb cecak
Posts: 6
Oracle Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello All,
We are seeing errors on some of our QA testing scripts that intermittently throw Connection Reset By Peer errors.

The Test scripts submit requests via F5 which forwards requests to Apache (2.2.21) with a mod_jk load_balancer with the following setting for each worker in the

worker1 props

and here is what is in the JBoss domain.xml for the AJP port from JBoss 7.1.1

<unbounded-queue-thread-pool name="SKUNKY.APP.AJP">
<max-threads count="300"/>
<keepalive-time time="3" unit="minutes"/>

Here is httpd.conf
Timeout 300 (Amount of time in seconds the server will wait for certain events before failing a request)
KeepAlive On (Enables HTTP persistent connections)
KeepAliveTimeout 15 (Amount of time the server will wait for subsequent requests on a persistent connection seconds.)
MaxKeepAliveRequests 100 (Number of requests allowed on a persistent connection)
TraceEnable Off

My question is that is it posisble that apache times out and closes the connection while jboss is still ready and working on the request?
What might be causing the Connection Reset By Peer error?
what am i missing here?
Any help is majorly appreciated!!
Sincerely Chan
Henry Wong
Posts: 23284
C++ Chrome Eclipse IDE Firefox Browser Java jQuery Linux VI Editor Windows
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

First, I can't answer your exact question... from the way you describe the problem, either we know it or we don't. Either we encountered the exact same thing, or we didn't.

You need to troubleshoot the problem. Take stack traces, and follow them. Add debugging messages and follow them. Etc. You need to do this to find the root cause of the problem, before you can attempt to fix it..

Unfortunately, you have a problem. A peer reset, is exactly that -- the peer did something unexpected. You are looking on the wrong side of the connection. I would recommend going to the other side of the connection. Is the other side your code too? If so, can you troubleshoot it?

  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!