Bug 1011365

Summary: Solution needed for JBAS010213: Cannot acquire lock default-host
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: johnborgjacob <johnborgjacob>
Component: ClusteringAssignee: Paul Ferraro <paul.ferraro>
Status: CLOSED NOTABUG QA Contact: Jitka Kozana <jkudrnac>
Severity: urgent Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.1.1CC: jason.greene, johnborgjacob, rhatlapa
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Windows   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-12 14:11:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
standalone-ha none

Description johnborgjacob 2013-09-24 07:20:26 UTC 
Created attachment 802066 [details]
standalone-ha

Description of problem: BAS010213: Cannot acquire lock default-host


Version-Release number of selected component (if applicable): Redhat EAP 6.1.1


How reproducible: every time


Steps to Reproduce:
setup a mod_jk loadbalance setup using standalone-ha configuration
enable session replication in the application
the first time the request is processes correctly in second or subsequent times the session lock happens
this is supposedly fixed as per 
https://bugzilla.redhat.com/show_bug.cgi?id=900204
but its still happening resulting in session replication not to be used and application is not usable

Actual results:
Session locking happens

Expected results:
Sesssion lock should not happen

Additional info:
attached my standalone-ha file for reference
Comment 1 johnborgjacob 2013-09-24 09:57:27 UTC 
Got this issue fixed by placing jboss-web.xml in web.xml, it would be good if this is updated in the documentation.
Comment 2 johnborgjacob 2013-09-24 09:58:43 UTC 
What i meant was, got this issue fixed by placing jboss-web.xml in web-inf folder, it would be good if this is updated in the documentation.
Comment 4 Paul Ferraro 2014-03-05 16:42:39 UTC 
Do you have a stack trace?
Comment 6 johnborgjacob 2014-03-06 16:22:57 UTC 
(In reply to Paul Ferraro from comment #4)
> Do you have a stack trace?

Its been a long time since this issue happened I didn't keep the trace. The issue got resolved by placing jboss-web.xml in web-inf folder, if you still want the trace its the same as in the original defect (https://bugzilla.redhat.com/show_bug.cgi?id=900204)

my request is to update the docs so that its easier to solve