I did try this using Karaf 2.0.0 which uses Felix 3, unfortunately, because of the proprietary nature of the implementation, I am unable to provide the stack-trace. I'll try to get something reproducable without my company's code and send it to you.
v/r, Mike Van ----- Original Message ----- From: "Richard S. Hall" <[email protected]> To: [email protected] Sent: Tuesday, October 12, 2010 2:14:13 PM Subject: Re: Unable to acquire global lock for resolve On 10/12/10 13:56, [email protected] wrote: > > Nope, this still is happening but the feedback on how to keep it from > happening has been negligible. Hmm. I last responded to you with a request for a reproducible scenario and the suggestion of trying it on a newer framework version if you hadn't already, but I didn't hear anything from you on either topic. So, what's up? Can you get me a scenario and did you try with the latest version? -> richard > > > v/r, > > > > Mike Van > ----- Original Message ----- > From: "Richard S. Hall"<[email protected]> > To: [email protected] > Sent: Sunday, October 10, 2010 7:49:27 PM > Subject: Re: Unable to acquire global lock for resolve > > Any follow up on this? > > -> richard > > > On 9/29/10 3:28 PM, Richard S. Hall wrote: >> On 9/29/10 15:19, Richard S. Hall wrote: >>> On 9/29/10 12:59, [email protected] 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. >> Of course, this depends on which version of the Felix framework you >> are using...we made some changes in this area in version 3.0.2, I >> believe, so if you aren't using at least that version you should try >> to upgrade and see what happens with it. >> >> -> richard >> >>> -> richard >>> >>>> >>>> v/r, >>>> >>>> >>>> >>>> Mike Van >>>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
