Sounds like some sort of timeout or firewall blocking to me. If it works fine when both nodes are on a local network or subnet, but not when they are remote, something in-between is causing problems, or one or the other nodes is not set to wait long enough for delays caused by intervening networks or routers.
John > -----Original Message----- > From: Lior Shliechkorn [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 15, 2003 4:56 PM > To: Tomcat Users List > Subject: RE: IO Exception: Connection reset by peer: socket > write error > > > > 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 > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
