Hi Chris,
Have you created a separate "parent" thread for ALL of the Soap
communication, possibly creating child threads within that thread for soap
specific tasks ? It sounds like you have got the SOAP IO engine running in
your root thread (e.g. Swings only thread) and hence you are not getting any
context switching to the UI. There is nothing to my knowledge special about
using apache soap in a multithreaded environment.
Hope that helps
Shaun O'Hagan
London UK.
-----Original Message-----
From: ext Chris Laws [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 18, 2001 5:16 PM
To: [EMAIL PROTECTED]
Subject: Apache SOAP threading
I am using Apache Tomcat SOAP to do distributed applications in Java. When
my client app sends a request to the server, it appears as if all threads on
the client side are paused until the response is received and processed from
the server. Sometimes the data sent from the server is of a relativly large
size which results in 10-15 seconds of total transaction time. While this
transaction is occuring, my user interface is frozen. Any attempt to isolate
the request/response process in its own thread has no effect. I'd like to be
able to allow the user to be able to access the interface without the
"freezing" effect. Any suggestions?
