|Anonymous | Login | Signup for a new account||11-30-2021 22:31 PST|
|Main | My View | View Issues | Change Log | Docs|
|Viewing Issue Advanced Details [ Jump to Notes ]||[ View Simple ] [ Issue History ] [ Print ]|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0000107||[Resin]||minor||always||04-16-05 00:00||11-30-05 14:43|
|ETA||none||Fixed in Version||3.0.14||Product Version||3.0.13|
|Summary||0000107: Log write interleaving|
Under load Resin's logging subsystem will interleave log writes. Here are snippets taken from the access log of a box serving 45Mb/s of content.
[29/Mar/2005:07:00:02 -188.8.131.52 - - [29/Mar/2005:07:00:02 -0500] .....
[01/Apr/2005:00:00:02 -05184.108.40.206 - - [01/Apr/2005:00:00:02 -0500] .....
As you can see Resin has completely botched the log entries. This problem is not limited to the access log. Any type of logging that includes heavy multiple simultaneous writes to the logging subsystem results in the log write being botched. I suspect the issue is related to thread safety and I'm not sure if it's Resin that is screwing up or if it's the JRE's logging subsystem that is the root cause.
This bug is extremely unfortunate because 1) it makes it impossible for our web log analyzer to get accurate numbers about site traffic and usage and 2) in another application, we are having a hell of a time using logging as a means of aiding debugging.
|Steps To Reproduce|
Gentoo Linux 220.127.116.11
The debug (non-access) logging was fixed in 3.0.13.
The access logging is still open.
|04-16-05 00:00||studdugie||New Issue|
|11-30-05 00:00||administrator||Fixed in Version||=> 3.0.14|
|11-30-05 14:43||ferg||Status||resolved => closed|
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed.|
27 unique queries executed.