|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 3084 | minor | always | 11-19-08 15:41 | 12-15-08 08:55 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 3.2.1 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.0 | ||
|
|
|||||
| Summary: | 0003084: log-service overlogging | ||||
| Description: |
(rep by Bryant Harris) Just wanted to touch base real quick... I found my servers were slowing to a crawl again, I traced it to some new code that was logging too frequently and the issue is resolved. So I don?t need any support on this, but I think you guys might have some issues with logging. I have not used JDK logging very much (more used to log4j) so I don?t know for sure if its possibly a JDK logging thing but it seems very strange that a server can run for 6-8 hours with no problems before falling behind in logging (frequent logging is continuous). This plus the fact that I didn?t see this with the free version... I think in an overlogging situation you?ve got something that consumes memory or something that over time slows down. At anyrate, just a data point for you guys. Very happy with my choice of Resin. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||