This content has been marked as final.
Show 4 replies
-
1. Re: A lock could not be obtained within the time requested
heiko.braun Sep 23, 2009 3:31 PM (in response to heiko.braun)This is worse then I thought. On a running jboss instance take a look at http://localhost:8080/jmx-console/HtmlAdaptor?action=invokeOpByName&name=jboss.system:type=ServerInfo&methodName=listThreadCpuUtilization
You'll see a bunch of "ODE-Server-X" threads with heavy CPU utilization. -
3. Re: A lock could not be obtained within the time requested
heiko.braun Sep 24, 2009 3:37 PM (in response to heiko.braun)I have switched trunk to H2 instead of derby. Although the initial error is gone now, others did occur. However the H2 exception handling is much more verbose and better to understand. And besides, it's the same DB the ESB installation already uses as a default. So we got one less artifact to worry about.
I'll keep you guys posted. -
4. Re: A lock could not be obtained within the time requested
heiko.braun Sep 24, 2009 3:40 PM (in response to heiko.braun)But what we really need is test coverage against a decent DB matrix:
https://jira.jboss.org/jira/browse/RIFTSAW-64
Anyone volunteering?