> From: Nelson Minar [mailto:[EMAIL PROTECTED]]
> >After around 950 consecutive calls, I start to get a
> >"java.net.ConnectException: Operation timed out: connect"
>
> The underlying problem is usually forgetting to call close() on the
> appropriate resource.
Thanks so much, that's the insight
>After around 950 consecutive calls, I start to get a
>"java.net.ConnectException: Operation timed out: connect"
This sounds like it may be that sockets aren't being closed. A common
problem is that a lot of systems have a limit of 1024 file descriptors
per process; if you're not closing sockets
I have found a very peculiar behavior when heavily stressing
the Axis client library.
After around 950 consecutive calls, I start to get a “java.net.ConnectException:
Operation timed out: connect” The strange thing is that the
service side is fine. If I stop the
client and run it
