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 Alex Horwitz <AH...@midwestiso.org> on 2006/04/10 18:43:33 UTC

RE: Sandesha in a Cluster

Sorry to come back to this after so long (was far away, unexectedly), but I would definitely be interested in whatever you developed Chathura, only for some basic scalability testing.  Would it be possible to shared this code?

Thanks for your help.

Alex

-----Original Message-----
From: Jaliya Ekanayake [mailto:jnekanayake@gmail.com]
Sent: Sunday, March 26, 2006 3:11 AM
To: Chathura Herath; Jaliya Ekanayake; sandesha-dev@ws.apache.org
Cc: Chamikara Jayalath
Subject: Re: Sandesha in a Cluster


That is great. Chamikara is working on Sandesha2's persistence layer and we 
have some issues with licenses
Can we use this under Apache? I mean IU has some licence for all the stuff. 
So if we can use this under apache then we can use it to implement the 
persistance queues.

Jaliya

----- Original Message ----- 
From: "Chathura Herath" <ch...@gmail.com>
To: "Jaliya Ekanayake" <ja...@apache.org>; <sa...@ws.apache.org>
Sent: Friday, March 24, 2006 11:52 PM
Subject: Re: Sandesha in a Cluster


Jaliya,
There is a persistant Queue implementation developped at IU, may be
you guys can use it if you are interested. I am not sure it meets your
requirements, i can show it to you offline, if you are interested . We
use it for messaging Queuing in the WS-Messenger broker.
 Don't think there will be any Licensing issue, lets not worry abt it for 
now.
Thanks
Chathura

On 3/24/06, Jaliya Ekanayake <jn...@gmail.com> wrote:
> Hi Alex,
>
> Yes, as you have mentioned to deploy Sandesha in a cluster it needs a
> persistance storage and we don't have it in Sandesha1. So if you can
> implement the SandeshaDatabaseDAO interface  then you can get the
> persistence behavior in Sandesha1.
>
> Sandesha2 already has a persistence layer and we have some issues in
> publishing it to the public domain due to some licensing issues and will 
> do
> it soon. In both cases we have Sender and Invoker's are stateless so will 
> be
> able to use them in a cluster.
>
> It will be really nice if you can give it a try and let us know.
>
> Thanks,
> Jaliya
>
> ----- Original Message -----
> From: "Alex Horwitz" <AH...@midwestiso.org>
> To: <sa...@ws.apache.org>
> Sent: Friday, March 24, 2006 9:01 AM
> Subject: Sandesha in a Cluster
>
>
> Hello all:
>
> Has anyone had experience deploying Axis/Sandesha in a Cluster?  After
> looking briefly at the server-side architecture, it almost appears that a
> single, persistent queue shared among all Sandesha web applications in a
> cluster might be a simple architecture that avoids the need for sticky
> sessions or session attributes, as the server components (sender, invoker)
> are event-driven and stateless.
>
> Any suggestions / advice on how to approach this problem would be greatly
> appreciated.
>
> Cheers,
>
> Alex
>
> ---------------------------------------------------------------------
> 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
>
>


--
Chathura Herath
http://people.apache.org/~chathura/
http://chathurah.blogspot.com/ 


---------------------------------------------------------------------
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