I've seen something like that happen if you have multiple threads trying
to use the same Call object on the client side, which is not thread
safe.
-Peter
David Turner wrote:
>
> I've been battling with a "SOAPException-Parsing error" for quite some
> time now when trying to deploy a simple service, and I've resorted to
> debugging the SOAP code to search out the problem. I've managed to get
> my service up and running on both Windows and Linux, but the one
> platform that I need it on doesn't work and gives me the above mentioned
> error.
>
> When I issue a uname command on the unix system the following system
> info is displayed: (informational only)
> OSF1 darwin.wi.mit.edu V4.0 1229 alpha alpha
>
> I thoroughly check all possible places for any parser conficts, but
> didn't find any that I know of.
>
> Using TCP Tunnel Monitor I know a good soap envelope was sent, but what
> I get back is a Internal Server Error with an incomplete SOAP envelope
> for the fault. During debugging I found that a NullPointerException was
> thrown when trying to extract the Call from the Envelope, which would
> account for the Fault being sent back in the first place. Still trying
> to determine why the NullPointerException was thrown -- need further
> debugging on that one.
>
> I checked the response in the RPCRouterServlet to see what was being
> sent back and it was a complete SOAP envelope that contained the Fault.
> What I don't get, and is probably the cause of the parsing error, is the
> fact the TCPTunnelMonitor is showing an incomplete SOAP envelope.
> Looking at TCPTunnelMonitor I'm losing data in the response.
>
> Has anybody run into this? Any ideas? Need help!
>
> --
> David Turner <[EMAIL PROTECTED]>
> Senior Software Engineer
> Whitehead Institute/MIT Center for Genome Research
> One Kendall Square, Bldg. 300
> Cambridge, MA 02139-1561 USA
> phone 617-252-1573 / fax 617-252-1902
