Azure instance number changes gives wrong status to the java tomcat app

Question

The documentation of microsoft says ( http://azure.microsoft.com/blog/2011/01/04/responding-to-role-topology-changes/ )
you receive a changing and a changed event when the instance number is changed.
In real live i see a changing, a changed and a stopping event.
After that my java application doesn't run the contextDestroyed, but does run the contextInitialized again.
I don't call the cancel methode on the changing event. So a stopping event is unexpected.
So why does i receive a stopping event? Is this a bug? And while i received a stopping event the server didn't preform a reboot, but my java app contextInitialized is called again? So why is that?
Any inside is appreciated?

Answer 1

Hi sir,
For this issue, I recommend you can refer to this blog:http://azure.microsoft.com/blog/2013/01/14/the-right-way-to-handle-azure-onstop-events/
When you received the onstopping event, the cloud service ILB could stop dispatch the request to this instance. And your instance may have 5 min to handler the uncompleted processor. And I wondered know how to code in your onstop() method in your project.
If your onstop method is canceled, you maybe not receive the instance reboot.
Regards,
Will
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.