[jboss-jira] [JBoss JIRA] Commented: (JBAS-6423) When JNDI cluster node definition method not available, make it more visible.
Galder Zamarreno (JIRA)
jira-events at lists.jboss.org
Tue Jan 27 11:59:44 EST 2009
[ https://jira.jboss.org/jira/browse/JBAS-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449897#action_12449897 ]
Galder Zamarreno commented on JBAS-6423:
----------------------------------------
Re: log.debug("JNDI has been found but the service wasn't started so we cannot " +
"be entirely sure we are the only one that wants to use this PORT " +
"as a GUID on this host.");
Brian: Should be reworded and made a WARN.
Re: catch (ReflectionException e)
{
log.debug ("JNDI querying has returned an exception, cannot use this strategy to find a node GUID for the cluster");
}
Brian: Should be reworded and made a WARN.
Re: catch (InstanceNotFoundException e)
{
log.debug ("JNDI not running here, cannot use this strategy to find a node GUID for the cluster");
}
Brian: Should be reworded and made INFO. Example:
catch (InstanceNotFoundException e)
{
log.debug ("JNDI is not running here, cannot use the JNDI port strategy for defining a node GUID for the cluster");
}
> 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
More information about the jboss-jira
mailing list