Malisetti, Ramanjaneyulu wrote:
I looked into tuscany code, looks like timeout is not esternalized. By
default value was set to 240 sec. I should have been taken from ws-policy.
requestMC.getOptions().setTimeOutInMilliSeconds(/GLOBAL_AXIS_TIMEOUT/);
Actually it is externalized. You can assign a different value to the
Axis2BindingInvoker.GLOBAL_AXIS_TIMEOUT public field to change the timeout.
Simon
I am still searching for JMS operation timeout.
Regards
Raman
*From:* Malisetti, Ramanjaneyulu
*Sent:* Wednesday, October 06, 2010 6:20 PM
*To:* user
*Subject:* timeout for requests on binding
Hi,
If we have a service exposed by SCA and invoking service
operations from SCA client, sometimes operation may take longtime. Is
there a way to control timeout independent of transport. There may be
solution based on Axis timeout if binding is WS and similarly there may
be message timeout if binding is JMS. Is there a way to control timeout
independent of transport?
Regards
Raman
