Hi All!
I put in the web.xml and made all session
data serializable. Application deployed successfuly but when
when request jumping from one node to another looks like all
data stored in session is lost, i c only default values.
server.xml:
I really dont und
Hi All!
I put in the web.xml and made all session
data serializable. Application deployed successfuly but when
when request jumping from one node to another looks like all
data stored in session is lost, i c only default values.
server.xml:
I really dont und
Hi All!
I put in the web.xml and made all session
data serializable. Application deployed successfuly but when
when request jumping from one node to another looks like all
data stored in session is lost, i c only default values.
server.xml:
I really dont und
On Fri, Oct 15, 2010 at 12:34:10PM +0200, Ronald Klop wrote:
> Op vrijdag, 15 oktober 2010 10:02 schreef Roman Makurin :
> >
> >
> >Hi All!
> >
> >I have an app which rely on session locking and its key
> >point here. Everything work on single tomcat i
Hi All!
I have an app which rely on session locking and its key
point here. Everything work on single tomcat instance,
but its completly broken in distributed env. So i want to
know is there any way to get my app working without
complete redesing? I need lock all incoming requests
untill business
Hi! Thanks for reply!
On Mon, Sep 20, 2010 at 11:30:52AM -0400, Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Roman,
>
> On 9/20/2010 3:27 AM, Roman Makurin wrote:
> > We have clustering setup with 2 tomcat 5.5 instances,
>
> Wh
Hi all!
We have clustering setup with 2 tomcat 5.5 instances,
and in some cases(eg when clients browser
disable cookies support) behaviour of request.getSession() is
really strange. According to api documentation this
call should always return session object but
it return null.
All URLs r encode
