Hi Check the documentation for the *exact* semantics of the multipleConsumers option. Given your example each of the given vm consumers (actually it's SedaConsumer as "VmComponent extends SedaComponent") will *compete* for getting that *single* exchange your're sending, and depending which one get's it, the message will be consumed either inside your first or second Camel context. This behaviour is intended, look at the *static* QUEUES field of VMComponent.
For the behaviour you're looking for (publish/subscribe style of messaging) just stick to one single Camel context and check the example [2] where using [3] you could run it as well. [1] http://camel.apache.org/seda.html#SEDA-Options [2] http://camel.apache.org/seda.html#SEDA-UsingmultipleConsumers [3] https://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/test/java/org/apache/camel/spring/example/FooEventRouteTest.java Babak -- View this message in context: http://camel.465427.n5.nabble.com/VM-queue-for-2-camel-context-tp5485770p5486115.html Sent from the Camel - Users mailing list archive at Nabble.com.
