Problem While Setting a Timeout from a JRF WebService in a WebCenter Portal Framework Application
(Doc ID 2017726.1)
Last updated on NOVEMBER 01, 2022
Applies to:
Oracle WebCenter Portal - Version 11.1.1.6.0 to 11.1.1.9.0 [Release 11g]Information in this document applies to any platform.
Symptoms
Experiencing problems while setting a timeout using a WebService Proxy Client inside a WebCenter Portal Framework application.
In summary, what happens is that you attempt to set a timeout for the WebService client call and such seems not to take effect.
You can simply verify this, by setting some code around the WebService call, like:
Changes
In a simple JDeveloper Generic application and not using JFR webservices, the functionality works as expected.
USEFUL:
Do remember a couple of things:
- The timeout setting won't be really the timeout for the entire WebService client call ( request from the client + connection to the WebService + execution of the WebService + response to the client );
- You'll be only able to set the connection or the request/execution timeout of the WebService, not the overall timeout of the WebService client call itself.
A possible way out for this could be to use a Thread class (eg, extend it) and use a thread to invoke the WebService client and later after X time, kill it.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |