Yep. Thats the way it happens. Sandesha keeps messages in its storage and keeps retrying.
In Sandesha2 the number of retransmissions depends in two policies.
1. Maximum Retransmission Count
2. Inactivity Timeout
Chamikara
On 10/13/06, Dennis Sosnoski <[EMAIL PROTECTED]> wrote:
Does Sandesha/Sandesha2 have known problems when the server is down at
the time the client is started? My assumption is that as long as a
persistent storage manager is configured Sandesha/Sandesha2 should be
able to accept messages even if the destination is currently
unreachable, and retain those messages for transmission even after a
restart.
- Dennis
--
Dennis M. Sosnoski
SOA, Web Services, and XML
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-296-6194 - Wellington, NZ +64-4-298-6117
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
