When you say "started a connection to the broker". Do you mean as a client to connect to a remote broker?
The stacktrace indicate you need slf4j-api.jar on the client side. And possible also the slf4j-log4j12.jar if you want to use log4j as the target logger.
I mean I've got a client application that has activemq-all-5.5.0-fuse-00-27.jar on classpath and (let's assume) does not depend on anything else, does not use logging etc. And when I call:
I get the error and stack trace. The broker is not even started, so the problem sits in activemq-all-5.5.0-fuse-00-27.jar - unless some other jar must be included, but it was not the case with previous ActiveMQ release, and I believe I haven't seen any additional requirements in the release note (although I might have missed something).
I guess I'm not the only one with such problem: http://activemq.2283324.n4.nabble.com/Problem-with-SLF4J-td3531330.html. Unfortunatelly problem was not solved in the thread.
the solution in that thread should work for you. The user resolved slf4j classpath issue and the rest of the thread was regarding other issue.
So, in 5.5.0 we use slf4j for logging. We provide slf4j-api in activemq-all, but your application should include one of the binders (as explained at http://www.slf4j.org/codes.html#StaticLoggerBinder).
I checked first and last post of the thread and infered the problem was not solved - my bad. Thanks for the hints. I guess with slf4j 1.6 where there will be a default binder there will be less confusion. Problem solved.
I'm glad it helped!