
|
If you were logged in you would be able to see more operations.
|
|
|
|
OSCache 2.4.1
com.opensymphony.oscache.plugins.diskpersistence.AbstractDiskPersistenceListener
line 352-366
There are a few cases here in which Exceptions are just eaten up with no logging whatsoever. An exception should be logged somewhere in these cases.
This made it very difficult to determine why some of our application objects were not being cached to disk. The root cause was a non-serializable IOException, however OSCache was suppressing the error.
To replicate:
1. Configure a disk-based cache.
2. Create a non-serializable object.
3. Try and cache the object. It doesn't ever get cached. Nothing gets written to disk except for the directories the file would be written to.
|
|
Description
|
OSCache 2.4.1
com.opensymphony.oscache.plugins.diskpersistence.AbstractDiskPersistenceListener
line 352-366
There are a few cases here in which Exceptions are just eaten up with no logging whatsoever. An exception should be logged somewhere in these cases.
This made it very difficult to determine why some of our application objects were not being cached to disk. The root cause was a non-serializable IOException, however OSCache was suppressing the error.
To replicate:
1. Configure a disk-based cache.
2. Create a non-serializable object.
3. Try and cache the object. It doesn't ever get cached. Nothing gets written to disk except for the directories the file would be written to.
|
Show » |
|