We're looking into a persistence implementation for sandesha2 using hibernate and we've also looked at the WSO2 implementation. Does sandesha2 actually recover and restart message delivery after an unexpected shutdown? The reason I ask is that the inmemory storage manager is persisting the message context including the transports. The transports (http for instance) won't survive a shutdown, particularly if the transport is the back channel from a request. How would one go about persisting the message context in a way such that sequence recovery can occur? For instance, I have 10 messages in a sequence, I sent two and then lost power. Will delivery of those messages automatically restart at power up? If the create sequence request is sent but the response is not received, will another create sequence request be sent again? - Rich
