[
https://issues.apache.org/jira/browse/JCS-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Narasimha Raju updated JCS-227:
-------------------------------
Description:
Incase any restart of the database lot log execptions are thrown, since we have
millions of get and puts happenning the logs are getting filled up.
The issue here is the put or get does not throw any exception which we could
catch and handle and controll logging.
If possible we should log on severe log level, logging should not print he
expcetion stacktrace and if would be better if just print how many times such
exception has occured instead of printing all. Printing all exceptions can be
done in finest.
Bcz of high cpu the log rollup is not happening.
was:
Incase any restart of the database lot log execptions are thrown, since we have
millions of get and puts happenning the logs are getting filled up.
The issue here is the put or get does not throw any exception which we could
catch and handle and controll logging.
If possible we should log on severe log level, logging should not print he
expcetion stacktrace and if would be better if just print how many times such
exception has occured instead of printing all. Printing all exceptions can be
done in finest
> With jdbc disk cache, when the database is down too many logs are printed
> causing the disk become full
> ------------------------------------------------------------------------------------------------------
>
> Key: JCS-227
> URL: https://issues.apache.org/jira/browse/JCS-227
> Project: Commons JCS
> Issue Type: Bug
> Components: JDBC Disk Cache
> Affects Versions: jcs-3.0, jcs-3.1
> Environment: Linux OS, jdk8,java util logging
> Reporter: Narasimha Raju
> Priority: Critical
> Labels: newbie
> Fix For: jcs-3.0, jcs-3.1
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Incase any restart of the database lot log execptions are thrown, since we
> have millions of get and puts happenning the logs are getting filled up.
> The issue here is the put or get does not throw any exception which we could
> catch and handle and controll logging.
> If possible we should log on severe log level, logging should not print he
> expcetion stacktrace and if would be better if just print how many times such
> exception has occured instead of printing all. Printing all exceptions can be
> done in finest.
> Bcz of high cpu the log rollup is not happening.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
