activemq-broker.xml is waiting for dependencies

[paul.berry]

Hi all,

Hopefully someone can answer a couple of questions for me.

I've downloaded and installed the latest FUSE ESB (4.4.1) and after a bit of fiddling about managed to get my camel bundle deployed correctly and working.  However, I've obviously broken something in the couple of days since then because now when I try to start servicemix I'm getting the following error:

Bundle activemq-broker.xml is waiting for dependencies

after a while that times out and I get

Unable to start blueprint container for bundle activemq-broker.xml due to unresolved dependencies

java.util.concurrent.TimeoutException

This is happening on 2 installs (one windows, one Fedora) and I can't seem to get past it.  Both machines have internet access so as far as I can see they should both be able to resolve any dependencies correctly. 

As a last ditch attempt to fix this I decided to delete my Fuse install and start again.  However, after deleting the entire Fuse install directory and re-extracting I have the same problem.  Also, doing 'OSGI:list' shows the same bundles installed as before I deleted / re-installed (ie: things I'd installed into the previous install are still installed).  So, here's my questions:

1) how can I fix the dependency issue I'm having?

2) how do I wipe the slate clean and start again with FUSE ESB?  is there a hidden config file outside the install directory that I need to get rid of as well?

Cheers!

[ffang]

Hi,

The error indicates that aries transaction manager bundle isn't available, did you change any configuration for your FUSE ESB? What's the exact version for your FUSE ESB?

Could you post the result of

list -t 0|grep Aries

Btw, generally just remove $FUSE_ESB/data(this remove the bundle cache) folder you can get a clean env again if you didn't change any configuration.

Freeman

[paul.berry]

Thanks for the quick reply...

output from list -t 0|grep Aries

Apache Aries Proxy Bundle (0.3.0)

Apache Aries Util (0.3.0)

Apache Aries Blueprint Bundle (0.3.1)

Apache Aries JMX Blueprint Bundle (0.3.0)

Apache Aries JMX Bundle (0.3.0)

Apache Aries Transaction Manager (0.2.0.incubating)

Apache Aries Transaction Manager (0.3.0)

Apache Aries Transaction Enlisting JDBC Datasource (0.3.0)

Apache Aries Transaction Blueprint (0.3.0)

How do I reset sevicemix if I have made configuration changes? (I assume you mean installed bundles using features:install).  where is the list of installed features kept?

Edited by: paul.berry on Feb 22, 2012 1:10 PM

[paul.berry]

hmm, I seem to have stopped the exception by:

installing the 0.3 version of the transaction manager:

osgi:install -s mvn:org.apache.aries.transaction/org.apache.aries.transaction.manager/0.3

uninstalling the old version

osgi:uninstall 53

and restarting servicemix.

However, That was just a guess so I don't know if that's the right way to fix this issue or not.  Will try deploying my route now and see if it works.

[paul.berry]

Okay, more info on this problem:

I started again from scratch (completely clean install directory).

First attempt to launch service mix hung at 'activemq-broker.xml awaiting namespace handlers'

I got bored waiting and killed the process.

Second attempt I didn't get an exception but I didn't see anything about the message broker starting.  Shutdown and restart again...

On this attempt it hung at 'activemq-broker.xml is waiting for dependencies (javax.transaction.TransactionManager)'

I then run the following commands:

osgi:uninstall 53

osgi:install -s mvn:org.apache.aries.transaction/org.apache.aries.transaction.manager/0.3

shutdown / restart and the message broker finally starts (yay!)

[ffang]

Hi,

Thanks for the investigation.

OK, the default activemq feature use old version(0.2-incubating) of org.apache.aries.transaction.manager bundle,   we should use 0.3 instead.

I'll create an internal jira ticket and fix it soon.

As a workaround, you can edit $FUSE_ESB/./system/org/apache/activemq/activemq-karaf/5.5.1-fuse-01-20/activemq-karaf-5.5.1-fuse-01-20-features.xml

change

then remove $FUSE_ESB/data folder and restart FUSE ESB.

Freeman

Edited by: ffang on Feb 23, 2012 12:01 AM

[paul.berry]

Thanks Freeman.

I'm now having another issue with actually deploying my bundle into servicemix, but I'll open another thread for that.

[paul.berry]

Hmm, it looks like I spoke too soon.  Even after making this change I was still having issues with the activemq-broker.

I 'fixed' my issues by downloading and using 4.4.0 instead of the 4.4.1 I had been trying to use. I don't know what changed between those two versions but 4.4.1 would hang / refuse to start with one of a number of errors at least 75% of the time and I was completely unable to get it working conistently and reliably.  4.4.0 works without a problem.

Some issues I had with 4.4.1:

The console doesn't 'remember' commands between sessions.  eg: start servicemix, enter a command (osgi:list), then shut down and restart servicemix.  Press 'up' and the last command is not shown in 4.4.1.  In 4.4.0 it is.

activemq broker refusing to start either due to 'waiting for dependencies' or 'waiting for namespace handlers'

Everything appearing to start up correctly (ie: no exceptions in the log) but the majority of bundles showing 'resolved' rather than installed or active

Obviously some or all of these might be issues with my setup (although I saw the same issues on 2 different installations, 1 windows and 1 linux) but for now I'll stick to 4.4.0.

[moacsjr_moacsjr]

Hello Paul,

I also noticed these same problems.

Moa.