You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by Dennis Sosnoski <dm...@sosnoski.com> on 2006/10/12 22:41:03 UTC
Operation when server is down
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: Operation when server is down
Posted by Jaliya Ekanayake <jn...@gmail.com>.
Yes, it should be able to do that once the persistency is fully implemented.
However the maximum time that the client should keep trying depends on the
"Inactivity Time out" value used.
-Jaliya
----- Original Message -----
From: "Dennis Sosnoski" <dm...@sosnoski.com>
To: <sa...@ws.apache.org>
Sent: Thursday, October 12, 2006 4:41 PM
Subject: Operation when server is down
> 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: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: Operation when server is down
Posted by Chamikara Jayalath <ch...@gmail.com>.
Hi Dennis,
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 <dm...@sosnoski.com> 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: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>
>
Re: Operation when server is down
Posted by Chamikara Jayalath <ch...@gmail.com>.
Hi Dennis,
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 <dm...@sosnoski.com> 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: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>
>
Re: Operation when server is down
Posted by Jaliya Ekanayake <jn...@gmail.com>.
Yes, it should be able to do that once the persistency is fully implemented.
However the maximum time that the client should keep trying depends on the
"Inactivity Time out" value used.
-Jaliya
----- Original Message -----
From: "Dennis Sosnoski" <dm...@sosnoski.com>
To: <sa...@ws.apache.org>
Sent: Thursday, October 12, 2006 4:41 PM
Subject: Operation when server is down
> 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: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org