[Dev] Session replication in jaggery apps

[Amila Maha Arachchi]

Hi,

Assume the scenario of two API Manager instances fronted with WSO2 ELB.
While user is logged in  and working in publisher or store app, all his
requests are going to the same node where the session is established.

At this moment if we kill one node, requests will start going to the other
node, but theres no session available in it.

My question is:
Is session replication valid for jaggery apps?

Regards,
AmilaM.

-- 
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com

Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Session replication in jaggery apps

[Ruchira Wageesha]

Hi Amila,

Since Jaggery is based on Tomcat, whatever the session replication
mechanism available for Java webapps, should be valid for Jaggery as
well[1]. But, I doubt whether it will work smoothly if there are any
non-serializable objects in the session.

/Ruchira

[1] https://tomcat.apache.org/tomcat-7.0-doc/cluster-howto.html


On Mon, Mar 17, 2014 at 4:59 PM, Amila Maha Arachchi wrote:

> Hi,
>
> Assume the scenario of two API Manager instances fronted with WSO2 ELB.
> While user is logged in  and working in publisher or store app, all his
> requests are going to the same node where the session is established.
>
> At this moment if we kill one node, requests will start going to the other
> node, but theres no session available in it.
>
> My question is:
> Is session replication valid for jaggery apps?
>
> Regards,
> AmilaM.
>
> --
> *Amila Maharachchi*
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
>
> Blog: http://maharachchi.blogspot.com
> Mobile: +94719371446
>
>


-- 

*Ruchira Wageesha**Associate Technical Lead*
*WSO2 Inc. - lean . enterprise . middleware |  wso2.com *

*email: ruch...@wso2.com ,   blog:
ruchirawageesha.blogspot.com ,
mobile: +94 77 5493444*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Session replication in jaggery apps

[Isuru Perera]

Hi,

So that means Jaggery uses HttpSession in Java Servlet API.

I hope following config also work with API Manager:
https://docs.wso2.org/display/AS521/Clustering+and+Http+Session+Replication

If the app is storing any non-serializable objects, then it's a problem
with app and we should fix it.

On Mon, Mar 17, 2014 at 7:20 PM, Ruchira Wageesha  wrote:

> Hi Amila,
>
> Since Jaggery is based on Tomcat, whatever the session replication
> mechanism available for Java webapps, should be valid for Jaggery as
> well[1]. But, I doubt whether it will work smoothly if there are any
> non-serializable objects in the session.
>
> /Ruchira
>
> [1] https://tomcat.apache.org/tomcat-7.0-doc/cluster-howto.html
>
>
> On Mon, Mar 17, 2014 at 4:59 PM, Amila Maha Arachchi wrote:
>
>> Hi,
>>
>> Assume the scenario of two API Manager instances fronted with WSO2 ELB.
>> While user is logged in  and working in publisher or store app, all his
>> requests are going to the same node where the session is established.
>>
>> At this moment if we kill one node, requests will start going to the
>> other node, but theres no session available in it.
>>
>> My question is:
>> Is session replication valid for jaggery apps?
>>
>> Regards,
>> AmilaM.
>>
>> --
>> *Amila Maharachchi*
>> Senior Technical Lead
>> WSO2, Inc.; http://wso2.com
>>
>> Blog: http://maharachchi.blogspot.com
>> Mobile: +94719371446
>>
>>
>
>
> --
>
> *Ruchira Wageesha**Associate Technical Lead*
> *WSO2 Inc. - lean . enterprise . middleware |  wso2.com *
>
> *email: ruch...@wso2.com ,   blog:
> ruchirawageesha.blogspot.com ,
> mobile: +94 77 5493444 <%2B94%2077%205493444>*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

about.me/chrishantha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Session replication in jaggery apps

[Kishanthan Thangarajah]

IIRC, the support for session replication for jaggery apps was added when
we implemented it for webapps. There were some changes needed from jaggery
deployment side (eg: reading jag.conf for "distributable" property) and it
was added. But the related jira is still in open state :
https://wso2.org/jira/browse/JAGGERY-275

@Dilshan, shouldn't this issue be in "fixed" state? Or is there anything
more to add?




On Mon, Mar 17, 2014 at 7:20 PM, Ruchira Wageesha  wrote:

> Hi Amila,
>
> Since Jaggery is based on Tomcat, whatever the session replication
> mechanism available for Java webapps, should be valid for Jaggery as
> well[1]. But, I doubt whether it will work smoothly if there are any
> non-serializable objects in the session.
>
> /Ruchira
>
> [1] https://tomcat.apache.org/tomcat-7.0-doc/cluster-howto.html
>
>
> On Mon, Mar 17, 2014 at 4:59 PM, Amila Maha Arachchi wrote:
>
>> Hi,
>>
>> Assume the scenario of two API Manager instances fronted with WSO2 ELB.
>> While user is logged in  and working in publisher or store app, all his
>> requests are going to the same node where the session is established.
>>
>> At this moment if we kill one node, requests will start going to the
>> other node, but theres no session available in it.
>>
>> My question is:
>> Is session replication valid for jaggery apps?
>>
>> Regards,
>> AmilaM.
>>
>> --
>> *Amila Maharachchi*
>> Senior Technical Lead
>> WSO2, Inc.; http://wso2.com
>>
>> Blog: http://maharachchi.blogspot.com
>> Mobile: +94719371446
>>
>>
>
>
> --
>
> *Ruchira Wageesha**Associate Technical Lead*
> *WSO2 Inc. - lean . enterprise . middleware |  wso2.com *
>
> *email: ruch...@wso2.com ,   blog:
> ruchirawageesha.blogspot.com ,
> mobile: +94 77 5493444 <%2B94%2077%205493444>*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Kishanthan Thangarajah*
Senior Software Engineer,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com *
Twitter - *http://twitter.com/kishanthan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Session replication in jaggery apps

[Dilshan Edirisuriya]

I have implemented this feature and tested it. You have to add
distributable property (true/false) in Jaggery conf file. Rest of the
configurations goes as [1]. Closed the JIRA.

{
"displayName":"My App",
"welcomeFiles":["index.jag"],
"distributable":true
}

[1] - http://tomcat.apache.org/tomcat-7.0-doc/cluster-howto.html





On Tue, Mar 18, 2014 at 10:24 AM, Kishanthan Thangarajah <
kishant...@wso2.com> wrote:

> IIRC, the support for session replication for jaggery apps was added when
> we implemented it for webapps. There were some changes needed from jaggery
> deployment side (eg: reading jag.conf for "distributable" property) and it
> was added. But the related jira is still in open state :
> https://wso2.org/jira/browse/JAGGERY-275
>
> @Dilshan, shouldn't this issue be in "fixed" state? Or is there anything
> more to add?
>
>
>
>
> On Mon, Mar 17, 2014 at 7:20 PM, Ruchira Wageesha wrote:
>
>> Hi Amila,
>>
>> Since Jaggery is based on Tomcat, whatever the session replication
>> mechanism available for Java webapps, should be valid for Jaggery as
>> well[1]. But, I doubt whether it will work smoothly if there are any
>> non-serializable objects in the session.
>>
>> /Ruchira
>>
>> [1] https://tomcat.apache.org/tomcat-7.0-doc/cluster-howto.html
>>
>>
>> On Mon, Mar 17, 2014 at 4:59 PM, Amila Maha Arachchi wrote:
>>
>>> Hi,
>>>
>>> Assume the scenario of two API Manager instances fronted with WSO2 ELB.
>>> While user is logged in  and working in publisher or store app, all his
>>> requests are going to the same node where the session is established.
>>>
>>> At this moment if we kill one node, requests will start going to the
>>> other node, but theres no session available in it.
>>>
>>> My question is:
>>> Is session replication valid for jaggery apps?
>>>
>>> Regards,
>>> AmilaM.
>>>
>>> --
>>> *Amila Maharachchi*
>>> Senior Technical Lead
>>> WSO2, Inc.; http://wso2.com
>>>
>>> Blog: http://maharachchi.blogspot.com
>>> Mobile: +94719371446
>>>
>>>
>>
>>
>> --
>>
>> *Ruchira Wageesha**Associate Technical Lead*
>> *WSO2 Inc. - lean . enterprise . middleware |  wso2.com *
>>
>> *email: ruch...@wso2.com ,   blog:
>> ruchirawageesha.blogspot.com ,
>> mobile: +94 77 5493444 <%2B94%2077%205493444>*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Kishanthan Thangarajah*
> Senior Software Engineer,
> Platform Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com *
> Twitter - *http://twitter.com/kishanthan *
>



-- 
Dilshan Edirisuriya
Senior Software Engineer - WSO2
Mob: + 94 777878905
http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Session replication in jaggery apps

[Amila Maha Arachchi]

Thanks. I'll follow the instructions and get back to you.


On Tue, Mar 18, 2014 at 11:04 AM, Dilshan Edirisuriya wrote:

> I have implemented this feature and tested it. You have to add
> distributable property (true/false) in Jaggery conf file. Rest of the
> configurations goes as [1]. Closed the JIRA.
>
> {
> "displayName":"My App",
> "welcomeFiles":["index.jag"],
> "distributable":true
> }
>
> [1] - http://tomcat.apache.org/tomcat-7.0-doc/cluster-howto.html
>
>
>
>
>
> On Tue, Mar 18, 2014 at 10:24 AM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> IIRC, the support for session replication for jaggery apps was added when
>> we implemented it for webapps. There were some changes needed from jaggery
>> deployment side (eg: reading jag.conf for "distributable" property) and it
>> was added. But the related jira is still in open state :
>> https://wso2.org/jira/browse/JAGGERY-275
>>
>> @Dilshan, shouldn't this issue be in "fixed" state? Or is there anything
>> more to add?
>>
>>
>>
>>
>> On Mon, Mar 17, 2014 at 7:20 PM, Ruchira Wageesha wrote:
>>
>>> Hi Amila,
>>>
>>> Since Jaggery is based on Tomcat, whatever the session replication
>>> mechanism available for Java webapps, should be valid for Jaggery as
>>> well[1]. But, I doubt whether it will work smoothly if there are any
>>> non-serializable objects in the session.
>>>
>>> /Ruchira
>>>
>>> [1] https://tomcat.apache.org/tomcat-7.0-doc/cluster-howto.html
>>>
>>>
>>> On Mon, Mar 17, 2014 at 4:59 PM, Amila Maha Arachchi wrote:
>>>
 Hi,

 Assume the scenario of two API Manager instances fronted with WSO2 ELB.
 While user is logged in  and working in publisher or store app, all his
 requests are going to the same node where the session is established.

 At this moment if we kill one node, requests will start going to the
 other node, but theres no session available in it.

 My question is:
 Is session replication valid for jaggery apps?

 Regards,
 AmilaM.

 --
 *Amila Maharachchi*
 Senior Technical Lead
 WSO2, Inc.; http://wso2.com

 Blog: http://maharachchi.blogspot.com
 Mobile: +94719371446


>>>
>>>
>>> --
>>>
>>> *Ruchira Wageesha**Associate Technical Lead*
>>> *WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>> *
>>>
>>> *email: ruch...@wso2.com ,   blog:
>>> ruchirawageesha.blogspot.com ,
>>> mobile: +94 77 5493444 <%2B94%2077%205493444>*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Kishanthan Thangarajah*
>> Senior Software Engineer,
>> Platform Technologies Team,
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - +94773426635
>> Blog - *http://kishanthan.wordpress.com
>> *
>> Twitter - *http://twitter.com/kishanthan *
>>
>
>
>
> --
> Dilshan Edirisuriya
> Senior Software Engineer - WSO2
> Mob: + 94 777878905
> http://wso2.com/
>



-- 
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com

Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Session replication in jaggery apps

[Kishanthan Thangarajah]

Great. Shall we also have this documented, if not already done?


On Tue, Mar 18, 2014 at 11:04 AM, Dilshan Edirisuriya wrote:

> I have implemented this feature and tested it. You have to add
> distributable property (true/false) in Jaggery conf file. Rest of the
> configurations goes as [1]. Closed the JIRA.
>
> {
> "displayName":"My App",
> "welcomeFiles":["index.jag"],
> "distributable":true
> }
>
> [1] - http://tomcat.apache.org/tomcat-7.0-doc/cluster-howto.html
>
>
>
>
>
> On Tue, Mar 18, 2014 at 10:24 AM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> IIRC, the support for session replication for jaggery apps was added when
>> we implemented it for webapps. There were some changes needed from jaggery
>> deployment side (eg: reading jag.conf for "distributable" property) and it
>> was added. But the related jira is still in open state :
>> https://wso2.org/jira/browse/JAGGERY-275
>>
>> @Dilshan, shouldn't this issue be in "fixed" state? Or is there anything
>> more to add?
>>
>>
>>
>>
>> On Mon, Mar 17, 2014 at 7:20 PM, Ruchira Wageesha wrote:
>>
>>> Hi Amila,
>>>
>>> Since Jaggery is based on Tomcat, whatever the session replication
>>> mechanism available for Java webapps, should be valid for Jaggery as
>>> well[1]. But, I doubt whether it will work smoothly if there are any
>>> non-serializable objects in the session.
>>>
>>> /Ruchira
>>>
>>> [1] https://tomcat.apache.org/tomcat-7.0-doc/cluster-howto.html
>>>
>>>
>>> On Mon, Mar 17, 2014 at 4:59 PM, Amila Maha Arachchi wrote:
>>>
 Hi,

 Assume the scenario of two API Manager instances fronted with WSO2 ELB.
 While user is logged in  and working in publisher or store app, all his
 requests are going to the same node where the session is established.

 At this moment if we kill one node, requests will start going to the
 other node, but theres no session available in it.

 My question is:
 Is session replication valid for jaggery apps?

 Regards,
 AmilaM.

 --
 *Amila Maharachchi*
 Senior Technical Lead
 WSO2, Inc.; http://wso2.com

 Blog: http://maharachchi.blogspot.com
 Mobile: +94719371446


>>>
>>>
>>> --
>>>
>>> *Ruchira Wageesha**Associate Technical Lead*
>>> *WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>> *
>>>
>>> *email: ruch...@wso2.com ,   blog:
>>> ruchirawageesha.blogspot.com ,
>>> mobile: +94 77 5493444 <%2B94%2077%205493444>*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Kishanthan Thangarajah*
>> Senior Software Engineer,
>> Platform Technologies Team,
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - +94773426635
>> Blog - *http://kishanthan.wordpress.com
>> *
>> Twitter - *http://twitter.com/kishanthan *
>>
>
>
>
> --
> Dilshan Edirisuriya
> Senior Software Engineer - WSO2
> Mob: + 94 777878905
> http://wso2.com/
>



-- 
*Kishanthan Thangarajah*
Senior Software Engineer,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com *
Twitter - *http://twitter.com/kishanthan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Session replication in jaggery apps

[Madhuka Udantha]

On Tue, Mar 18, 2014 at 11:16 AM, Kishanthan Thangarajah <
kishant...@wso2.com> wrote:

> Great. Shall we also have this documented, if not already done?
>
Yap, Since some features/functions/APIs lately added to jaggery and had
missed documentation.
We will sync docs and APIs soon. (Around in week)

>
>
> On Tue, Mar 18, 2014 at 11:04 AM, Dilshan Edirisuriya wrote:
>
>> I have implemented this feature and tested it. You have to add
>> distributable property (true/false) in Jaggery conf file. Rest of the
>> configurations goes as [1]. Closed the JIRA.
>>
>> {
>> "displayName":"My App",
>> "welcomeFiles":["index.jag"],
>> "distributable":true
>> }
>>
>> [1] - http://tomcat.apache.org/tomcat-7.0-doc/cluster-howto.html
>>
>>
>>
>>
>>
>> On Tue, Mar 18, 2014 at 10:24 AM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>> IIRC, the support for session replication for jaggery apps was added
>>> when we implemented it for webapps. There were some changes needed from
>>> jaggery deployment side (eg: reading jag.conf for "distributable" property)
>>> and it was added. But the related jira is still in open state :
>>> https://wso2.org/jira/browse/JAGGERY-275
>>>
>>> @Dilshan, shouldn't this issue be in "fixed" state? Or is there anything
>>> more to add?
>>>
>>>
>>>
>>>
>>> On Mon, Mar 17, 2014 at 7:20 PM, Ruchira Wageesha wrote:
>>>
 Hi Amila,

 Since Jaggery is based on Tomcat, whatever the session replication
 mechanism available for Java webapps, should be valid for Jaggery as
 well[1]. But, I doubt whether it will work smoothly if there are any
 non-serializable objects in the session.

 /Ruchira

 [1] https://tomcat.apache.org/tomcat-7.0-doc/cluster-howto.html


 On Mon, Mar 17, 2014 at 4:59 PM, Amila Maha Arachchi 
 wrote:

> Hi,
>
> Assume the scenario of two API Manager instances fronted with WSO2
> ELB. While user is logged in  and working in publisher or store app, all
> his requests are going to the same node where the session is established.
>
> At this moment if we kill one node, requests will start going to the
> other node, but theres no session available in it.
>
> My question is:
> Is session replication valid for jaggery apps?
>
> Regards,
> AmilaM.
>
> --
> *Amila Maharachchi*
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
>
> Blog: http://maharachchi.blogspot.com
> Mobile: +94719371446
>
>


 --

 *Ruchira Wageesha**Associate Technical Lead*
 *WSO2 Inc. - lean . enterprise . middleware |  wso2.com
 *

 *email: ruch...@wso2.com ,   blog:
 ruchirawageesha.blogspot.com ,
 mobile: +94 77 5493444 <%2B94%2077%205493444>*

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> *Kishanthan Thangarajah*
>>> Senior Software Engineer,
>>> Platform Technologies Team,
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>>
>>> Mobile - +94773426635
>>> Blog - *http://kishanthan.wordpress.com
>>> *
>>> Twitter - *http://twitter.com/kishanthan
>>> *
>>>
>>
>>
>>
>> --
>> Dilshan Edirisuriya
>> Senior Software Engineer - WSO2
>> Mob: + 94 777878905
>> http://wso2.com/
>>
>
>
>
> --
> *Kishanthan Thangarajah*
> Senior Software Engineer,
> Platform Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com *
> Twitter - *http://twitter.com/kishanthan *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com

*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev