Page History

...

Sync : direct:// + threads()

• Same JVM but different CamelContext

This approach is suitable for solutions running in standalone mode or deployed in Web Application Server (different WAR/EAR)

vm://

Remark : This component cannot be used between different OSGI servers

• • With persistence

JMS queue engine : jms:// + threads()
Activemq queue engine : activemq:// + threads()

...

If you prefer to deploy routes on servers having different CPU/memory, then you can use the following components

• • Suitable for solutions running in standalone mode or deployed in Web Application Server (different WAR/EAR)

vm://

This component cannot be used between different OSGI servers

• • Between Within or between different instances of OSGI servers (SMX4)

...