-
1. Re: Is there any problem in setting lock acquire timeout from web-console of WildFly-8.2?
jaikiran Apr 10, 2015 5:29 AM (in response to valsaraj007)Lock acquire timeout on what resource?
-
2. Re: Is there any problem in setting lock acquire timeout from web-console of WildFly-8.2?
valsaraj007 Apr 10, 2015 7:17 AM (in response to jaikiran)Hi jaikiran,
Is there any way to find out which resource thrown this timeout error?
I did trial and error. Set high values to each entry under infinispan and finally found the correct one.
<cache-container name="web" default-cache="dist" module="org.wildfly.clustering.web.infinispan">
<transport lock-timeout="120000"/>
<distributed-cache name="dist" batching="true" mode="ASYNC" owners="2" l1-lifespan="0">
<locking isolation="REPEATABLE_READ" acquire-timeout="300000" concurrency-level="1000"/> ----> Added
<file-store/>
</distributed-cache>
</cache-container>
When I set this to 5minutes, timeout error gone. This was happening when I uploaded a file with large size. I wonder why it is using cache for file upload. This upload action class is in request scope. Can you share more details on this?
Thanks!
-
3. Re: Is there any problem in setting lock acquire timeout from web-console of WildFly-8.2?
jaikiran Apr 12, 2015 1:35 AM (in response to valsaraj007)Is your web application marked as clustered, through the use of <distributable/> tag in the web.xml? Is that intentional?
-
4. Re: Is there any problem in setting lock acquire timeout from web-console of WildFly-8.2?
valsaraj007 Apr 12, 2015 11:43 PM (in response to jaikiran)Yes, it is marked as clustered through the use of <distributable/> tag in the web.xml. We need to add HA and scalability to the application. Is there any other way to do this?