We use Camel extensively in our app. The broker configuration looks like this
<broker:broker useJmx="false" persistent="false" brokerName="myBroker"> <broker:transportConnectors> <broker:transportConnector name="vm" uri="vm://myBroker" /> <broker:transportConnector name="tcp" uri="tcp://${broker.host}:${broker.port}" /> </broker:transportConnectors> <broker:managementContext> <broker:managementContext connectorPort="1111"> </broker:managementContext> </broker:managementContext> <broker:systemUsage> <broker:systemUsage> <broker:memoryUsage> <broker:memoryUsage limit="20 mb"/> </broker:memoryUsage> <broker:storeUsage> <broker:storeUsage limit="1 gb"/> </broker:storeUsage> <broker:tempUsage> <broker:tempUsage limit="100 mb"/> </broker:tempUsage> </broker:systemUsage> </broker:systemUsage> </broker:broker> The broker is used for inter-vm communication and occasionally for third party feed processing. Is there anything we can do to improve this as the startup is now causing performance issues. I must say though, that this is very random and sometimes the broker comes up spontaneously. Thanks in advance -- View this message in context: http://camel.465427.n5.nabble.com/Embedded-ActiveMQ-in-Camel-very-very-start-up-slow-up-to-10-minutes-to-startup-tp5731541.html Sent from the Camel - Users mailing list archive at Nabble.com.