Hi Pubudu,
Also please test with GD enabled. We ran into issues in session replication
when GD was enabled in the following scenario.
Enable GD in node 1 and 2 - Start node1 - update session attributes by
sending requests to node 1 - start node 2 (make sure during this startup
the ghost webapp
Hi Azeez/Sameera and et al.
I'm currently undergoing development of $subject [1]
https://redmine.wso2.com/issues/3417
In the current implementation of embedded tomcat in appserver doesn't
supports Manager[2]
http://tomcat.apache.org/tomcat-7.0-doc/config/manager.html attributes
defines in
On Mon, Nov 17, 2014 at 8:53 AM, Pubudu Dissanayake pubu...@wso2.com
wrote:
CarbonTomcatSessionManager
What if you simply improve CarbonTomcatSessionManager to support
persistence as well, rather than writing a new class? If you want to turn
off persistence, you can have a parameter.
--
On Mon, Nov 17, 2014 at 10:06 AM, Afkham Azeez az...@wso2.com wrote:
On Mon, Nov 17, 2014 at 8:53 AM, Pubudu Dissanayake pubu...@wso2.com
wrote:
CarbonTomcatSessionManager
What if you simply improve CarbonTomcatSessionManager to support
persistence as well, rather than writing a new
So globally switching the SessionManager can be done by editing the global
context.xml file?
On Mon, Nov 17, 2014 at 11:41 AM, Pubudu Dissanayake pubu...@wso2.com
wrote:
On Mon, Nov 17, 2014 at 10:06 AM, Afkham Azeez az...@wso2.com wrote:
On Mon, Nov 17, 2014 at 8:53 AM, Pubudu Dissanayake
Ok, go ahead with your implementation.
On Mon, Nov 17, 2014 at 11:49 AM, Afkham Azeez az...@wso2.com wrote:
So globally switching the SessionManager can be done by editing the global
context.xml file?
On Mon, Nov 17, 2014 at 11:41 AM, Pubudu Dissanayake pubu...@wso2.com
wrote:
On Mon,
On Mon, Nov 17, 2014 at 11:52 AM, Afkham Azeez az...@wso2.com wrote:
Ok, go ahead with your implementation.
Noted
On Mon, Nov 17, 2014 at 11:49 AM, Afkham Azeez az...@wso2.com wrote:
So globally switching the SessionManager can be done by editing the
global context.xml file?
Indeed,
