|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 3229 | minor | always | 01-08-09 16:42 | 03-01-10 12:50 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | urgent | OS Version: | |||
| Status: | closed | Product Version: | 3.0.25 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.6 | ||
|
|
|||||
| Summary: | 0003229: log file formatting | ||||
| Description: |
(rep by Jamison Novak) I'm struggling with some log formatting in Resin 3.0 and I'm hoping you can point me in the right direction. I've been unsuccessful in finding anything about this in documentation. We are currently logging Java exceptions (or stack traces/dumps, if you prefer) and, since they can be very long and typically multi-line, Resin puts a timestamp in front of each part of the exception even though it's all one big error. Is there any way to prevent that from happening and to only have a timestamp on the first part of it? For example: Bad: [01/08/09:08:16:25] java.lang.NullPointerException [01/08/09:08:16:25] at com.foo.agent.action.pkg.shared.booking.ServiceAssignmentAction.doBookingWork(Unknown Source) [01/08/09:08:16:25] at com.foo.agent.action.pkg.shared.booking.BookingAction.doPkgProcessWork(Unknown Source) [01/08/09:08:16:25] at com.foo.agent.action.pkg.PkgProcessAction.doPkgWork(Unknown Source) [ ... ] Good: [01/08/09:08:16:25] java.lang.NullPointerException at com.foo.agent.action.pkg.shared.booking.ServiceAssignmentAction.doBookingWork(Unknown Source) at com.foo.agent.action.pkg.shared.booking.BookingAction.doPkgProcessWork(Unknown Source) at com.foo.agent.action.pkg.PkgProcessAction.doPkgWork(Unknown Source) [...] We are attempting to import our Resin logs into a centralized log system and, because of that time stamping, it is interpreting each of those lines from a single exception as unrelated events. We are looking for a way to get it to be treated as a single log event. Any thoughts? I'm really at a loss. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||