| Anonymous | Login | Signup for a new account | 10-26-2025 05:52 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 | ||||
| Reporter | sam | View Status | public | ||||||
| Assigned To | |||||||||
| Priority | high | Resolution | fixed | Platform | |||||
| Status | closed | OS | |||||||
| Projection | none | OS Version | |||||||
| ETA | none | Fixed in Version | 3.0.14 | Product Version | 3.0.14 | ||||
| Product Build | 3.0.14 | ||||||||
| Summary | 0000250: stdout.log becomes jvm.log in latest snapshot | ||||||||
| Description |
RSN-273 (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 | |||||||||
| Additional Information | |||||||||
| Attached Files | |||||||||
|
|
|||||||||
Issue History |
|||
| Date Modified | Username | Field | Change |
| 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. |