Hi Chris
I was connecting locally to the same node over the local interface on
both EC2 and locally.
Since this went unresolved for sometime now for me, I investigated this
a bit myself, first looking at the Coyote source code, and then
experimenting with plain Java sockets. It seems like the issue is not
really Tomcat resetting connections by itself, but rather; letting the
underlying OS do it. It seems like it could be a but difficult to
prevent this with blocking sockets, but I hope what I've found
investigating this issue will help others in future
http://esbmagic.blogspot.com/2012/10/does-tomcat-bite-more-than-it-can-chew.html
regards
asankha
On 10/31/2012 09:27 PM, Christopher Schultz wrote:
Also, are you using a load balancer, or connecting directly to the EC2
instance? Do you have a public, static IP? If you use a static IP,
Amazon proxies your connections. I'm not sure what happens if you use
a non-static IP (which are public, but can change).
--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org
http://esbmagic.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
