You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <ji...@apache.org> on 2015/06/16 23:51:01 UTC
[jira] [Assigned] (QPID-6575) Log subscription state change message
(SUB-1003) only when a subscription has been suspended for an unusally long
period of time
[ https://issues.apache.org/jira/browse/QPID-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Godfrey reassigned QPID-6575:
---------------------------------
Assignee: Rob Godfrey
> Log subscription state change message (SUB-1003) only when a subscription has been suspended for an unusally long period of time
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-6575
> URL: https://issues.apache.org/jira/browse/QPID-6575
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Assignee: Rob Godfrey
> Fix For: 6.0 [Java]
>
>
> SUB-1003 is logged currently whenever a subscription changes state i.e. as the client session/consumer is able to accept more messages. With some use-cases (low prefetch) and some messaging stacks (Sping's DMLC) this can be very frequent. Indeed, with Spring in certain configurations, this will lead to a pair of messages per message. For this reason, we turn off SUB-1003 in the log4j configuration. In v6, we have killed the log4j configuration so SUB-1003 is being logged again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org