DO NOT REPLY [Bug 31356] - Duplicate sessions counter not incremented in ManagerBase

gzilla/show_bug.cgi?id=31356 Duplicate sessions counter not incremented in ManagerBase [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 31356] - Duplicate sessions counter not incremented in ManagerBase

gzilla/show_bug.cgi?id=31356 Duplicate sessions counter not incremented in ManagerBase --- Additional Comments From [EMAIL PROTECTED] 2004-09-22 07:16 --- Created an attachment (id=12828) diff to fix problem - To unsubscr

DO NOT REPLY [Bug 31356] New: - Duplicate sessions counter not incremented in ManagerBase

gzilla/show_bug.cgi?id=31356 Duplicate sessions counter not incremented in ManagerBase Summary: Duplicate sessions counter not incremented in ManagerBase Product: Tomcat 5 Version: 5.5.1 Platform: Alpha OS/Version: Other

Re: Duplicate Sessions Tomcat 4.1.24

Andy Chapman wrote: Thanks Remy, I knew something as major as this would have surfaced and been fixed eons ago. However there is something here. After more brain-racking, a vital piece of the jigsaw has come to light. The app was updated at a suspiciously similar time to when the problem was report

RE: Duplicate Sessions Tomcat 4.1.24

ubject: Re: Duplicate Sessions Tomcat 4.1.24 Andy Chapman wrote: > I have a deployed web app with a medium size user base (~500) which > recently went live. The app relies on the session to retrieve user > information. The session usage is simply to store a couple of ids > (Strings) and

Re: Duplicate Sessions Tomcat 4.1.24

Andy Chapman wrote: I have a deployed web app with a medium size user base (~500) which recently went live. The app relies on the session to retrieve user information. The session usage is simply to store a couple of ids (Strings) and retrieve them from the session to lookup data. This all works p

Duplicate Sessions Tomcat 4.1.24

I have a deployed web app with a medium size user base (~500) which recently went live. The app relies on the session to retrieve user information. The session usage is simply to store a couple of ids (Strings) and retrieve them from the session to lookup data. This all works perfectly with a small

Re: Duplicate sessions

ate session ids > with Tomcat 4.x. > > Is there any patch available, or else is that > managed in later versions? > > Pl suggest h'w to avoid duplicate sessions > > Thanks & Regards > Srujana > > > > ---

Duplicate sessions

Hi We are facing problems with duplicate session ids with Tomcat 4.x. Is there any patch available, or else is that managed in later versions? Pl suggest h'w to avoid duplicate sessions Thanks & Regard