activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manish Gulati" <>
Subject RE: VM Transport..please help..
Date Thu, 16 Nov 2006 04:33:56 GMT
You can try using 


instead of 


Manish Gulati

This e-mail transmission and any documents, files, or previous e-mail
messages appended or attached to it, may contain information that is
confidential or legally privileged. If you are not the intended
recipient, or a person responsible for delivering it to the intended
recipient, you are hereby notified that you must not read this
transmission and that any disclosure, copying, printing, distribution,
or use of the information contained or attached to this transmission is
STRICTLY PROHIBITED. If you have received this transmission in error,
please immediately notify the sender by telephone + or
return e-mail message and delete the original
transmission, its attachments, and any copies without reading or saving
in any manner. Thank you.

-----Original Message-----
From: ActiveMQ_User1 [] 
Sent: Wednesday, November 15, 2006 7:27 PM
Subject: VM Transport..please help..


We're using Mule and Active MQ (version 3.2.2) in our app - the broker
embedded within Mule and we've specified the brokerUrl as vm://<server
name>. We're running the app as standalone windows service. However,
noticed that Active MQ seems to shut down after a while (usually after
running for a few days). This is annoying because we have to keep
the service every time the broker goes down. I was reading about the vm
transport on the website and came across this: 

The first client to use the VM connection will boot an embedded broker.
Subsequent connections will attach that the same broker. Once all VM
connections to the broker have been closed, the embedded broker will
automatically shutdown.

What does that last line imply? Has it got anything to do with my
Is there any way to prevent the broker from shutting down or restarting
it did? I read about the failover option..but not sure if that would
make a
difference. I have also tried using tcp://localhost:61616 instead of vm
that hasn't changed things much either - the broker keeps shutting down.

I'm not sure if I have configured things correctly. Here's my Mule
(just pasting the ActiveMQ part):

<connector name="jmsConnector"
	        <property name="specification" value="1.1"/>
	        <property name="connectionFactoryJndiName"
	        <property name="jndiInitialFactory"
	        <map name="connectionFactoryProperties">
	            <property name="brokerURL" value="vm://localhost"/> 
	            <property name="brokerXmlConfig"

And here's the broker part of my ActiveMQ config file:

      <tcpServerTransport uri="tcp://localhost:61616" backlog="1000"
useAsyncSend="true" maxOutstandingMessages="50"/>

        <journalPersistence directory="../var/journal">
          <jdbcPersistence dataSourceRef="derby-ds"/>

Not sure if I need the brokerUrl and a brokerXmlConfig.

Any ideas? I'd really appreciate any sort of help - I'm getting a little
dejected by it all. Thanks! 

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message