You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2020/10/07 13:55:00 UTC

[jira] [Resolved] (CAMEL-15584) Switch UUID generator to new vanilla implementation

     [ https://issues.apache.org/jira/browse/CAMEL-15584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-15584.
---------------------------------
    Resolution: Fixed

> Switch UUID generator to new vanilla implementation
> ---------------------------------------------------
>
>                 Key: CAMEL-15584
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15584
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.6.0
>
>
> The default uuid generator was from old days based on ActiveMQ that as a broker had the need to generate UUID that are unique across a fleet of brokers (hosts) and therefore it included the hostname in the id. 
> This has the drawback today as the hostname needs to be resolved once which does a DNS lookup (its not an ip adr) and therefore it can delay the startup.
> Also on graalvm, quarkus etc then we use the new vanilla generator instead. Also we dont want to native compile and get the hostname of the os that compiled.
> The vanilla generates is fast and generate unique ids, also across a fleet of nodes. So lets consider switching to it.
> Also discussed on the chat forum
> https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/DefaultUUIDGenerator.20inet.20call.20timeout.20issue



--
This message was sent by Atlassian Jira
(v8.3.4#803005)