10 messages in org.apache.felix.usersRe: Unable to acquire global lock for...| From | Sent On | Attachments |
|---|---|---|
| mvan...@comcast.net | Sep 29, 2010 9:58 am | |
| Richard S. Hall | Sep 29, 2010 12:19 pm | |
| Richard S. Hall | Sep 29, 2010 12:27 pm | |
| Richard S. Hall | Oct 10, 2010 4:49 pm | |
| mvan...@comcast.net | Oct 12, 2010 10:56 am | |
| Richard S. Hall | Oct 12, 2010 11:13 am | |
| mvan...@comcast.net | Oct 12, 2010 11:30 am | |
| Arjun Panday | Feb 2, 2011 7:47 am | |
| Richard S. Hall | Feb 2, 2011 8:03 am | |
| Bertrand Delacretaz | Mar 2, 2011 4:45 am |
| Subject: | Re: Unable to acquire global lock for resolve | |
|---|---|---|
| From: | Richard S. Hall (hea...@ungoverned.org) | |
| Date: | Sep 29, 2010 12:19:36 pm | |
| List: | org.apache.felix.users | |
On 9/29/10 12:59, mvan...@comcast.net wrote:
All,
When attempting to deploy dom4j as part of a Hibernate 3 feature, I get the
following error:
Error executing command: Could not start bundle
mvn:org.dom4j/com.springsource.org.dom4j/1.6.1 in feature(s): Unresolved
constraint in bundle com.springsource.org.dom4j [59]. Unable to acquire global
lock for resolve.
When attempting to deploy the feature a second time it resolves. However, in
another feature for jdbc, no matter how many times I attempt to deploy the
feature, the global lock never resolves. Can anyone give me feedback about why
this is happening?
This is a recent change to try to deal with potential deadlocks. Typically, this situation arises when people are trying to do refreshes and resolves at the same time. It shouldn't occur if you are just trying to resolve bundles.
If you have a reproducible scenario, open up a JIRA issue and describe the precise steps to reproduce and I can take a closer look.
-> richard
v/r,
Mike Van