You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "Ing. Diego Trombetta" <d....@mbm.it> on 2007/09/12 11:23:34 UTC
Tomcat lost requests/logs
I'm working with Tomcat 5.5.23.
The users are complaining that they need to log in a lot of
times during the day,
therefore I took a look at logs and, to my surprise, I found out
that there are missing requests!
What I mean is that on the logs I can read something like:
10-set-2007 10.18.44 INFO: [MyApp/MyServlet] "My Message"
(user)
10-set-2007 10.27.56 INFO: [MyApp/MyServlet] "My Message"
(user)
while the users performed 3 requests (e.g. at 10.18, at 10.21
and at 10.18)!!!!
And I'm sure he did because he updated DB tables and I can see
the "last update time" in those tables.
Therefore my servlet processed all the requests, but tomcat
somehow logged only two of them.
This behaviour on one hand makes me loose important logging
informations,
on the other hand make the session expire sooner than what they
should!!!
Any suggestions about it?
What can I do to monitor what's going on there?
R: Tomcat lost requests/logs
Posted by "Ing. Diego Trombetta" <d....@mbm.it>.
There is only one application server running.
The logs described are just an example: my logs are more datailed.
I print out also informations about the method, the parameters of the request and so on,
therefore I can discriminate which request has updated the DB. And I can be sure that
the server and the DB have the same timezone.
The session timeout is 20 minutes, but the session expires sooner than that.
The user performes 3 requests (e.g. at 10.18, at 10.27 and at 10.40) and
at the 3rd he needs to relogin!
-----Messaggio originale-----
Da: David Delbecq [mailto:delbd+jakarta@oma.be]
Inviato: mercoledì 12 settembre 2007 12.04
A: Tomcat Users List
Oggetto: Re: Tomcat lost requests/logs
Looks like you have configured round robin somewhere and another tomcat handled the 2 other requests.
Another possibility, regarding logs, is that timezone used to log (local server timezone) is not same as used by your database or as used by your client's desktop clock.
The session can expire for various reasons:
- timeout (see tomcat logs)
- invalid session id provided (if you have 2 tomcat server sharing load and they do not share session, this can happen)
- User cleared cookies or user disabled cookies and your application does not use url rewriting mecanisms
- Your application calls session.invalidate()
En l'instant précis du 12/09/07 11:23, Ing. Diego Trombetta s'exprimait en ces termes:
>
>
> I'm working with Tomcat 5.5.23.
> The users are complaining that they need to log in a lot of times
> during the day,
> therefore I took a look at logs and, to my surprise, I found out that
> there are missing requests!
> What I mean is that on the logs I can read something like:
>
> 10-set-2007 10.18.44 INFO: [MyApp/MyServlet] "My Message"
> (user)
>
> 10-set-2007 10.27.56 INFO: [MyApp/MyServlet] "My Message"
> (user)
>
> while the users performed 3 requests (e.g. at 10.18, at 10.21 and at
> 10.18)!!!!
> And I'm sure he did because he updated DB tables and I can see the
> "last update time" in those tables.
>
> Therefore my servlet processed all the requests, but tomcat somehow
> logged only two of them.
>
> This behaviour on one hand makes me loose important logging
> informations,
> on the other hand make the session expire sooner than what they
> should!!!
>
> Any suggestions about it?
> What can I do to monitor what's going on there?
>
>
>
--
http://www.noooxml.org/
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat lost requests/logs
Posted by David Delbecq <de...@oma.be>.
Looks like you have configured round robin somewhere and another tomcat
handled the 2 other requests.
Another possibility, regarding logs, is that timezone used to log (local
server timezone) is not same as used by your database or as used by your
client's desktop clock.
The session can expire for various reasons:
- timeout (see tomcat logs)
- invalid session id provided (if you have 2 tomcat server sharing load
and they do not share session, this can happen)
- User cleared cookies or user disabled cookies and your application
does not use url rewriting mecanisms
- Your application calls session.invalidate()
En l'instant précis du 12/09/07 11:23, Ing. Diego Trombetta s'exprimait
en ces termes:
>
>
> I'm working with Tomcat 5.5.23.
> The users are complaining that they need to log in a lot of
> times during the day,
> therefore I took a look at logs and, to my surprise, I found out
> that there are missing requests!
> What I mean is that on the logs I can read something like:
>
> 10-set-2007 10.18.44 INFO: [MyApp/MyServlet] "My Message"
> (user)
>
> 10-set-2007 10.27.56 INFO: [MyApp/MyServlet] "My Message"
> (user)
>
> while the users performed 3 requests (e.g. at 10.18, at 10.21
> and at 10.18)!!!!
> And I'm sure he did because he updated DB tables and I can see
> the "last update time" in those tables.
>
> Therefore my servlet processed all the requests, but tomcat
> somehow logged only two of them.
>
> This behaviour on one hand makes me loose important logging
> informations,
> on the other hand make the session expire sooner than what they
> should!!!
>
> Any suggestions about it?
> What can I do to monitor what's going on there?
>
>
>
--
http://www.noooxml.org/
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org