[
https://issues.apache.org/jira/browse/ARTEMIS-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16867792#comment-16867792
]
ASF subversion and git services commented on ARTEMIS-2385:
----------------------------------------------------------
Commit 9d12ad6501b6f9ef2ac1556b419b5cfe920530cf in activemq-artemis's branch
refs/heads/master from brusdev
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=9d12ad6 ]
ARTEMIS-2385 Log header for rejecting message with too large header
Use warning level to add in the log the ID and debug level to add in the
log the message header of rejecting message with too large header.
> Log header for rejecting message with too large header
> ------------------------------------------------------
>
> Key: ARTEMIS-2385
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2385
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Domenico Bruscino
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The usage scenario I am thinking about; broker admins see many of these
> rejections but no way to trace it back to the application that is sending the
> offending message(s) to the broker. I have seen this scenario a few times,
> where broker admins had issues identifying which applications were
> responsible for these messages; so any data to help identify the offending
> message would be very useful.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
