Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 51220 invoked by uid 500); 5 Dec 2002 14:10:17 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 51128 invoked from network); 5 Dec 2002 14:10:16 -0000 From: "Carsten Ziegeler" To: Subject: RE: [SHOWSTOPPER?] Mixed sessions Date: Thu, 5 Dec 2002 15:09:58 +0100 Message-ID: MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <44201.10.0.0.1.1039086801.squirrel@_default_> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-MIMETrack: Itemize by SMTP Server on PBSN1/Systeme und Netzwerke(Release 5.0.8 |June 18, 2001) at 05.12.2002 15:10:09, Serialize by Router on PBSN1/Systeme und Netzwerke(Release 5.0.8 |June 18, 2001) at 05.12.2002 15:10:10, Serialize complete at 05.12.2002 15:10:10 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi Antonio, if you have more information please let us now. For example which environment do you use (JDK, Operating System, Servlet Engine). Thanks Carsten Carsten Ziegeler Open Source Group, S&N AG > -----Original Message----- > From: Antonio Gallardo [mailto:agallardo@agsoftware.dnsalias.com] > Sent: Thursday, December 05, 2002 12:13 PM > To: cocoon-dev@xml.apache.org > Subject: Re: [SHOWSTOPPER?] Mixed sessions > > > Hi, > > Sorry, but this is not a proxy error or a bad network configuration. We > turned off the proxy and the problem continues. Couriously before 25-Nov > everything was OK. But after that date the problems with mixed sessions > started. We are also checking all the network environment and everything > is OK. > > Yesterday morning I installed the lastest CVS of Cocoon 2.1 from 7:00 a.m. > CST. > > And because this problem take some time to start the mixing of sessions. I > will be sure later today if there were problems. I will ask users how was > yesterday and I promise I will put the feedback here. > > Please, next time ask more info (if you need) about a related problem. I > was sended many mails alerting about that but nobody response my mails. > Why ignore a site with 40 users? If I will have problems with few users I > will dont post nothing here and will resolve the problem locally. > > I think that the problem was related to the multithreading issue that > Carsten pointed 2 days ago. But I saw reactions until another user report > another diferent problem. > > I didnt sleep two days because of that problem. :-( > > By the way, I think we miss a docs about how to configure cocoon for a > production environment. Maybe some tips will be enough. I learned it in > the hard way. :-( > > As long as I know there is no info about that. I will post a doc about > that in wiki. I hope another people will help in this effort. > > Regards, > > Antonio Gallardo. > > > > Sylvain Wallez dijo: > > Carsten Ziegeler wrote: > > > >>Hi, > >> > >>we have several reports that under some cicumstances it > >>seems that sessions are mixed. It seems that under > >>heavy load a user A might get the session of user B. > >>Now generally I would call this a showstopper for > >>the 2.0.4 release. > >> > >>Unfortunately we don't have a reproducable test case > >>for this - does anyone have one? > >>Or are these problems not related to Cocoon but > >>to any third party components? > >> > >>I suggest that as long as the reason for this > >>problem is not found, we should delay the release. > >> > >>What do you think? > >> > >> > > > > I guess you're referring to the "[Authentication] - User with mixed > > Sessions" thread on cocoon-users, right ? > > > > This problem is IMO more related to proxy configuration than to Cocoon, > > at it seems that the proxy doesn't distinguish requests having different > > session cookies. > > > > So this should affect *every* servlet application and not Cocoon in > > particular, and therefore I wouldn't consider it as a showstopper. > > > > Nevertheless, we shouldn't ignore this problem, and see if we can use > > the cache information available in the pipeline to automatically set the > > "Cache-Control" header. But this can come in a future version. > > > > Sylvain > > > > -- > > Sylvain Wallez Anyware Technologies > > http://www.apache.org/~sylvain http://www.anyware-tech.com { > > XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } > > > > > > > > --------------------------------------------------------------------- To > > unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > > For additional commands, email: cocoon-dev-help@xml.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > For additional commands, email: cocoon-dev-help@xml.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org