Folks;
I am running an (axis-based) SOAP web service inside a tomcat 5.5
environment to link two subsidiaries of our company. This service is
supposed to recieve messages including very large (> 100 MB) MIME
attachments. So far, recieving and decoding messages (small sizes, or
locally) works well, but external tests using the remote sender client
and bigger attachments always ends up like that:
[...]
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode: faultString: java.net.SocketTimeoutException: Read timed
out faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:
java.net.SocketTimeoutException: Read timed out at
java.net.SocketInputStream.socketRead0(Native Method) at
java.net.SocketInputStream.read(SocketInputStream.java:129) at
java.io.BufferedInputStream.fill(BufferedInputStream.java:21
[...]
This is bad. So, short question, given that modifying the calling
client is not possible to me: Where to tweak my setup to get rid of
that error? Is that an issue related to the tomcat setup or to axis?
Currently I am playing around with axis MessageContext.setTimeout(),
but documentation on that is rather limited - is this what I am looking
for?
TIA for any hints and bye,
Kris
--
Kristian Rink * http://zimmer428.net * jab: [EMAIL PROTECTED]
icq: 48874445 * fon: ++49 176 2447 2771
"One dreaming alone, it will be only a dream; many dreaming together
is the beginning of a new reality." (Hundertwasser)
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
