On Thu, Oct 2, 2008 at 3:37 AM, Dejan Bosanac
<[EMAIL PROTECTED]> wrote:
> If you are taking this route, you can try defining your broker
> configuration in a separate xml file and do something like
>
> BrokerService broker = BrokerFactory.createBroker(new
> URI("xbean:activemq.xml"));
> broker.sta
If you are taking this route, you can try defining your broker
configuration in a separate xml file and do something like
BrokerService broker = BrokerFactory.createBroker(new
URI("xbean:activemq.xml"));
broker.start();
it will be easier to configure it that way.
Cheers
--
Dejan Bosanac
htt
I was able to configure my broker programatically within my startup mbean
using the following without jmx conflicts:
BrokerService broker =
org.apache.activemq.broker.BrokerFactory.createBroker("broker:(vm://localhost)");
broker.setUseJmx(true);
broker.setPersistent(false);
broker.sta
OK so I have narrowed this down to the amq:broker element behaves badly in
spring or in spring within JBoss. I changed my broker name to localhost2.
Spring or JBoss appears to be registering this mbean twice. Anybody have
any ideas on how to fix this?
So I tried changing my connectionFactory to use the following URL
brokerURL="vm://localhost?create=false"
This did not solve my problem. Ordering does not seem to matter. I get this
issue regardless of the ordering.
--
View this message in context:
http://www.nabble.com/Configuring-Embedded
2008/10/1 James Strachan <[EMAIL PROTECTED]>:
> 2008/10/1 CB4 <[EMAIL PROTECTED]>:
>>
>> I forgot to mention that if I omit the amq:broker element from my context
>> everything works just fine as the connectionFactory created the broker with
>> default behavior (using the vm URI). However this won
2008/10/1 CB4 <[EMAIL PROTECTED]>:
>
> I forgot to mention that if I omit the amq:broker element from my context
> everything works just fine as the connectionFactory created the broker with
> default behavior (using the vm URI). However this won't do it for me as I
> need to configure the broker
I forgot to mention that if I omit the amq:broker element from my context
everything works just fine as the connectionFactory created the broker with
default behavior (using the vm URI). However this won't do it for me as I
need to configure the broker with my own settings.
--
View this message
Here is the full stack trace:
2008-10-01 09:29:31,059 ERROR main
[org.apache.activemq.broker.BrokerService] Failed to start ActiveMQ JMS
Message Broker. Reason: javax.management.InstanceAlreadyExistsException:
org.apache.activemq:BrokerName=localhost,Type=Broker already registered.
javax.manageme
