Tomcat Channel Issue in EC2 clustering environment

[Jasintha Dasanayaka <ja...@gmail.com>]

Hi all

Axis2 Tribes utilizes Tomcat underneath. In Tomcat clustering, there's away
to add a listener to a channel, and get notifications based on different
scenarios such as member join, member leave etc. Axis2 tribes registers a
such listener in Tomcat, in order to identify whether a new member is
joined/left a Tomcat channel.

We are using EC2 based clustering environment, In this case,
intermittently, we've seen that the memberDisappear event of that
particular listener hasn't been triggered when a member leaves a tomcat
channel.

Any Idea ??


/Jasintha

-- 
*Thanks & Regards

Jasintha Dasanayake
*
*
*
*
*mobile +94 (0)71 624 1368 ,

Re: Tomcat Channel Issue in EC2 clustering environment

[Christopher Schultz <ch...@christopherschultz.net>]

Jasintha,

This is a question more appropriate for the users' list
(users@tomcat.apache.org). Consider re-posting there.

-chris

On 8/2/13 2:13 AM, Jasintha Dasanayaka wrote:
> Hi all
> 
> Axis2 Tribes utilizes Tomcat underneath. In Tomcat clustering, there's away
> to add a listener to a channel, and get notifications based on different
> scenarios such as member join, member leave etc. Axis2 tribes registers a
> such listener in Tomcat, in order to identify whether a new member is
> joined/left a Tomcat channel.
> 
> We are using EC2 based clustering environment, In this case,
> intermittently, we've seen that the memberDisappear event of that
> particular listener hasn't been triggered when a member leaves a tomcat
> channel.
> 
> Any Idea ??
> 
> 
> /Jasintha
> 

Tomcat Channel Issue in EC2 clustering environment

[Jasintha Dasanayaka <ja...@gmail.com>]

Hi all

Axis2 Tribes utilizes Tomcat underneath. In Tomcat clustering, there's away
to add a listener to a channel, and get notifications based on different
scenarios such as member join, member leave etc. Axis2 tribes registers a
such listener in Tomcat, in order to identify whether a new member is
joined/left a Tomcat channel.

We are using EC2 based clustering environment, In this case,
intermittently, we've seen that the member-disappear event of that
particular listener hasn't been triggered when a member leaves a tomcat
channel.

Any Idea ??


/Jasintha

-- 
*Thanks & Regards

Jasintha Dasanayake
*
*
*
*
*mobile +94 (0)71 624 1368 ,




-- 
*Thanks & Regards

Jasintha Dasanayake
*
*WSO2 Inc
*
*
*mobile +94 (0)71 624 1368 ,