not the problem - this is on an intranet - no proxy. all our pages carry that header
as well. This bug is documented and reproduced by Macromedia:
Jrun Bug 24049 – It is possible to get a duplicate session id during multi-user use
of Jrun if the user browses to a Jrun Web application root directory without using a
trailing slash.
"Haseltine, Celeste" <[EMAIL PROTECTED]> wrote: Will,
Good point. All of our web pages carry the header below. Perhaps that is
why we have not experienced this problem.
response.setHeader("Pragma","no-cache"); //HTTP 1.0 refetch completely next
time document is
needed.
response.setHeader("Cache-Control","no-cache"); //HTTP 1.1
response.setDateHeader ("Expires", 0); //prevents caching at the proxy
server, refetches ONLY if it
has been modified since last fetch
response.setHeader("Cache-Control","no-store"); //HTTP 1.1
Celeste
-----Original Message-----
From: Will Berger [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 27, 2002 10:38 AM
To: JRun-Talk
Subject: RE: Difficult To Reproduce Session Issue
I am coming late to this thread, but I thought I would give you my 2 cents.
We ran into this problem sometime ago where it appeared to be a jrun bug
that caused sessions to get mixed up, turned out to be that the new client
that we signed up had a proxy caching server and our jsp were being cached.
Adding the
response.addHeader("Pragma", "No-cache");
response.addHeader("Cache-Control", "no-cache");
response.addDateHeader("Expires", 1);
This resolved the issue.
Will
-----Original Message-----
From: Mike Collins [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 27, 2002 11:01 AM
To: JRun-Talk
Subject: Re: Difficult To Reproduce Session Issue
Some ideas on troubleshooting this issue:
I can think of 3 reasons why someone can get the wrong session data:
1. your jsessionid cookie somehow gets reset during the session to another
valid session
2. when your session is initialized you step on someone else's httpsession
object
3. requests with an incoming jsessionid gets bound to the wrong httpsession
object
Some ideas on troubleshooting the above scenarios:
- upon the creation of a new session, record the jsessionid in the
httpsession object.
- if a value already exists you know that you have just hit #2
- on all subsequent requests validate the jsessionid with the value on the
httpsession object. If they are not equal you know the problem is 1 or 3.
If you add these lines of code I would think you have a pretty good chance
at isolating and stopping folks from getting the wrong session. I would
also hope it might lead us to a resolution.
My gut tells me it is number 3, the others seem like they would have
revealed themselves by now.
Regards,
Mike
----- Original Message -----
From: "Jeff Ramin"
To: "JRun-Talk"
Sent: Wednesday, March 27, 2002 9:08 AM
Subject: Re: Difficult To Reproduce Session Issue
> Well, as long as we're commenting on the competition:
>
> My current lightweight app server of choice is Resin. I don't have
> much experience with it yet, but it seems solid. And fast. My first
> option used to be JRun, but given that this serious bug has gotten
> through Macromedia's quality assurance system 3 times, I have
> lost faith.
>
> As for WebSphere - I don't know about versions 3.5 or 4.0 (is 4.0
> out yet?), but I have a lot of experience with 3.0. My advice given
> that experience: RUN AWAY AS FAST AS YOU CAN.
>
>
> michael veit wrote:
> > We evaled both of those WebSphere and WebLogic - Websphere is much
harder to work with then is WebLogic. WebLogic is close to JRun in ease of
administration. But they both are very expensive, but "you get what u pay
for".
> > "Haseltine, Celeste" wrote: Michael,
> >
> > We haven't seen this problem, not yet anyway. But our servers are not
under
> > much of a load yet, as our site is just getting off the ground. We
expect
> > that to change over the next three to four months. If we do run into the
> > same problem, I suspect that will be the final straw for the owner of
this
> > facility, and he too will decide to go with another JSP/Servlet server.
The
> > only thing stopping him now is the much greater costs of either BEA
Weblogic
> > and IBM Websphere, which are the only two JSP/Servlet/EJB servers I
would
> > consider going to at this point in time. Of course, since I recommended
> > JRUN Server to the owner (mainly for the much lower costs and ease of
use
> > for a young group that was new to JSP/Servlet development and web
> > administration) it would probably mean my job. Oh well, such is life!!!
> >
> > If you do find a patch or get additional assistance from
Macromedia/Allaire,
> > please post it on this listserver. Good luck!!!
> >
> > Celeste
> >
>
>
>
> --
> Jeffrey Ramin
> Berbee
> 5520 Research Park Drive Madison, WI 53711
> [EMAIL PROTECTED]
> 608.298.1024
>
> Berbee...putting the E in business
>
>
______________________________________________________________________
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community. http://www.fusionauthority.com/ads.cfm
Archives: http://www.mail-archive.com/jrun-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
