Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of jasinthad@gmail.com designates
 209.85.219.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAP3k8oTbf-aNLKO-e2sP1CLhavoPSN31qhUrbjwXQDWrH68S1A@mail.gmail.com>
References: 
 <CAP3k8oTbf-aNLKO-e2sP1CLhavoPSN31qhUrbjwXQDWrH68S1A@mail.gmail.com>
Date: Mon, 5 Aug 2013 11:34:57 +0530
Message-ID: 
 <CAP3k8oRH1gRtyQq-TK_-_azCiOSxeQBHgL-qyh0kT0Nm49hBSA@mail.gmail.com>
Subject: Tomcat Channel Issue in EC2 clustering environment
From: Jasintha Dasanayaka <jasinthad@gmail.com>
To: users@tomcat.apache.org
Content-Type: multipart/alternative; boundary=089e013cbdc480464904e32d16cb

--089e013cbdc480464904e32d16cb
Content-Type: text/plain; charset=ISO-8859-1

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 ,

--089e013cbdc480464904e32d16cb--