-
1. Re: "could not obtain lock within 5000 MILLISECONDS" on @Stateful bean
jaikiran Feb 10, 2016 10:54 PM (in response to atchijov-vgw)Can you post the entire exception stacktrace and any relevant code? That will help us understand what's going on. By the way, which specific version of WildFly is this?
-
2. Re: "could not obtain lock within 5000 MILLISECONDS" on @Stateful bean
atchijov-vgw Feb 11, 2016 2:47 AM (in response to jaikiran)Hi Jaikiran,
Thanks for your response.
We are using Wildfly 8.2.0 Final
I have create a public gist with all relevant information: Stack trace and relevant code snippets for https://developer.jboss.org/message/950700?et=watches.email.thread#950700 · G…
As I mentioned in the first post, as of now KickboxApi.verify() method does not do anything. (It checks for the particular setting to see if this feature has been enabled and than exit)
Please let me know if you need any additional information, I would be more than happy to provide it.
Once again, thanks for taking time to look into this problem,
Andrei
-
3. Re: "could not obtain lock within 5000 MILLISECONDS" on @Stateful bean
jaikiran Feb 11, 2016 7:56 AM (in response to atchijov-vgw)Can you take a thread dump of the server process when this happens? You can use jstack to take the thread dump and post that attach here.
-
4. Re: "could not obtain lock within 5000 MILLISECONDS" on @Stateful bean
rhusar Feb 11, 2016 2:39 PM (in response to atchijov-vgw)Possibly related to [WFLY-5568] Concurrent access timeout -- could not obtain lock within 5000 MILLISECONDS - JBoss Issue Tracker if your configuration is clustered or invoking on 2 clusters.