[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-451) UUID for auto-generated jvmRoute does not work with WildFly

Radoslav Husar (JIRA) issues at jboss.org
Thu Feb 26 05:38:49 EST 2015


    [ https://issues.jboss.org/browse/MODCLUSTER-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043863#comment-13043863 ] 

Radoslav Husar commented on MODCLUSTER-451:
-------------------------------------------

We no longer use it in WildFly, instance-id must be set uniquely on all nodes. Also note you should never bind to 0.0.0.0.

> UUID for auto-generated jvmRoute does not work with WildFly
> -----------------------------------------------------------
>
>                 Key: MODCLUSTER-451
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-451
>             Project: mod_cluster
>          Issue Type: Bug
>          Components: Core & Container Integration (Java)
>    Affects Versions: 1.3.0.Final
>         Environment: WildFly 8.2.0.Final, mod_cluster 1.3.0
>            Reporter: Michal Babacek
>            Assignee: Radoslav Husar
>             Fix For: 1.3.1.Beta3
>
>
> It appears that UUID is not generated with WildFly/Undertow/mod_cluster setup. For example, if one does not set any instance-id/jvmRoute and binds to 0.0.0.0, one gets {{localhost}} jvmRoute Instead of a proper UUID.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)


More information about the mod_cluster-issues mailing list