Affects Version/s: 5.5.1-fuse-02-02
Fix Version/s: None
Similar Issues:Show 10 results
MB-782 Configureing JMX to use JAAS in ActiveMQ leads to 'unable to find LoginModule class' exception MB-1085 activemq-all.jar is missing the slf4j-log4j12 dependency MB-1233 activemq-admin commands need to be updated MB-949 Speeding up consumer transactions with ActiveMQ MB-749 Cannot initialize a JAAS PropertiesLoginModule instance using the Karaf/OSGi login configuration mechanism MB-781 ActiveMQ's <managementContext> does not allow configuration of SSL or JAAS MB-847 Allow for easy externalization of ActiveMQ configuration MB-280 MBean Configuration Syntac MB-765 Instance PID is placed in $ACTIVEMQ_HOME/data, not $ACTIVEMQ_BASE/data MB-274 Documentation for amqPersistenceAdapter's maxDataFileLength/maxFileLength setting
We have recently seen a couple a Support Request regarding the the use of the activemq-all.jar and the required libraries.
Can we add a section to the Fuse documentation that has the following information: http://activemq.apache.org/initial-configuration.html.
Please ensure it is clear that the activemq-all.jar includes all the required libraries. However if they choose to have more control of the jars used by ActiveMQ, rather than using the preconfigured activemq-all.jar, the following list of libraries should be used:
kahadb.jar (if you wish to use persistence)
J2EE APIs which could be the j2ee.jar from Sun or your J2EE container or you could use Geronimo's freely distributable geronimo-spec-j2ee.jar. If you are inside a servlet container and being dependent on the j2ee.jar causes you troubles, the parts of the J2EE jar we are dependent on are as follows...