You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "clebert suconic (Jira)" <ji...@apache.org> on 2019/08/26 15:29:02 UTC

[jira] [Closed] (ARTEMIS-2385) Log header for rejecting message with too large header

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

clebert suconic closed ARTEMIS-2385.
------------------------------------

> 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
>             Fix For: 2.10.0
>
>          Time Spent: 1.5h
>  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
(v8.3.2#803003)