An embedded broker executes within the same JVM process as the client(s) that is using its services. There may be one or more clients residing within a single JVM, each executing within its own thread of execution; all clients access the same embedded broker. The clients communicate with the embedded broker via direct method invocation (DMI) as opposed to serializing command objects across a TCP/IP-based transport connector.
http://activemq.apache.org/how-do-i-embed-a-broker-inside-a-connection.html Unlike an embedded broker, a standalone broker is one that does not have clients co-residing in its JVM and instead communicates with its clients through one of the network-based transport connectors. It is possible to have standalone and embedded brokers communicate with one another. Joe Get a free ActiveMQ user guide @ http://www.ttmsolutions.com stanleychen wrote: > > Hello, > > Sorry for such basic question. I am using Spring for my application. I > am wondering what differences there is between "embedded" ActiveMQ and > "stand-alone" ActiveMQ. If I run ActiveMQ embedded, does thing mean > remote clients can still connect up? Is my understand correct that > embeeded ActiveMQ means that ActiveMQ will start automatically when I > start my Spring application, or is there some other meanings to it? > > Thank you. > -- View this message in context: http://www.nabble.com/difference-between-running-ActiveMQ-embedded-and-stand-alone-tp19518221p19518570.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
