[jboss-jira] [JBoss JIRA] Resolved: (JBAS-6423) When JNDI cluster node definition method not available, make it more visible.

[Galder Zamarreno (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Galder Zamarreno resolved JBAS-6423.
------------------------------------

    Resolution: Done


> When JNDI cluster node definition method not available, make it more visible.
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-6423
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6423
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-4.2.3.GA, JBossAS-5.0.0.GA
>            Reporter: Galder Zamarreno
>            Assignee: Galder Zamarreno
>             Fix For: JBossAS-5.1.0.Beta1
>
>
> If jboss:service=${jboss.partition.name:DefaultPartition} MBean has <depends>jboss:service=Naming</depends>
> lacking due to misconfiguration, cluster partition views can appear like this:
> New cluster view for partition ckern02050: 6 ([210.1.12.29:-e82b3e3:11ed3b44d77:-7fff, 210.1.12.22:290190e2:11ed3b4545f:-7fff, 210.1.12.29:3575580a:11ed3b4e374:-7ffe, 210.1.12.22:-4a060875:11ed3b4f980:-7fff, 210.1.12.152:-6fdd83c3:11ed3b4ffad:-7fff, 210.1.12.22:65e6f006:11ed3b56eb8:-7fff, 210.1.12.29:1ec6be2f:11ed3b56d3c:-7fff] delta: 1)
> This can be rather confusing and the messages leading to the reason why these hexadecimal ports appear are
> digged in debug messages.
> The aim of this JIRA is to make these messages more visible.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira