Yes that looks correct.
I suspect that perhaps a different configuration file is being loaded
up instead of the one you think is being loaded then.
On 6/14/06, William Blackburn <[EMAIL PROTECTED]> wrote:
Sorry if this is an often requested question, but I've been looking
over the docs and list archives and I just can't seem to find the
answer.
We have multiple developers frequently deploying activemq in the own
environments during test/development, yet the activemq brokers all
still try and federate. I've played withe the activemq config, but no
matter what I try I can't stop them. Is there a way to prevent the
discovery and federation process? the broker section of my file
currently looks like:
<broker id="broker" useJmx="false">
<persistenceAdapter>
<journaledJDBC journalLogFiles="5"
dataDirectory="#dataDir" dataSource="#postgres-ds"/>
</persistenceAdapter>
<transportConnectors>
<transportConnector uri="tcp://localhost:61616"/>
</transportConnectors>
</broker>
--
Regards,
Hiram
