Hi Geoffry,
the Camel vm:// protocol (in the Camel core) is supported.
But your usage is not correct.
The vm: component provides asynchronous SEDA behavior so that messages
are exchanged on a BlockingQueue and consumers are invoked in a separate
thread pool to the producer.
It's used to communicate between two routes in the same JVM.
It's not designed to use a TCP connection.
Regards
JB
On 09/10/2011 12:21 AM, Geoffry Roberts wrote:
All,
I have a blueprint file that works if I use tcp:// protocol but does not
work if I use vm:// all else being equal.
Is the vm protocol supported?
My blueprint file, which I drop into the deploy directory (See below.)
queues messages nicely if I use tcp. Of course, everything is running in
the same jvm.
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0";>
<bean id="jms"
class="org.apache.activemq.camel.component.ActiveMQComponent">
<!-- This works. --> <property name="brokerURL"
value="tcp://localhost:61616" />
<!-- This does not work. <property name="brokerURL"
value="vm://localhost:61616" /> -->
</bean>
<camelContext xmlns="http://camel.apache.org/schema/blueprint";>
<route>
<from uri="timer:test?period=5000" />
<setBody>
<constant>Ave Mundus!!</constant>
</setBody>
<to uri="jms:queue:ave" />
</route>
</camelContext>
</blueprint>
Thanks
--
Geoffry Roberts
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
