We have created a custom failover implementation for the webservice which is
deployed over two hosts.
URL1 and URL2 are placed in the configuration. The WS call is first tested
using a sample test soap message as the webservice may not be available and
checks if the webservice can accept requests. We use a custom client object
which uses clasess like PortType and BindingProvider to make the webservice
call and is then cached.
If in case the webservice fails in the middle of processing it tries
refreshes the custom client object using the URL2.
The issue we are facing is when the WS client tries hit the URL1 and do not
get the success response for some reason and fails (e.g mistyped URL or
something) then URL2 also fails even though it is working. We tested this by
reversing the order of the url. After doing some debugging we found that the
proxy/stub is being cached and even if we use URL2 it still uses URL1 which
has just failed and causes everything to fail.
--
View this message in context: http://www.nabble.com/sei-proxy-caching-tp25751545p25751545.html
Sent from the JAX-WS Development mailing list archive at Nabble.com.