[MGNLADVCACHE-19] Problem with cache Created: 03/Nov/11  Updated: 05/May/15  Resolved: 05/May/15

Status: Closed
Project: Advanced Cache
Component/s: None
Affects Version/s: 1.3
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Jose Ramon Rodriguez Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Red Hat 6, jdk 1.6


Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

02 nov 2011 17:09:59,392 ERROR http-8080-38 org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/].[default] - Servlet.service() para servlet default lanzó excepción
net.sf.ehcache.constructs.blocking.LockTimeoutException: Lock timeout. Waited more than 10000ms to acquire lock for key DefaultCacheKey{uri='/dms/product/custom/SUELOS-LAMINADOS/14506982/14506982_l', serverName='www.leroymerlin.es', locale='es', params={}} on blocking cache default



 Comments   
Comment by Gino Esposto [ 05/May/15 ]

I have the same problem here on our third public instance:

15-05-05 09:09:19 ERROR [ajp-nio-8010-exec-320]org.springframework.security.web.context.SecurityContextPersistenceFilter: Caught exception: Lock timeout. Waited more than 10000ms to acquire lock for key DefaultCacheKey{uri='/de/ueber-die-migros/werte/frische.html', serverName='www.migros.ch', locale='de', channel='desktop', params={}', secure='false', method='get'} on blocking cache default
net.sf.ehcache.constructs.blocking.LockTimeoutException: Lock timeout. Waited more than 10000ms to acquire lock for key DefaultCacheKey{uri='/de/ueber-die-migros/werte/frische.html', serverName='www.migros.ch', locale='de', channel='desktop', params={}', secure='false', method='get'} on blocking cache default
Does anybody know about the reason for such a caching timeout problem?

Comment by Evzen Fochr [ 05/May/15 ]

Dear Gino, for resolving this issue, please ask on forum.

Comment by Roman Kovařík [ 05/May/15 ]

Hi Gino,
basically what's happening is that when a client requests a cacheable URL for the very first time, the system creates a lock and starts generating the output data for the resource. Any other request to the same URL must wait until the first one is done (to not process the same resource multiple times which would put unnecessary load on server since all other requests can be served from cache as soon as the first one is finished). The timeout has been introduced (as per MAGNOLIA-3333) like a safety net for threads, to not wait forever in case the first one doesn't finish, for whatever reason. This used to indicated some performance troubles, caused by e.g. overloading by requests in peak hours. While it's possible to configure a blockingTimeout property at your EhCache configuration, the default value set to 10 seconds should already be more than enough.

Generated at Sun Feb 11 23:10:12 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.