>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 or files then you hit that
limit after about 950 calls (the other FDs are overhead).
The underlying problem is usually forgetting to call close() on the
appropriate resource. You can't wait for the garbage collector to get
around to closing things. (You have to remember to close things even
when your code throws an exception; that's what finally{} is for.)
Two quick and dirty ways to test if this is the problem (both OS
specific, alas):
modify the per-process limit of FDs and see if the number of calls
you can make changes.
run "netstat" or "lsof" and look for lots of open handles
You say the problem is in the client side.. Make sure you're closing
everything you open yourself. If it's still showing the problem, it
may be in Axis' client code itself.
>On the client side I am using jdk1.3_02, and the most recent Axis
>code. The server is using Apache SOAP. My next step is to try another
>JDK version.
What OS is this on?
