[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-458) Add JVMRoute or node identifier to httpd/mod_cluster errors

[Michal Babacek (JIRA)]

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

Michal Babacek updated MODCLUSTER-458:
--------------------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/modcluster/mod_cluster/pull/148, https://github.com/modcluster/mod_cluster/pull/147


Done.

The new implementation shows error messages such as:
{noformat}
21:33:11,301 ERROR [org.jboss.modcluster] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) MODCLUSTER000042: Error MEM sending STATUS command to 192.168.122.1/192.168.122.1:6666, configuration will be reset: MEM: Can't read node with "Worker-1" JVMRoute
{noformat}
or
{noformat}
MEM: Old node with "WORKER-001" JVMRoute still exists
{noformat}
instead the old ambiguous:
{noformat}
MEM: Can't read node
{noformat}

> Add JVMRoute or node identifier to httpd/mod_cluster errors
> -----------------------------------------------------------
>
>                 Key: MODCLUSTER-458
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-458
>             Project: mod_cluster
>          Issue Type: Feature Request
>          Components: Native (httpd modules)
>            Reporter: Coty Sutherland
>            Assignee: Michal Babacek
>
> Messages such as:
> [Tue Apr 14 10:38:56 2015] [warn] manager_handler STATUS error: MEM: Can't read node
> are very difficult to troubleshoot given the limited context provided. It would be great if we could add some sort of node identifier or the JVMRoute of the node to the message above.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)