A couple of things that come to mind: 1. What happens if you do an HTTP GET, e.g. from a browser, to the SOAP router servlet URL?
2. What happens if you try to call a targetObjectURI that does not exist? 3. Have you run tcpdump on your server to see what is actually coming in and whether *anything* is going out? On 3 Jun 2003 at 11:40, Richard Wareing wrote: > Well, I was working happily with Apache Soap along with ksoap (on a > mobile handheld device), and they were talking to each other quite fine. > Then after the weekend I came back to work on things again, and boom > Apache Soap wouldn't give me any more SOAP (XML) responses. > > For example, something as simple as a ServiceMangerClient list command > simply sits there forever. The deploy command is similar. I know they > get TO the SOAP server as the commands are indeed executed on the server > side, but Apache SOAP refuses to send back any SOAP responses. > > After recognizing that attempts at fixing this were proving futile, I > blew the whole install of Apache Tomcat and Apache SOAP, reinstalled > from scratch. Guess what? Same problem :(. > > Anyone else have any ideas? :) My last resort is nuking Linux and > re-installing that, however I'd rather not stoop to such a Microsoft > solution to the problem :). > > Rich... > > > Scott Nichol Do not reply directly to this e-mail address, as it is filtered to only receive e-mail from specific mailing lists.
