[
http://jira.magnolia-cms.com/browse/MAGNOLIA-3333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Bärfuss updated MAGNOLIA-3333:
--------------------------------------
Summary: cache: improve logging on blocking timeouts and unlock in the
cache filter on exceptions (was: LockTimeoutException)
Description:
After a longer discussion we have done the following:
- log when a requests takes longer to produce the content than the lock timeout
for the waiting threads are
- log when a request was blocked longer than the timeout period (because the
producer has not finished yet)
- introduced a blocking cache interface to expose the timeout configuration an
to wrap the unlock method
- it is now the cache filter which will unblock on exceptions (before it was
the store executor)
was:
I've noticed a lot of exceptions like the attached on our documentation
website. I have currently no idea why this happens. Restarting the instance
"solves" the issue.
There is a secondary issue to this: the exception appears both in the logs and
on screen. I believe this type of exception should never been rendered in the
client of a public instance (it shows some information that might be considered
sensitive). (perhaps a good generic solution to this problem would be a filter
intercepting all exceptions and rendering a default uninformative error page on
public instances)
I updated the title and description.
The original description was:
{quote}
I've noticed a lot of exceptions like the attached on our documentation
website. I have currently no idea why this happens. Restarting the instance
"solves" the issue.
There is a secondary issue to this: the exception appears both in the logs and
on screen. I believe this type of exception should never been rendered in the
client of a public instance (it shows some information that might be considered
sensitive). (perhaps a good generic solution to this problem would be a filter
intercepting all exceptions and rendering a default uninformative error page on
public instances)
{quote}
> cache: improve logging on blocking timeouts and unlock in the cache filter on
> exceptions
> -----------------------------------------------------------------------------------------
>
> Key: MAGNOLIA-3333
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3333
> Project: Magnolia
> Issue Type: Bug
> Components: cache
> Reporter: Grégory Joseph
> Assignee: Philipp Bärfuss
> Priority: Major
> Fix For: 4.4.2, 5.0
>
> Attachments: MAGNOLIA-3333-exception.txt, magnolia-module-cache.patch
>
>
> After a longer discussion we have done the following:
> - log when a requests takes longer to produce the content than the lock
> timeout for the waiting threads are
> - log when a request was blocked longer than the timeout period (because the
> producer has not finished yet)
> - introduced a blocking cache interface to expose the timeout configuration
> an to wrap the unlock method
> - it is now the cache filter which will unblock on exceptions (before it was
> the store executor)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
