Even with higher timeout values we have this problem. It looks like that we get this problem as soon there's higher concurrency on the system ( > 30 concurrent user).
-----Original Message----- From: Wiegard, Hanno [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 23, 2002 11:18 AM To: 'Tomcat Users List' Subject: RE: Session.IsNew problems This should not happen, but I'll test this again with higher timeout values. The only thing that could happen is that a request takes longer than the timeout, e.g. we have a timeout of 10 sec., but the request processing takes about 20 sec. But I guess the timeout is calculated relative to the end of one request. -----Original Message----- From: Ralph Einfeldt [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 23, 2002 10:09 AM To: Tomcat Users List Subject: AW: Session.IsNew problems This should only happen if the session times out between two requests. Are you shure, that this did not happen ? > -----Ursprüngliche Nachricht----- > Von: Wiegard, Hanno [mailto:[EMAIL PROTECTED]] > Gesendet: Dienstag, 23. April 2002 09:48 > An: '[EMAIL PROTECTED]' > Betreff: Session.IsNew problems > > But it looks like that the request.getSession(true).isNew() > call sometimes return true even if the session is continued > (we see that the client sends his session cookie, but isNew() > returns true). -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
