Agreed on that one. However, back to the issue, this is not letting me log back in to the application. And, it's not throwing an exception in the filter that I have that gets/releases DB connections from a connection pool. When the application is run over in the same network as the DB there is no problem at all. Just when I run it from a different location it seems to act up in this manner. That's why I'm not quite sure. "Turner, John" <[EMAIL PROTECTED]> wrote: Never mind...I missed the part about the DB. *sigh* ...time for an after work beer.
John > -----Original Message----- > From: Turner, John [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 15, 2003 4:45 PM > To: 'Tomcat Users List' > Subject: RE: IO Exception: Connection reset by peer: socket > write error > > > > Agreed, though in my experience "connection reset by peer" > messages mean the > browser/client has stopped accepting data from the server, for various > reasons: timeouts, closing the browser window, etc. In most > situations, > they are harmless. > > John > > > -----Original Message----- > > From: Shapira, Yoav [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, January 15, 2003 4:41 PM > > To: Tomcat Users List > > Subject: RE: IO Exception: Connection reset by peer: socket > > write error > > > > > > Howdy, > > You're going to need to give us a lot more than that ;) What tomcat > > version, what connectors, full stack trace / log if possible, > > etc... ;) > > > > Yoav Shapira > > Millennium ChemInformatics > > > > -- To unsubscribe, e-mail: For additional commands, e-mail: --------------------------------- Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now
