Hi all, In what ways is the Tomcat session persistence useful to us? If it is not useful, can we get rid of that functionality? Then we can resolve issues like this.
Thanks, Senaka. On Wed, Jul 25, 2012 at 5:05 AM, Dushan Abeyruwan <[email protected]> wrote: > Hi Folks, > We have a scenario, which may have unstable ESB proxy service creation { > https://wso2.org/jira/browse/ESBJAVA-1341"} > How I observed this as follows, create a proxy wait for the session > timeout and then clicked "save proxy" and more interestingly the proxy > saved with NULL values, this was not observed with ESB 4.0.3 because if > session time out the direction happens to the cabon login UI thus > everything okay with that, but now due to the recent changers in the carbon > core as I heard tomcat session now is persistence thus even though the > session expired we can save BUT. the session does not include with the > proxy information > > any idea why this .. any workaround for this > > cheers > Dushan Abeyruwan > *Senior Software Engineer* > *Integration Technologies Team* > *WSO2 Inc. http://wso2.com/* > *Mobile:(+94)714408632* > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Senaka Fernando* Member - Integration Technologies Management Committee; Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
