Hi, This is probably a stupid error on my part as I can't see how other people haven't encountered it .... yes I've been searching the archives !
I have a simple web service which does a jdbc query to various databases and returns a table of information in a string buffer. This has worked happily since beta2. But what I have found is that if the query is a large one ie it takes some time to run I get a socket exception - I first assumed this was size related at first but it is actually timing related , if the web service is delayed for 30 seconds then axis spawns another and another and so on when the first one completes the socket is messed up from the duplicate second request and fails. If I put a debug on a web service and hold it I get the same effect as well so is definitely timing. I discovered the issue on Beta2 but it still occurs on RC2 and version 1.0. I'm running Tomcat 4.0.3 which runs a servlet version of the web service with no problems regardless of delays. The fact that it takes exactly 30 seconds before a new thread is spawned suggests its almost a 'feature' can it be adjusted anywhere ? Any suggestions gratefully received! as I seem to be up against a brick wall on this one. Regards, Richard Downey Contenlo [EMAIL PROTECTED]
