SOAP Call object not thread-safe ?

[Haug Thomas]

Hi,

I have a question regarding the Call class on the client
side. 
Is it possible to use one instance of that class by concurrent
threads or is that class (or the classes it depends on) not 
thread-safe?
I suspect that this class is not thread-safe, because I 
receive the folllowing SOAP exception:

[SOAPException: faultCode=SOAP-ENV:Client; msg=Parsing error, response was:
FWK005 parse may not be called while parsing.;
targetException=org.xml.sax.SAXException:
                FWK005 parse may not be called while parsing.]
        at org.apache.soap.rpc.Call.invoke(Call.java:250)
        at
de.siemens.webframework.soap.client.GenericSOAPForwarder.sendSync(GenericSOA
PForwarder.java:153)
        at
de.siemens.query.RemoteRequestBase.sendSync(RemoteRequestBase.java:255)
        at
de.siemens.query.PatientRequest.getPatients(PatientRequest.java:164)
        at
de.siemens.webframework.soap.client.tst.ConcurrentSynchSOAPClient.run(Concur
rentSynchSOAPClient.java:38)
        at java.lang.Thread.run(Thread.java:484)

I'm using the SOAP toolkit 2.2 and Xerces1.4.0.

Is the concurrent usage of one Call object not intended ? I haven't found an
hint on that.
 
Thanks,
Thomas