Thanks for the insight. New implementation is based on the approach of
single Hazelcast cluster shared across all webapps and context param
(similar to /distributer tag) based approach to enable/disable session
replication.
On Tue, Oct 14, 2014 at 11:10 AM, Kishanthan Thangarajah
Hi Azeez/Srinath
I've managed to implement Tomcat Session replication using Hazelcast APIs.
As per the off-line chats with Azeez and Sameera,This functionality is
applicable to all web applications which are deploy in WSO2 AS. I've
introduced a global web filter, which is define in the web.xml
Is a Hazelcast cluster created per webapp, or is a single cluster shared
across all webapps? Why did you drop the idea of using a SessionListener
SessionManager?
On Mon, Oct 13, 2014 at 7:57 PM, Pubudu Dissanayake pubu...@wso2.com
wrote:
Hi Azeez/Srinath
I've managed to implement Tomcat
I haven't drop the idea of using HttpSessionManager but what i thought was
to evaluate how extent we can use this feature as a global web filter and
HttpSessionListener is already placed in the global filter. In the current
implementation Hazelcast creates a cluster per webapp, but I'm in progress
Hi Pubudu,
Just to be clear, this feature should work on per webapp basis. i.e not all
webapps' sessions should be replicated, but the selected ones by the user.
Earlier we used a webapp context property (distributable) to enable this at
webapp level.
Also here are the test cases that comes to
On Thu, Oct 2, 2014 at 9:22 AM, Srinath Perera srin...@wso2.com wrote:
I am not sure from notes what we decided.
Cannot we just used hazelcast session replication? does above design you
mentioned built on top of Hazelcast?
Yes, the plan is to use what Hazelcast provides. Otherwise, we will
Hi All,
Based on the Architecture review of Tomcat session replication using
caching , following aspects were discussed.
Participants
- Azeez, Sameera , Aruna, Jayanga, Gayashan, SupunM, Niranjan and
Myself
Proposed solution. - key-val: (CarbonSessionCacheKey, CarbonSessionCache)
-
I am not sure from notes what we decided.
Cannot we just used hazelcast session replication? does above design you
mentioned built on top of Hazelcast?
--Srinath
On Wed, Oct 1, 2014 at 2:18 PM, Pubudu Dissanayake pubu...@wso2.com wrote:
Hi All,
Based on the Architecture review of Tomcat
Hi All,
I am working on an improvement for Carbon to enable tomcat session
replication support using caching .Our previous implementation was based on
a Tomcat Valve ( CarbonTomcatSessionReplicationValve.java).And it was used to
replicate the session and adding it to cluster message.
Http
We need to use Hazelcast
When implemented we need to test this with multilple nodes (at least 4) and
in high load conditions before it is done done.
--Srinath
On Wed, Oct 1, 2014 at 8:52 AM, Dinesh J Weerakkody dine...@wso2.com
wrote:
Hi,
I came across this project [1] and might be useful.
Hi Srinath
Hazelcast WM allows us to cluster user http sessions automatically.
Followings are required for enabling Hazelcast Session Clustering
http://hazelcast.com/use-cases/web-session-clustering/ [2][3]
- Target application or web server should support Java 1.5+
- Target application or
11 matches
Mail list logo