[jira] [Updated] (QPID-8715) [Broker-J] Http Management - Exception stack trace in logs

["Tomas Vavricka (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/QPID-8715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomas Vavricka updated QPID-8715:
---------------------------------
    Fix Version/s: qpid-java-broker-11.0.0
                       (was: qpid-java-broker-10.0.2)

> [Broker-J] Http Management - Exception stack trace in logs
> ----------------------------------------------------------
>
>                 Key: QPID-8715
>                 URL: https://issues.apache.org/jira/browse/QPID-8715
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Broker-J
>    Affects Versions: qpid-java-broker-9.2.1
>            Reporter: Kyrre
>            Priority: Minor
>             Fix For: qpid-java-broker-11.0.0
>
>         Attachments: group_member_exception.txt
>
>
> When trying to do a GET against the HTTP management interface to check for the existence of a certain group member, the attached stack trace pops up in the logs. This adds a lot of noise to the logs. I suggest making a structured log entry with the URL that is not found, or removed entirely
> Assuming there exists a group called 'my-group', performing a GET request against the management API url '/api/latest/groupmember/default/my-group/non-existing' results in the log entry attached-



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org