You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2020/11/23 05:31:00 UTC

[jira] [Updated] (AMQ-7443) Prefetch warnings should include client IP information

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

Jean-Baptiste Onofré updated AMQ-7443:
--------------------------------------
    Fix Version/s:     (was: 5.15.14)
                   5.15.15

> Prefetch warnings should include client IP information
> ------------------------------------------------------
>
>                 Key: AMQ-7443
>                 URL: https://issues.apache.org/jira/browse/AMQ-7443
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.15.12
>            Reporter: Lionel Cons
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>             Fix For: 5.16.1, 5.15.15
>
>
> In ActiveMQ up to 5.15.12, prefetch warnings look like this:
> {code}
> 2020-03-18 09:25:07,892 [ActiveMQ NIO Worker 7] WARN TopicSubscription - TopicSubscription: consumer=ID:foo.acme.com-7195-1584519807454-1:61:-1:1, destinations=1, dispatched=563, delivered=897, matched=564, discarded=0, prefetchExtension=0, usePrefetchExtension=true: has twice its prefetch limit pending, without an ack; it appears to be slow
> {code}
> This is not enough to find the culprit client (after the fact). ActiveMQ should (also) log the client IP address (and port). It should ideally be similar to other warnings like:
> {code}
> 2020-03-18 09:18:31,539 [ActiveMQ InactivityMonitor Worker] WARN Transport - Transport Connection to: tcp://192.1.1.1:51550 failed: org.apache.activemq.transport.InactivityIOException: Channel was inactive for too (>7500) long: tcp://192.1.1.1:51550
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)