Hi there,
worked for me in 5.9.1...
Tom
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Connection-Refused-from-ActiveMQConnectionFactory-tp4664195p4689158.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hello,
Maybe the user forum is not the recommended place for this discussion: but
besides the blueprint xml discussion; there's another "design" question that
I'm not sure of how it is seen by the AMQ devs at this moment:
I'll be making a few assumptions since I'm not very experienced with
Active
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
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 y
I guess the service factory that creates the broker should register a vm
connection factory service in osgi once it has successfully started a
broker,
that could then be used to depend on. I think that is a sensible
enhancement.
One thing that may help today is adding a dependency on the service
