I couldnt able to make the timeout working in the web service call builder.
I created simple Webservice demo application where i added thread sleep code to simulate the timeout.
Added webservice call builder to invoke the demo webservice created above and tested. It is not getting timed out at all.. timeout is set to 30 seconds in the builder
tested with 1) 45 seconds
2) 90 seconds
3) 190 seconds
I even tested with "com.bowstreet.util.soap.SOAPRequest.defaultTimeout" property to 30 in override.properties still with no luck..
Could someone please guide me where i'm wrong or is there any known issue with WEF?
WEF : v 22.214.171.124
Thanks and regards
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
5 replies Latest Post - 2012-03-20T12:55:00Z by SystemAdmin
Pinned topic Webservice timeout is not working - web service call builder
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-03-20T12:55:00Z at 2012-03-20T12:55:00Z by SystemAdmin
Re: Webservice timeout is not working - web service call builder2012-03-06T14:35:43Z in response to SystemAdminHi All,
Further to that, it is evetually timing out after 5 min. But we are specifying as 30 seconds in the webservice call builder. :(
Thanks and Regards
mburati 060000VQ20352 PostsACCEPTED ANSWER
Re: Webservice timeout is not working - web service call builder2012-03-06T16:04:03Z in response to SystemAdminThe 6.1.5.x version is pretty old by now (you may want to consider upgrading at some point), but I believe that may have been the first version to offer the option of the older Apache AXIS web service support or the newer JAX-WS web service support. I believe there's an option in the WS builder that allows you to specify whether to use JAX-WS if it's available.
It's possible that the Apache AXIS Connection timeout was only a network "connection" timeout (how long to wait for issues connecting to the remote server) and not a read timeout. You may want to make sure you're using the newer JAX-WS support and see if the timeout works more like what you're expecting there. In either case, WEF doesn't manage the timeout itself, it passes it down to the web services layer (AXIS or JAX-WS) and asks it to manage the WS connection.
Re: Webservice timeout is not working - web service call builder2012-03-06T16:43:27Z in response to mburatiI checked again, Under Advanced sectionm, Use JAX-WS if available is enabled and i'm testing my client portlet in WAS v7.0. So it should be JAX-WS client.
I will check my demo web service also again and update.
DGawron 10000054HC50 Posts