|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 147 | minor | always | 05-06-05 00:00 | 11-30-05 14:44 | |
|
|
|||||
| Reporter: | user142 | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 3.0.13 | ||
| Product Build: | 3.0.13 | Resolution: | fixed | ||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.0.14 | ||
|
|
|||||
| Summary: | 0000147: Named log going to path="stdout:" gets redirected by <stdout-log> | ||||
| Description: |
RSN-141 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: <host host-name="hogwarts.com"> <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> <stdout-log path="c:/hogwarts/stdout.log"/> <resin:log name="com.hogwarts.resin.boot">...Now you don't!</resin:log> </host> 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. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | Windows XP | ||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||