Starting with Camel 2.5, Camel supports 3rd party UUID generator(s). This is useful, if e.g. your messaging provider does not support UUID's with a length of 36 characters (like Websphere MQ). Another useful scenario is to use a simple counter for testing purpose. With this it is easier to correlate the exchanges in the log/debugger.
You only have to implement org.apache.camel.spi.UuidGenerator and tell Camel, that it should use your custom implementation:
Camel will configure this UUID generator by doing a lookup in the Spring bean registry to find the bean of the type org.apache.camel.spi.UuidGenerator.
Camel comes with three implementations of org.apache.camel.spi.UuidGenerator:
From Camel 2.10.7/2.11.1 onwards the JVM system property with key: activemq.idgenerator.port can be used to assign a specific port which is used during initialization of the UUID generator. By default the port number 0 is used. Though in some cloud infrastructures this is not allowed, and thus a specific port can be assigned instead.
From Camel 2.5 onwards the ActiveMQUuidGenerator is the default generator because its the fastest.