On 16/03/2010 02:01, Song Thuy Nguyen wrote:
The thing is, I'm using the failover behaviour in Apache Synapse (Enterprise Service
Bus). I can give Synapse a list of web service endpoints that have the same interface.
One is the primary service endpoint and the others are the backups in case
Hello,
usually you will get a The requested resource /XYZ is not available response
when you call an unavailable web service on Apache Tomcat. However, for a
special use case I don't want Tomcat to answer to requests for a
unknown/unavailable web service. I just want Tomcat to ignore it
I don't think you can do that. After Tomcat accepts the HTTP
connection and decides whether to respond, it's too late to pretend
there's no server there. The user's web browser displays a different
error message for no server (something like can't establish a
connection) vs. server timeout
Len Popp wrote:
I don't think you can do that. After Tomcat accepts the HTTP
connection and decides whether to respond, it's too late to pretend
there's no server there. The user's web browser displays a different
error message for no server (something like can't establish a
connection) vs.
The thing is, I'm using the failover behaviour in Apache Synapse (Enterprise
Service Bus). I can give Synapse a list of web service endpoints that have the
same interface. One is the primary service endpoint and the others are the
backups in case the primary endpoint become unavailable for some
