similar way whether connected to tomcat
or httpd. As its tomcat whose behaviour is unexpected, I'm hoping someone
here can help me.
Thanks again,
Tim.
On 17 May 2011 09:10, wrote:
>
>
>
> -- Forwarded message --
> From: Tim Stibbs
> To: users@tomcat.a
I have a java client that is making a large number of calls to a servlet
running in a web app in tomcat 5.5.28. I have noticed that if the client
process runs for too long, the client machine runs out of ports throwing a
"java.net.BindException: Address already in use: connect". I thought that
java
