Hello @Bernd van Oostrum, yes, checked into that but isn't this the default for all communications (which I don't want to change)?
Thanks, Hermann
------------------------------
Hermann Huebler
Alpium IT Solutions GmbH
Vienna
Austria
#IBMChampion
------------------------------
Original Message:
Sent: Mon June 17, 2024 07:46 AM
From: Bernd van Oostrum
Subject: Liberty: Configuration of JAX-WS communication timeouts like connection timeout, receive-timeout using server.xml
Hi Hermann,
Did you check setting sun.net.client.defaultConnectTimeout as a system-property or to set it as a JVM-option?
------------------------------
Bernd van Oostrum
Leuven
32478808505
Original Message:
Sent: Tue June 11, 2024 09:37 AM
From: Hermann Huebler
Subject: Liberty: Configuration of JAX-WS communication timeouts like connection timeout, receive-timeout using server.xml
We are accessing SOAP based WebServices ( using JAX-WS ) on WebSphere Liberty (24.0.0.5) and are looking for the best way to configure communication timeouts like connect-timeout, receive-timeout for our deployment. Ideally without having to change the Java code.
For JAX-RS there is a server.xml configuration element webTarget which seems to do exactly what we are looking for for the JAX-WS implementation.
For JAX-WS we have not found any server.xml configuration element to achieve that. The best we've found so far is using the http.conduit.client properties but these require modification of the Java code. Is there any equivalent to the webTarget configuration element for JAX-WS?
Note: I've also posted the question on StackOverflow
------------------------------
Hermann Huebler
Alpium IT Solutions GmbH
Vienna
Austria
#IBMChampion
------------------------------