When using web apps then you will get a broker created in each WAR as they are in separate class loaders even if its a singleton in a spring.xml.
Either add ActiveMQ to the global classpath, create a broker in just one of your WARs or run the broker elsewhere. On 8/8/06, jamo <[EMAIL PROTECTED]> wrote:
No, the config section below is the only broker that's defined. But, I did notice from the Tomcat log that Spring is apparently creating the first broker in a different (app root) web context and then it trys to create a second broker for the app web context (which of course generates the error). Not sure why this occurring, but I'm going to take a look at the Spring options for creating the broker as a singleton. -- View this message in context: http://www.nabble.com/Spring-Embedded-broker-Journal-already-opened-error-tf2069517.html#a5706315 Sent from the ActiveMQ - User forum at Nabble.com.
-- James ------- http://radio.weblogs.com/0112098/
