|Anonymous | Login | Signup for a new account||04-21-2021 09:42 PDT|
|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|
|0000250||[Resin]||minor||always||06-09-05 00:00||11-30-05 14:43|
|ETA||none||Fixed in Version||3.0.14||Product Version||3.0.14|
|Summary||0000250: stdout.log becomes jvm.log in latest snapshot|
(rep by K Fetterman)
In a recent snapshot, the output that use to be written to stdout.log is
now being written to jvm.log. This is a pain since because I have
written monitoring scripts to monitor stdout.log.
Is there a way to configure resin to write these
messages to stdout.log?
|Steps To Reproduce|
Before version 3.0.13, System.out.xxx and resin messages were written to stdout.log. Why in 3.0.13 did it change to jvm.log? Now in 3.0.13, when resin first starts up, it writes to stdout.log. Then at some point, it switches and starts writing to jvm.log.
This is confusing. Resin now writes to jvm.log, stdout.log and stderr.log. It would be helpful if the documentation was updated to explain what these files are used for and how the various resin.conf configuration parameters <stdout-log>, <stderr-log>, <log name="" path="stdout:" >, etc affect their use.
The current documentation doesn't make this clear.
There was no change in 3.0.13. 3.0.13 acts the same as 3.0.12.
There was a change in the snapshot which has been reversed.
The jvm.log has been around since early in 3.0.x.
|06-09-05 00:00||sam||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
31 total queries executed.|
29 unique queries executed.