DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18277>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18277 Socket Timeouts for Axis Clients ------- Additional Comments From [EMAIL PROTECTED] 2003-07-23 08:22 ------- Copy paste from mailing list -- subject : Read Timeout (Again) > Axis is an implementation of among other packages the standardized > javax.xml.rpc classes. As a programmer working with external libraries I > have little control over (or time to invest in), I tend to shield myself > as much as I can from implementation dependent API's. So I use the > standard API's , just like I do with xerces and xalan. However to > control the timeout I would have to cast my javax.xml.rpc.Call instance > to org.apache.axis.client.Call (As far as I know, if'm wrong then by all > means correct me and forget about the rest of this comment ;-p). This is > ugly, dirty code that can easily break if I switch implementation but > still leave the axis.jar somewhere in the classpath of the IDE. It will > cause a runtime class cast exception. this is a good point. a very good point. If you want a timeout of >60secs, you have to hard bind to Axis, and not pure JAX-RPC. this argues strongly in favour of -cranking up the timeout to something much bigger (like 600s) -providing a JAX-RPC compatible means of setting it, ie. through Call.setProperty -maybe a declarative way of doing it (which requires a client side WSDD) we could do it with Call.setProperty() easily enough: Call.setProperty("axis.connect.timeout",new Integer(0));
