Brad Davis [
http://community.jboss.org/people/bradsdavis] replied to the discussion
"SOAPProxy initialization and deployment ordering"
To view the discussion, visit:
http://community.jboss.org/message/541582#541582
--------------------------------------------------------------
SoapProxy is meant to take a service and expose it on the ESB. However, proxing services
exposed on localhost requires the services to be written in JBossWS. Otherwise, trying
to proxy a localhost service will cause the Server Restart to Freeze. The server will
get to the point of trying to proxy, and then will try and attempt to load the WSDL
definition to proxy from the LocalHost, which is not yet available because the server has
not completed starting up. This does not time out, and leads to an unresponsive SOA-P
server.
Additionally, in the case the Web Service being proxied is not on the same box, the
following situation could occur. If the SOA-P server is restarting and tries to fetch
the remote Service to proxy, if the remote service is temporarily unavailable, the whole
service containing the SOAP-Proxy will fail deploying. This is not ideal, since other
services may be dependant on the failed SOAP-Proxy service, leading to a domino affect of
many services failing.
Idealy, the service would start, and hitting the SOAP-Proxy would return a service
temporarily unavailable code, or Soap-Fault. However, it is crucial that the service
start and also that the service continues to periodically try and Proxy the remote
service to ensure when it comes online, the server can service requests appropriately.
So to summarize, I think it should be Lazily initialized, and in the case that the service
is unavailable when it does Lazily initialize, I believe that we should actively try to
re-engage with the Proxied Web Service. Otherwise, when the remote services comes back
online, if your organization has built against the ESB, even though the service is now
available, the ESB Service will remain indefinately down until server restart.
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/541582#541582]
Start a new discussion in JBoss ESB Development at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]