[
https://issues.apache.org/jira/browse/QPID-8715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18045103#comment-18045103
]
ASF GitHub Bot commented on QPID-8715:
--------------------------------------
dakirily opened a new pull request, #356:
URL: https://github.com/apache/qpid-broker-j/pull/356
This PR addresses JIRA
[QPID-8715](https://issues.apache.org/jira/browse/QPID-8715), updating netty
dependencies to version 4.2.8.Final
> [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-10.0.2
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
