activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <>
Subject Re: Connection Refused from ActiveMQConnectionFactory
Date Mon, 04 Mar 2013 14:20:41 GMT
The service factory that auto creates the broker based on
etc/org.apache.activemq.server-default.cfg only supports spring xml at the
moment, the injection of properties into a blueprint context that
is explicitly created by the ManagedServiceFactory needs to be in
investigated some more to have is support blueprint in the same way.
Please create an enhancement to track this, because it is something we
should do for the next release.

But the old way of deploying a blueprint xml that contains a broker is
still possible, just drop the blueprint xml into the deploy directory or
add it to your bundle and it will be get initialised.
What has been dropped are the karaf commands that do the copy into the
deploy directory for you.
Using a managed service factory and external properties that can be visible
via config admin provides a more consistent karaf experience.

On 4 March 2013 13:11, Neduz <> wrote:

> Hello,
> I've tried adding
> As first blueprint item in the blueprint xml file as this services provided
> by the bundle from mvn:org.apache.activemq/activemq-osgi/5.8.0
> But that doesn't resolve the problem apparently.
> And the Broker is only ready about 1.1s later:
> Did I correctly implement your suggestion? I've added the filter option
> because file-installer also provides an ManagedServiceFactory. And the
> availability and activation options I added assuming they would prevent
> blueprint from just making proxies before the service is actually
> available.
> At every Karaf start another bundle or bundles fail to start due to the
> connection refused message. Sometimes (about 1 in 4 or 1 in 5 times) all
> bundles start perfectly.
> PS: I agree that using the "waiting" for an OSGI service to be available is
> the best approach for a mixed blueprint/spring-beans environment; but was
> the Blueprint method for creating a broker deliberately dropped? If yes for
> what reason(s)?
> Kind regards,
> Tom Mercelis
> --
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message