I didn't realize that config was added recently (looks like 5.12.0). It
also looks like the dependency jcl-over-slf4j was added as part of that
commit as well so not sure if that is also causing you problems.
I'm not entirely sure why it was just added (probably just to make it easy
to provide fo
The file log4j.properties in activemq-all was added on 2/12/15 (not sure
what release of ActiveMQ that correlates to). That's the kicker. When we
upgraded recently from 5.11.1 to 5.13.1 is when the problem became
apparent. You can see why. It's a non-trivial exercise to coordinate
multiple teams to
Nothing has been changed so I don't know what you are referring to. That
log4j dependency has been included in that jar for a while, since
AMQ-3715. The main point of that jar file is it is an easy way to spin up
a broker for testing and it is supposed to contain concrete dependencies of
things so
Per the online documentation, using activemq-all is a legitimate way to
connect to a broker. For those that were happily using it up until now,
whether others consider it 'overkill' or not, they are now screwed by this
change. Regardless, stating that one can 'fine tune' dependencies by
switching a
On 03/29/2016 02:43 PM, stak wrote:
So are you saying that activemq-all.jar is not a production grade jar to be
used as a client jar when they want to connect to an external activemq as a
client?. Is the purpose of that jar really only for a quick unit test of
sorts?
--
View this message in c
If you just need to connect as a JMS client, you just need the
activemq-client jar and its transitive dependencies. If you are using
something like maven then you can add that jar to your pom file and then
exclude dependencies you don't want (in this case log4j).
On Tue, Mar 29, 2016 at 2:43 PM,
So are you saying that activemq-all.jar is not a production grade jar to be
used as a client jar when they want to connect to an external activemq as a
client?. Is the purpose of that jar really only for a quick unit test of
sorts?
--
View this message in context:
http://activemq.2283324.n4.na
On 03/29/2016 12:30 PM, stak wrote:
In a particular application, logback is being used for the application
logging. When the application added dependency on activemq-all 5.13.1 jar
in order to access ActiveMQ, it appears that activemq-all has dependendency
on log4j which seem to conflicting the
