Re: timeout troubles
"Scott Nichol" <[email protected]> Mon, 20 Dec 2004 11:53:27 -0500
| Newsgroups | gmane.text.xml.soap.user |
|---|---|
| Message-ID | <078b01c4e6b4$6d96aef0$6401a8c0@northgate> |
You should move to Axis if you can. It continues to be developed and supports many specs that Apache SOAP does not: SOAP 1.2, WSDL 1.1, DIME, JAX-RPC all come to mind. Scott Nichol Do not send e-mail directly to this e-mail address, because it is filtered to accept only mail from specific mail lists. ----- Original Message ----- From: "Julien ALLANOS" <[email protected]> To: <[email protected]> Sent: Monday, December 20, 2004 11:21 AM Subject: Re: timeout troubles Selon Scott Nichol <[email protected]>: > The Java sockets classes did not provide any way to timeout the connect until > JDK 1.4. Prior to that, only I/O after the connection was made was subject > to timeout. The 2.3.1 release of SOAP does not support this new feature of > JDK 1.4. However, the current code base does. If you download the code from > http://cvs.apache.org/dist/soap/nightly/2004-06-22/, you will be able to have > a shorter timeout for the connect if you are using JDK 1.4 or later. > > Scott Nichol Thanks. I may be a bit scared of using a nightly build in a production environment though... Is there any documentation about how to set the connection timeout with this version of SOAP? I was also thinking about moving to Axis, does it have such a connection timeout feature? are there other benefits of moving to Axis? thanks. -- Julien ALLANOS Silicomp-AQL