Versions Compared

Old Version 12

changes.mady.by.user Reuben Garrett

Saved on

compared with

New Version 13

changes.mady.by.user Reuben Garrett

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: readability

...

This component differs from the Seda component in that VM supports communication across CamelContext instances - so you can use this mechanism to communicate across web applications (provided that camel-core.jar is on the system/boot classpath).

This component VM is an extension to the Seda component.

URI format

Code Block
vm:someNamequeueName[?options]

Where someName queueName can be any string to uniquely identify the endpoint within the JVM (or at least within the classloader that loaded camel-core.jar)

...

Info
titleCamel 1.x to 2.3 - Same URI must be used for both producer and consumer

An exactly identical VM endpoint URI must be used for both the producer and the consumer endpoint. Otherwise, Camel will create a second VM endpoint despite that the someName queueName portion of the URI is identical. For example:

Code Block
java
java
from("direct:foo").to("vm:bar?concurrentConsumers=5");

from("vm:bar?concurrentConsumers=5").to("file://output");

Notice that we have to use the full URI, including options in both the producer and consumer.

In Camel 2.4 this has been fixed so that only the queue name must match. Using the queue name bar, we could rewrite the previous exmple as follows:

Code Block
java
java
from("direct:foo").to("vm:bar");

from("vm:bar?concurrentConsumers=5").to("file://output");

...