|Anonymous | Login | Signup for a new account||07-14-2020 09:28 PDT|
|Main | My View | View Issues | Change Log | Docs|
|Viewing Issue Simple Details [ Jump to Notes ]||[ View Advanced ] [ Issue History ] [ Print ]|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0000147||[Resin]||minor||always||05-06-05 00:00||11-30-05 14:44|
|Summary||0000147: Named log going to path="stdout:" gets redirected by <stdout-log>|
Debug output to the console (path="stdout:") in resin.conf via a named <log> and <resin:log> winds up getting redirected after a <stdout-log> entry. For example:
<log name="com.hogwarts.resin.boot" level="info" path="stdout:" timestamp="[%H:%M:%S.%s] "/>
<resin:log name="com.hogwarts.resin.boot">Now you see me...</resin:log>
<resin:log name="com.hogwarts.resin.boot">...Now you don't!</resin:log>
I would expect stdout-log only to apply to things written in code with System.out.println() and possibly un-named logs. I would expect the scenario described above to continue to go to the console. This is useful for monitoring the status of server startup if you have a lot of (or slow starting) webapps.
|Additional Information||Windows XP|
Currently, that behavior is the designed/intended behavior, i.e. we did think about that and chose that behavior.
On the other hand, the requested behavior might be more logical and useful.
Capture the System.out and System.err streams, but not stdout: or stderr: from Vfs.
|Can you clarify on what the fix is? Did you implement system-out/-err as desicribed by Sam or some other fix?|
|05-06-05 00:firstname.lastname@example.org||New Issue|
|11-30-05 00:00||administrator||Fixed in Version||=> 3.0.14|
|11-30-05 14:44||ferg||Status||resolved => closed|
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
33 total queries executed.|
31 unique queries executed.