You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/01/13 05:26:00 UTC
[jira] [Work logged] (AMQ-7443) Prefetch warnings should include
client IP information
[ https://issues.apache.org/jira/browse/AMQ-7443?focusedWorklogId=535206&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-535206 ]
ASF GitHub Bot logged work on AMQ-7443:
---------------------------------------
Author: ASF GitHub Bot
Created on: 13/Jan/21 05:25
Start Date: 13/Jan/21 05:25
Worklog Time Spent: 10m
Work Description: jbonofre opened a new pull request #610:
URL: https://github.com/apache/activemq/pull/610
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 535206)
Remaining Estimate: 0h
Time Spent: 10m
> Prefetch warnings should include client IP information
> ------------------------------------------------------
>
> Key: AMQ-7443
> URL: https://issues.apache.org/jira/browse/AMQ-7443
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, Transport
> Affects Versions: 5.15.12
> Reporter: Lionel Cons
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 5.16.1, 5.15.15
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)