Change the Web Service Timeout on a WebSphere JVM
The WebSphere JVM sets the web service call timeouts to the default value of 600 seconds. This is fine if the web service calls always completed in milliseconds. But, for some, that always is not the case.
If a web service call blocked for a long time, this would mean that JVM threads in the WebSphere Application Server would be blocked too. This is an issue because threads are finite. The longer the web services are blocked, more new requests would block even more threads until the JVM becomes unresponsive.
To fix this (or at least to protect the JVM), the recommendation is to lower the web service call timeout on every JVM in the system. The timeout value (shown in the screen shot below, see the "timeout") is set to 90 seconds.
Figure 1 Admin Console JVM Custom Properties
Change the Web Service Timeout on a WebSphere ESB Application
An individual application can over-ride the JVM timeout. If you’re using a JAX-WS binding, you need to define a new policy set that contains a HTTP transport policy as described in the WebSphere Application Server InfoCenter:
This policy set has a Connection timeout property (in addition to many other settings):
Figure 2 Defining a Policy Set Using the Admin Console
Once the policy set is defined, it can be imported in IBM Integration Designer
Export the policy set from the Admin Console:
and then import it in to IBM Integration Designer (File > Import > Web services > WebSphere Policy Sets).
At this point, you may have to restart IID to pick up the new policy set. Check to see if the policy set that you just imported is loaded in IID:
Figure 3 Windows > Preferences > General > Service Policies
Then select the import on the assembly diagram and on the Properties tab select the Binding > Policy Sets panel. Here you can select the default policy set for the binding.
Figure 4 AudatexMod Assembly Diagram in IID