Wadi and unicast?
|
View:
New views
20 Messages
—
Rating Filter:
Alert me
|
 |
Wadi and unicast?
by Jason Warner
::
Rate this Message:
Hi all,
I tried poking around the documentation and google for an answer but came up dry. Does wadi support unicast? If so, how can I configure this? Thanks! -- ~Jason Warner |
|
|
Re: Wadi and unicast?
by Gianny Damour-2
::
Rate this Message:
Hello Jason,
WADI relies on Tribes for its inter-process communication. What you have done for the Geronimo native Tomcat clustering where cluster members are statically configured can also be done with WADI. If you have a look at the source code of TribesDispatcher, you can see that one of the constructors takes a collection of Members; this is a static list of cluster members: https://svn.codehaus.org/wadi/trunk/wadi/wadi-tribes/src/main/java/ org/codehaus/wadi/tribes/TribesDispatcher.java I also noticed that you have been able to switch off Tribes multicasting. Could you please explain me how this is done? Currently, you can configure a static list of cluster members however you cannot switch off multicasting. Thanks, Gianny On 19/07/2008, at 2:14 AM, Jason Warner wrote: > Hi all, > > I tried poking around the documentation and google for an answer > but came up dry. Does wadi support unicast? If so, how can I > configure this? > > Thanks! > > -- > ~Jason Warner --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Wadi and unicast?
by Filip Hanik - Dev Lists
::
Rate this Message:
Gianny Damour wrote:
> Hello Jason, > > WADI relies on Tribes for its inter-process communication. What you > have done for the Geronimo native Tomcat clustering where cluster > members are statically configured can also be done with WADI. > > If you have a look at the source code of TribesDispatcher, you can see > that one of the constructors takes a collection of Members; this is a > static list of cluster members: > https://svn.codehaus.org/wadi/trunk/wadi/wadi-tribes/src/main/java/org/codehaus/wadi/tribes/TribesDispatcher.java > > > I also noticed that you have been able to switch off Tribes > multicasting. Could you please explain me how this is done? Currently, > you can configure a static list of cluster members however you cannot > switch off multicasting. bit flag. If you only pass in the SND_TX and SND_RX flags, and not the MBR_TX and MBR_RX then you don't get multicasting Filip > > > Thanks, > Gianny > > On 19/07/2008, at 2:14 AM, Jason Warner wrote: > >> Hi all, >> >> I tried poking around the documentation and google for an answer but >> came up dry. Does wadi support unicast? If so, how can I configure >> this? >> >> Thanks! >> >> -- >> ~Jason Warner > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Wadi and unicast?
by Jason Warner
::
Rate this Message:
Thanks for the reply, Gianny. I'll give that a try.
Filip, I created a subclass for the purpose of disabling multicasting based on a response you made to a user post on the tomcat list. Is that still the best way to handle this? Are there plans to expose this functionality. Thanks! On Sun, Jul 20, 2008 at 2:47 PM, Filip Hanik - Dev Lists <devlists@...> wrote:
-- ~Jason Warner |
|
|
Re: Wadi and unicast?
by Gianny Damour-2
::
Rate this Message:
Hello Filip,
Thanks for the explanation. Based on my tests, static members are returned by Channel.getMembers () even if their are unavailable. Is there a way to alter the behaviour of Channel.getMembers() so that only live members are returned? Thanks, Gianny On 21/07/2008, at 4:47 AM, Filip Hanik - Dev Lists wrote: > Gianny Damour wrote: >> Hello Jason, >> >> WADI relies on Tribes for its inter-process communication. What >> you have done for the Geronimo native Tomcat clustering where >> cluster members are statically configured can also be done with WADI. >> >> If you have a look at the source code of TribesDispatcher, you can >> see that one of the constructors takes a collection of Members; >> this is a static list of cluster members: >> https://svn.codehaus.org/wadi/trunk/wadi/wadi-tribes/src/main/java/ >> org/codehaus/wadi/tribes/TribesDispatcher.java >> >> I also noticed that you have been able to switch off Tribes >> multicasting. Could you please explain me how this is done? >> Currently, you can configure a static list of cluster members >> however you cannot switch off multicasting. > yes, the Channel.java interface, start(int services) method takes a > int bit flag. If you only pass in the SND_TX and SND_RX flags, and > not the MBR_TX and MBR_RX then you don't get multicasting > > Filip >> >> >> Thanks, >> Gianny >> >> On 19/07/2008, at 2:14 AM, Jason Warner wrote: >> >>> Hi all, >>> >>> I tried poking around the documentation and google for an answer >>> but came up dry. Does wadi support unicast? If so, how can I >>> configure this? >>> >>> Thanks! >>> >>> -- >>> ~Jason Warner >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Wadi and unicast?
by Filip Hanik - Dev Lists
::
Rate this Message:
yes, you insert the TcpFailureDetector interceptor (use the
addInterceptor call) and that will validate all members using TCP. if you want discovery of static members, then add the TcpPingInterceptor before the TcpFailureDetector Filip Gianny Damour wrote: > Hello Filip, > > Thanks for the explanation. > > Based on my tests, static members are returned by Channel.getMembers() > even if their are unavailable. Is there a way to alter the behaviour > of Channel.getMembers() so that only live members are returned? > > Thanks, > Gianny > > On 21/07/2008, at 4:47 AM, Filip Hanik - Dev Lists wrote: > >> Gianny Damour wrote: >>> Hello Jason, >>> >>> WADI relies on Tribes for its inter-process communication. What you >>> have done for the Geronimo native Tomcat clustering where cluster >>> members are statically configured can also be done with WADI. >>> >>> If you have a look at the source code of TribesDispatcher, you can >>> see that one of the constructors takes a collection of Members; >>> this is a static list of cluster members: >>> https://svn.codehaus.org/wadi/trunk/wadi/wadi-tribes/src/main/java/org/codehaus/wadi/tribes/TribesDispatcher.java >>> >>> >>> I also noticed that you have been able to switch off Tribes >>> multicasting. Could you please explain me how this is done? >>> Currently, you can configure a static list of cluster members >>> however you cannot switch off multicasting. >> yes, the Channel.java interface, start(int services) method takes a >> int bit flag. If you only pass in the SND_TX and SND_RX flags, and >> not the MBR_TX and MBR_RX then you don't get multicasting >> >> Filip >>> >>> >>> Thanks, >>> Gianny >>> >>> On 19/07/2008, at 2:14 AM, Jason Warner wrote: >>> >>>> Hi all, >>>> >>>> I tried poking around the documentation and google for an answer >>>> but came up dry. Does wadi support unicast? If so, how can I >>>> configure this? >>>> >>>> Thanks! >>>> >>>> -- >>>> ~Jason Warner >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Wadi and unicast?
by Filip Hanik - Dev Lists
::
Rate this Message:
yes,the startup options have been added to trunk, and are proposed for a
backport into Tomcat 6.0.x Filip Jason Warner wrote: > Thanks for the reply, Gianny. I'll give that a try. > > Filip, I created a subclass for the purpose of disabling multicasting > based on a response you made to a user post on the tomcat list. Is > that still the best way to handle this? Are there plans to expose > this functionality. > > Thanks! > > On Sun, Jul 20, 2008 at 2:47 PM, Filip Hanik - Dev Lists > <devlists@... <mailto:devlists@...>> wrote: > > Gianny Damour wrote: > > Hello Jason, > > WADI relies on Tribes for its inter-process communication. > What you have done for the Geronimo native Tomcat clustering > where cluster members are statically configured can also be > done with WADI. > > If you have a look at the source code of TribesDispatcher, you > can see that one of the constructors takes a collection of > Members; this is a static list of cluster members: > https://svn.codehaus.org/wadi/trunk/wadi/wadi-tribes/src/main/java/org/codehaus/wadi/tribes/TribesDispatcher.java > > > I also noticed that you have been able to switch off Tribes > multicasting. Could you please explain me how this is done? > Currently, you can configure a static list of cluster members > however you cannot switch off multicasting. > > yes, the Channel.java interface, start(int services) method takes > a int bit flag. If you only pass in the SND_TX and SND_RX flags, > and not the MBR_TX and MBR_RX then you don't get multicasting > > Filip > > > > Thanks, > Gianny > > On 19/07/2008, at 2:14 AM, Jason Warner wrote: > > Hi all, > > I tried poking around the documentation and google for an > answer but came up dry. Does wadi support unicast? If > so, how can I configure this? > > Thanks! > > -- > ~Jason Warner > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > > -- > ~Jason Warner --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Wadi and unicast?
by Gianny Damour-2
::
Rate this Message:
This is working as expected :) I also had to move the
StaticMembershipInterceptor after the TcpFailureDetector to make it works (it is not possible to have this interceptor between the TcpFailure and the TcpPing interceptors). Jason, if you have a look to the latest TribesDispatcher you will see that I added a disableMulticasting constructor parameter. If you fancy writing the necessary Geronimo integration code to use static member with unicast only let me know and I will deploy a SNAPSHOT. Thanks, Gianny On 22/07/2008, at 1:15 AM, Filip Hanik - Dev Lists wrote: > yes, you insert the TcpFailureDetector interceptor (use the > addInterceptor call) and that will validate all members using TCP. > if you want discovery of static members, then add the > TcpPingInterceptor before the TcpFailureDetector > > Filip > > Gianny Damour wrote: >> Hello Filip, >> >> Thanks for the explanation. >> >> Based on my tests, static members are returned by >> Channel.getMembers() even if their are unavailable. Is there a way >> to alter the behaviour of Channel.getMembers() so that only live >> members are returned? >> >> Thanks, >> Gianny >> >> On 21/07/2008, at 4:47 AM, Filip Hanik - Dev Lists wrote: >> >>> Gianny Damour wrote: >>>> Hello Jason, >>>> >>>> WADI relies on Tribes for its inter-process communication. What >>>> you have done for the Geronimo native Tomcat clustering where >>>> cluster members are statically configured can also be done with >>>> WADI. >>>> >>>> If you have a look at the source code of TribesDispatcher, you >>>> can see that one of the constructors takes a collection of >>>> Members; this is a static list of cluster members: >>>> https://svn.codehaus.org/wadi/trunk/wadi/wadi-tribes/src/main/ >>>> java/org/codehaus/wadi/tribes/TribesDispatcher.java >>>> >>>> I also noticed that you have been able to switch off Tribes >>>> multicasting. Could you please explain me how this is done? >>>> Currently, you can configure a static list of cluster members >>>> however you cannot switch off multicasting. >>> yes, the Channel.java interface, start(int services) method takes >>> a int bit flag. If you only pass in the SND_TX and SND_RX flags, >>> and not the MBR_TX and MBR_RX then you don't get multicasting >>> >>> Filip >>>> >>>> >>>> Thanks, >>>> Gianny >>>> >>>> On 19/07/2008, at 2:14 AM, Jason Warner wrote: >>>> >>>>> Hi all, >>>>> >>>>> I tried poking around the documentation and google for an >>>>> answer but came up dry. Does wadi support unicast? If so, how >>>>> can I configure this? >>>>> >>>>> Thanks! >>>>> >>>>> -- >>>>> ~Jason Warner >>>> >>>> >>>> ------------------------------------------------------------------- >>>> -- >>>> To unsubscribe from this list, please visit: >>>> >>>> http://xircles.codehaus.org/manage_email >>>> >>>> >>>> >>> >>> >>> -------------------------------------------------------------------- >>> - >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> >> > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Wadi and unicast?
by Filip Hanik - Dev Lists
::
Rate this Message:
correct, the ordering of the interceptors is important to achieve what
you want. afterall, the logic is very simple, the static interceptor, just intercepts the getMembers() call, and adds the list of static to it, the tcp failure detector intercepts the call and after the static returned, it validates it. so the order should be, TcpPingInterceptor -> TcpFailureDetector -> StaticMembershipInterceptor Filip Gianny Damour wrote: > This is working as expected :) I also had to move the > StaticMembershipInterceptor after the TcpFailureDetector to make it > works (it is not possible to have this interceptor between the > TcpFailure and the TcpPing interceptors). > > Jason, if you have a look to the latest TribesDispatcher you will see > that I added a disableMulticasting constructor parameter. If you fancy > writing the necessary Geronimo integration code to use static member > with unicast only let me know and I will deploy a SNAPSHOT. > > Thanks, > Gianny > > On 22/07/2008, at 1:15 AM, Filip Hanik - Dev Lists wrote: > >> yes, you insert the TcpFailureDetector interceptor (use the >> addInterceptor call) and that will validate all members using TCP. >> if you want discovery of static members, then add the >> TcpPingInterceptor before the TcpFailureDetector >> >> Filip >> >> Gianny Damour wrote: >>> Hello Filip, >>> >>> Thanks for the explanation. >>> >>> Based on my tests, static members are returned by >>> Channel.getMembers() even if their are unavailable. Is there a way >>> to alter the behaviour of Channel.getMembers() so that only live >>> members are returned? >>> >>> Thanks, >>> Gianny >>> >>> On 21/07/2008, at 4:47 AM, Filip Hanik - Dev Lists wrote: >>> >>>> Gianny Damour wrote: >>>>> Hello Jason, >>>>> >>>>> WADI relies on Tribes for its inter-process communication. What >>>>> you have done for the Geronimo native Tomcat clustering where >>>>> cluster members are statically configured can also be done with WADI. >>>>> >>>>> If you have a look at the source code of TribesDispatcher, you can >>>>> see that one of the constructors takes a collection of Members; >>>>> this is a static list of cluster members: >>>>> https://svn.codehaus.org/wadi/trunk/wadi/wadi-tribes/src/main/java/org/codehaus/wadi/tribes/TribesDispatcher.java >>>>> >>>>> >>>>> I also noticed that you have been able to switch off Tribes >>>>> multicasting. Could you please explain me how this is done? >>>>> Currently, you can configure a static list of cluster members >>>>> however you cannot switch off multicasting. >>>> yes, the Channel.java interface, start(int services) method takes a >>>> int bit flag. If you only pass in the SND_TX and SND_RX flags, and >>>> not the MBR_TX and MBR_RX then you don't get multicasting >>>> >>>> Filip >>>>> >>>>> >>>>> Thanks, >>>>> Gianny >>>>> >>>>> On 19/07/2008, at 2:14 AM, Jason Warner wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> I tried poking around the documentation and google for an answer >>>>>> but came up dry. Does wadi support unicast? If so, how can I >>>>>> configure this? >>>>>> >>>>>> Thanks! >>>>>> >>>>>> -- >>>>>> ~Jason Warner >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe from this list, please visit: >>>>> >>>>> http://xircles.codehaus.org/manage_email >>>>> >>>>> >>>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe from this list, please visit: >>>> >>>> http://xircles.codehaus.org/manage_email >>>> >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Wadi and unicast?
by Jason Warner
::
Rate this Message:
Hi Gianny,
I'm currently working to expose static membership for a tomcat cluster configuration. As soon as I finish that, I'll be moving to do the same with wadi (if it's not implemented, I haven't looked at it yet). Thanks! On Thu, Jul 24, 2008 at 4:47 AM, Gianny Damour <gianny.damour@...> wrote: This is working as expected :) I also had to move the StaticMembershipInterceptor after the TcpFailureDetector to make it works (it is not possible to have this interceptor between the TcpFailure and the TcpPing interceptors). -- ~Jason Warner |
|
|
Re: Wadi and unicast?
by Filip Hanik - Dev Lists
::
Rate this Message:
hi Jason,
the static membership is exposed in the Tomcat configuration, you just use the <Interceptor> element Filip, Jason Warner wrote: > Hi Gianny, > > I'm currently working to expose static membership for a tomcat cluster > configuration. As soon as I finish that, I'll be moving to do the > same with wadi (if it's not implemented, I haven't looked at it yet). > > Thanks! > > On Thu, Jul 24, 2008 at 4:47 AM, Gianny Damour > <gianny.damour@... <mailto:gianny.damour@...>> > wrote: > > This is working as expected :) I also had to move the > StaticMembershipInterceptor after the TcpFailureDetector to make > it works (it is not possible to have this interceptor between the > TcpFailure and the TcpPing interceptors). > > Jason, if you have a look to the latest TribesDispatcher you will > see that I added a disableMulticasting constructor parameter. If > you fancy writing the necessary Geronimo integration code to use > static member with unicast only let me know and I will deploy a > SNAPSHOT. > > Thanks, > Gianny > > > On 22/07/2008, at 1:15 AM, Filip Hanik - Dev Lists wrote: > > yes, you insert the TcpFailureDetector interceptor (use the > addInterceptor call) and that will validate all members using TCP. > if you want discovery of static members, then add the > TcpPingInterceptor before the TcpFailureDetector > > Filip > > Gianny Damour wrote: > > Hello Filip, > > Thanks for the explanation. > > Based on my tests, static members are returned by > Channel.getMembers() even if their are unavailable. Is > there a way to alter the behaviour of Channel.getMembers() > so that only live members are returned? > > Thanks, > Gianny > > On 21/07/2008, at 4:47 AM, Filip Hanik - Dev Lists wrote: > > Gianny Damour wrote: > > Hello Jason, > > WADI relies on Tribes for its inter-process > communication. What you have done for the Geronimo > native Tomcat clustering where cluster members are > statically configured can also be done with WADI. > > If you have a look at the source code of > TribesDispatcher, you can see that one of the > constructors takes a collection of Members; this > is a static list of cluster members: > https://svn.codehaus.org/wadi/trunk/wadi/wadi-tribes/src/main/java/org/codehaus/wadi/tribes/TribesDispatcher.java > > I also noticed that you have been able to switch > off Tribes multicasting. Could you please explain > me how this is done? Currently, you can configure > a static list of cluster members however you > cannot switch off multicasting. > > yes, the Channel.java interface, start(int services) > method takes a int bit flag. If you only pass in the > SND_TX and SND_RX flags, and not the MBR_TX and MBR_RX > then you don't get multicasting > > Filip > > > > Thanks, > Gianny > > On 19/07/2008, at 2:14 AM, Jason Warner wrote: > > Hi all, > > I tried poking around the documentation and > google for an answer but came up dry. Does > wadi support unicast? If so, how can I > configure this? > > Thanks! > > -- > ~Jason Warner > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > > -- > ~Jason Warner --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Wadi and unicast?
by Jason Warner
::
Rate this Message:
Filip,
The interceptor portion is already in place, but there is currently no way to define a static member. The interceptor gbean needs to be modified to be able to handle static members. At least, that's the understanding I have of how static configuration works. Please let me know if I am way off base. Thanks! On Mon, Jul 28, 2008 at 4:35 PM, Filip Hanik - Dev Lists <devlists@...> wrote: hi Jason, -- ~Jason Warner |
|
|
Re: Wadi and unicast?
by Filip Hanik - Dev Lists
::
Rate this Message:
aah, you're talking Geronimo, not Tomcat :)
got it Filip Jason Warner wrote: > Filip, > > The interceptor portion is already in place, but there is currently no > way to define a static member. The interceptor gbean needs to be > modified to be able to handle static members. At least, that's the > understanding I have of how static configuration works. Please let me > know if I am way off base. > > Thanks! > > On Mon, Jul 28, 2008 at 4:35 PM, Filip Hanik - Dev Lists > <devlists@... <mailto:devlists@...>> wrote: > > hi Jason, > the static membership is exposed in the Tomcat configuration, you > just use the <Interceptor> element > > Filip, > > Jason Warner wrote: > > Hi Gianny, > > I'm currently working to expose static membership for a tomcat > cluster configuration. As soon as I finish that, I'll be > moving to do the same with wadi (if it's not implemented, I > haven't looked at it yet). > Thanks! > > On Thu, Jul 24, 2008 at 4:47 AM, Gianny Damour > <gianny.damour@... > <mailto:gianny.damour@...> > <mailto:gianny.damour@... > <mailto:gianny.damour@...>>> wrote: > > This is working as expected :) I also had to move the > StaticMembershipInterceptor after the TcpFailureDetector to > make > it works (it is not possible to have this interceptor > between the > TcpFailure and the TcpPing interceptors). > > Jason, if you have a look to the latest TribesDispatcher > you will > see that I added a disableMulticasting constructor > parameter. If > you fancy writing the necessary Geronimo integration code > to use > static member with unicast only let me know and I will deploy a > SNAPSHOT. > > Thanks, > Gianny > > > On 22/07/2008, at 1:15 AM, Filip Hanik - Dev Lists wrote: > > yes, you insert the TcpFailureDetector interceptor (use the > addInterceptor call) and that will validate all members > using TCP. > if you want discovery of static members, then add the > TcpPingInterceptor before the TcpFailureDetector > > Filip > > Gianny Damour wrote: > > Hello Filip, > > Thanks for the explanation. > > Based on my tests, static members are returned by > Channel.getMembers() even if their are unavailable. Is > there a way to alter the behaviour of > Channel.getMembers() > so that only live members are returned? > > Thanks, > Gianny > > On 21/07/2008, at 4:47 AM, Filip Hanik - Dev Lists > wrote: > > Gianny Damour wrote: > > Hello Jason, > > WADI relies on Tribes for its inter-process > communication. What you have done for the > Geronimo > native Tomcat clustering where cluster > members are > statically configured can also be done with > WADI. > > If you have a look at the source code of > TribesDispatcher, you can see that one of the > constructors takes a collection of Members; > this > is a static list of cluster members: > > https://svn.codehaus.org/wadi/trunk/wadi/wadi-tribes/src/main/java/org/codehaus/wadi/tribes/TribesDispatcher.java > > I also noticed that you have been able to > switch > off Tribes multicasting. Could you please > explain > me how this is done? Currently, you can > configure > a static list of cluster members however you > cannot switch off multicasting. > > yes, the Channel.java interface, start(int > services) > method takes a int bit flag. If you only pass > in the > SND_TX and SND_RX flags, and not the MBR_TX and > MBR_RX > then you don't get multicasting > > Filip > > > > Thanks, > Gianny > > On 19/07/2008, at 2:14 AM, Jason Warner wrote: > > Hi all, > > I tried poking around the documentation and > google for an answer but came up dry. Does > wadi support unicast? If so, how can I > configure this? > > Thanks! > > -- ~Jason Warner > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > > -- > ~Jason Warner > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > > -- > ~Jason Warner --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Wadi and unicast?
by Jason Warner
::
Rate this Message:
Hi Gianny,
I've finished up pretty much all my tomcat stuff and I've turned my attention to wadi. Have you given anymore thought to pushing out a snapshot that includes the new TrbeDispacther constructor? Thanks! Jason On Thu, Jul 24, 2008 at 4:47 AM, Gianny Damour <gianny.damour@...> wrote: This is working as expected :) I also had to move the StaticMembershipInterceptor after the TcpFailureDetector to make it works (it is not possible to have this interceptor between the TcpFailure and the TcpPing interceptors). -- ~Jason Warner |
|
|
Re: Wadi and unicast?
by Gianny Damour-2
::
Rate this Message:
Hello Jason,
I have just pushed brand new snapshots with the new TrbesDispacther constructor. Let me know if you have any integration issues! Thanks, Gianny --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Wadi and unicast?
by Jason Warner
::
Rate this Message:
Some parts of this message have been removed.
Learn more about Nabble's security policy.
Is there a way to specify the port that a wadi instance will use? It seems that the port is dynamically chosen starting at 4000. IT makes it a little difficult when defining more than one static implementation on a machine. Thanks! On 8/14/08, Gianny Damour <gianny.damour@...> wrote: Hello Jason, -- ~Jason Warner |
|
|
Re: Wadi and unicast?
by Gianny Damour-2
::
Rate this Message:
Hello Jason,
I have just deployed a new wadi-tribes snapshot which allows the configuration of the port you are talking about and of the Tribes multicasting properties. Here is the updated constructor: public TribesDispatcher(String clusterName, String localPeerName, EndPoint endPoint, Collection<StaticMember> staticMembers, boolean disableMulticasting, Properties mcastServiceProperties, int receiverPort) { Thanks, Gianny On 23/08/2008, at 5:20 AM, Jason Warner wrote: > Hi Gianny, > > Is there a way to specify the port that a wadi instance will use? > It seems that the port is dynamically chosen starting at 4000. IT > makes it a little difficult when defining more than one static > implementation on a machine. > > Thanks! > > On 8/14/08, Gianny Damour <gianny.damour@...> wrote: > Hello Jason, > > I have just pushed brand new snapshots with the new TrbesDispacther > constructor. > > Let me know if you have any integration issues! > > Thanks, > Gianny > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > > -- > ~Jason Warner --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Wadi and unicast?
by Jason Warner
::
Rate this Message:
Some parts of this message have been removed.
Learn more about Nabble's security policy.
On 8/23/08, Gianny Damour <gianny.damour@...> wrote: Hello Jason, -- ~Jason Warner |
|
|
Re: Wadi and unicast?
by Gianny Damour-2
::
Rate this Message:
Hi Jason,
WADI does not make use of UniqueId. Tribes may be using it internally. Based on the look of MemberImpl.equals(), I think that even if you have configured the same UniqueId for all your servers, the servers will actually be distinct as host and port are distinct. Thanks, Gianny On 26/08/2008, at 7:48 AM, Jason Warner wrote: > Thanks Gianny! Another quick question, does wadi make use of the > UniqueId attribute of the static member? I accidentally configured > my servers incorrectly with respect to the UniqueId attribute, but > it didn't really seem to affect anything. > > On 8/23/08, Gianny Damour <gianny.damour@...> wrote: > Hello Jason, > > I have just deployed a new wadi-tribes snapshot which allows the > configuration of the port you are talking about and of the Tribes > multicasting properties. Here is the updated constructor: > > public TribesDispatcher(String clusterName, > String localPeerName, > EndPoint endPoint, > Collection<StaticMember> staticMembers, > boolean disableMulticasting, > Properties mcastServiceProperties, > int receiverPort) { > > Thanks, > Gianny > > > On 23/08/2008, at 5:20 AM, Jason Warner wrote: > > Hi Gianny, > > Is there a way to specify the port that a wadi instance will use? > It seems that the port is dynamically chosen starting at 4000. IT > makes it a little difficult when defining more than one static > implementation on a machine. > > Thanks! > > On 8/14/08, Gianny Damour <gianny.damour@...> wrote: > Hello Jason, > > I have just pushed brand new snapshots with the new TrbesDispacther > constructor. > > Let me know if you have any integration issues! > > Thanks, > Gianny > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > > -- > ~Jason Warner > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > > -- > ~Jason Warner --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Wadi and unicast?
by Filip Hanik - Dev Lists
::
Rate this Message:
correct, the UniqueId is provided for detection of the "split brain
problem", for dynamic members, it allows the system to know if the process was restarted/crashed or if it just got disconnected from the cluster. Filip Gianny Damour wrote: > Hi Jason, > > WADI does not make use of UniqueId. Tribes may be using it internally. > Based on the look of MemberImpl.equals(), I think that even if you > have configured the same UniqueId for all your servers, the servers > will actually be distinct as host and port are distinct. > > Thanks, > Gianny > > On 26/08/2008, at 7:48 AM, Jason Warner wrote: > >> Thanks Gianny! Another quick question, does wadi make use of the >> UniqueId attribute of the static member? I accidentally configured >> my servers incorrectly with respect to the UniqueId attribute, but it >> didn't really seem to affect anything. >> >> On 8/23/08, Gianny Damour <gianny.damour@...> wrote: >> Hello Jason, >> >> I have just deployed a new wadi-tribes snapshot which allows the >> configuration of the port you are talking about and of the Tribes >> multicasting properties. Here is the updated constructor: >> >> public TribesDispatcher(String clusterName, >> String localPeerName, >> EndPoint endPoint, >> Collection<StaticMember> staticMembers, >> boolean disableMulticasting, >> Properties mcastServiceProperties, >> int receiverPort) { >> >> Thanks, >> Gianny >> >> >> On 23/08/2008, at 5:20 AM, Jason Warner wrote: >> >> Hi Gianny, >> >> Is there a way to specify the port that a wadi instance will use? It >> seems that the port is dynamically chosen starting at 4000. IT makes >> it a little difficult when defining more than one static >> implementation on a machine. >> >> Thanks! >> >> On 8/14/08, Gianny Damour <gianny.damour@...> wrote: >> Hello Jason, >> >> I have just pushed brand new snapshots with the new TrbesDispacther >> constructor. >> >> Let me know if you have any integration issues! >> >> Thanks, >> Gianny >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> >> >> >> -- >> ~Jason Warner >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> >> >> >> -- >> ~Jason Warner > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
| Free embeddable forum powered by Nabble | Forum Help |
