Hi I have just committed this to trunk.
camel-jetty will now return 503 when shutting down. This allows you to process existing messages while new messages will be denied with 503. You can also suspend/resume the consumer from JMX console with the operations for that. It would be great if you have the time to test it on your end as well. On Tue, Apr 20, 2010 at 7:45 PM, Ilya S <devmailboxl...@gmail.com> wrote: > Hi Claus, > > Thanks for creating a ticket. I think Service Unavaliable should be > find for load balancer (LB). > > In my particular case load balancer will be checking some predefined > healthcheck/status page with a status info that can be parsed by LB. > E.g. every 5 seconds the LB will issue a GET request to some url, if > the returned status is negative, the LB will take the server out of a > pool. When we are about to perform maintenance, we will indicate in > our healthcheck page that the server is about to go down. Then, after > a delay we will initiate a gracefull shutdown. > > I now realize that with the health check page I can in fact simply use > the "Defer" option as you originally suggested. I will let the LB know > that we are about to shutdown via healthcheck page first, and so it > should stop redirecting new requests to the machine in question. > Eventually, all the in flight exchanges will finish, and the machine > can be completely shutdown. > > Thanks again, > > Ilya. > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
