activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <>
Subject [jira] [Updated] (APLO-7) better logging messages
Date Fri, 13 May 2011 16:14:47 GMT


Hiram Chirino updated APLO-7:

          Component/s: apollo-broker
    Affects Version/s: 1.0-beta1
        Fix Version/s: 1.0-beta2

> better logging messages
> -----------------------
>                 Key: APLO-7
>                 URL:
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-broker
>    Affects Versions: 1.0-beta1
>            Reporter: Hiram Chirino
>            Assignee: Hiram Chirino
>             Fix For: 1.0-beta2
> {quote}
> I'm trying the latest Apollo snapshot and I see in the logs:
>  2011-04-21 08:16:12,536 connected: /
> Could you please add the local port number too?
> This is especially useful in case of failures. I got:
>  2011-04-21 08:14:16,970 authentication failed. address:/, reason:No associated
> After investigation, it was the tcp port (and not the ssl port) so it
> was not at all related to certificates. A message such as "invalid
> user name or password" would be much better.
> Also, like for, it would
> be useful to get the user name in case of authentication failures.
> Finally, to make the log parsers' life easier, it would be really nice
> to use a standard format for the messages. For instance something like:
>  connected: local: remote:
>  authentication failed: local: remote: reason:"invalid
user name or password" user:guesst
> FWIW, the "local" address could be useful in case of multihomed servers.
> If you don't want to bother about how to format key/value pairs, maybe
> you could use log4j's MDC?
> Cheers,
> Lionel
> {quote}

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message