[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1107) Less noisy client-side failover
Tim Fox (JIRA)
jira-events at lists.jboss.org
Sun Oct 14 06:56:05 EDT 2007
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1107?page=all ]
Tim Fox updated JBMESSAGING-1107:
---------------------------------
Fix Version/s: Unscheduled
> Less noisy client-side failover
> -------------------------------
>
> Key: JBMESSAGING-1107
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1107
> Project: JBoss Messaging
> Issue Type: Feature Request
> Components: JMS Clustering
> Affects Versions: 1.4.0.GA
> Reporter: Ovidiu Feodorov
> Assigned To: Ovidiu Feodorov
> Priority: Minor
> Fix For: Unscheduled
>
>
> When a cluster node failure occurs, the client side reports a significant amount of ERROR logging. This is technically correct, those errors are actually occurring, but a clustered connection factory has in-place a fail-over mechanism whose job is to cope with those errors and hopefully make them disappear.
> If the fail-over succeeds, the user should not see any ERROR-level logging. At most, there should be a WARN along the lines of "node failure detected, the fail-over mechanism is dealing with it". The user should see ERRORs only if the fail-over itself fails.
> Tons of stack traces produce a significant level of discomfort even if the fail-over succeeds, leaving the user in doubt whether actually the process worked.
> The logging information should be naturally still available, but at DEBUG level.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list