[
http://jira.magnolia-cms.com/browse/MAGNOLIA-3333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Haderka reopened MAGNOLIA-3333:
-----------------------------------
Can you add junit or integration test that would reexecute scenario described
by Philipp and ensure that it is really solved by the patch?
Thx.
> LockTimeoutException
> --------------------
>
> Key: MAGNOLIA-3333
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3333
> Project: Magnolia
> Issue Type: Bug
> Components: cache
> Reporter: Grégory Joseph
> Assignee: Ondřej Chytil
> Priority: Major
> Fix For: 4.3.x, 4.4.2, 5.0
>
> Attachments: MAGNOLIA-3333-exception.txt, magnolia-module-cache.patch
>
>
> 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)
--
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]>
----------------------------------------------------------------
