Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 89210 invoked from network); 9 Jan 2003 21:18:00 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 9 Jan 2003 21:18:00 -0000 Received: (qmail 29543 invoked by uid 97); 9 Jan 2003 21:19:01 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 29526 invoked by uid 97); 9 Jan 2003 21:19:00 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 29513 invoked by uid 98); 9 Jan 2003 21:18:59 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.5.0 Beta Date: Thu, 09 Jan 2003 14:17:30 -0700 From: "Jeff Tulley" To: Subject: Re: One other freaky thing Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Also, there was a recent security issue with mod_jk that had symptoms like this. It would mean that somebody is purposely sending you a malformed packet, so it is not extremely likely. But, if you are using mod_jk, I'd update to the absolute latest released binaries to see if the problem doesn't happen again. Jeff Tulley (jtulley@novell.com) (801)861-5322 Novell, Inc., the leading provider of Net business solutions http://www.novell.com >>> mmolloy@ncycles.com 1/8/03 3:12:39 PM >>> Our application is running on a server in Pennsylvania. A user there was working as well as a user in Tennessee. The user in Tennessee got an error on a page, hit her back key, and the user in Pennsylvania's screen showed up on the Tennessee user's screen. The people in Tennessee are connected to the Pennsylvania system via a frame relay. Everything is contained within each user's session, so this should never happen. The application has been under development for a year now, and this has never happened before. Some kind of weird bug that we shouldn't worry about, or something that someone else has encountered? Thanks for any help, --Michael Molloy -- To unsubscribe, e-mail: For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: