[ 
https://issues.apache.org/jira/browse/QPID-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14998590#comment-14998590
 ] 

ASF subversion and git services commented on QPID-6833:
-------------------------------------------------------

Commit 1713635 from [~lorenz.quack] in branch 'java/trunk'
[ https://svn.apache.org/r1713635 ]

QPID-6833: [Java Broker] When adding a ticker wakeup the connection to ensure 
the ticker is taken into account

> [Java Broker] Operational log message  SUB-1003  is not logged by 
> SuspendedConsumerLoggingTicker causing failures of 
> ConsumerLoggingTest#testSubscriptionSuspend
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-6833
>                 URL: https://issues.apache.org/jira/browse/QPID-6833
>             Project: Qpid
>          Issue Type: Bug
>    Affects Versions: qpid-java-6.0
>            Reporter: Alex Rudyy
>            Priority: Critical
>
> Operational log message  "SUB-1003 : Suspended for {0,number} ms" is not 
> logged by SuspendedConsumerLoggingTicker causing failures of 
> ConsumerLoggingTest#testSubscriptionSuspen
> {noformat}
> junit.framework.AssertionFailedError: Expected at least two suspension 
> messages, but got 1
>       at junit.framework.Assert.fail(Assert.java:57)
>       at junit.framework.Assert.assertTrue(Assert.java:22)
>       at junit.framework.TestCase.assertTrue(TestCase.java:192)
>       at 
> org.apache.qpid.server.logging.ConsumerLoggingTest.testSubscriptionSuspend(ConsumerLoggingTest.java:328)
> {noformat}
> It appear that QueueConsumerImpl anonymous implementation of 
> SuspendedConsumerLoggingTicker is not called all the time to issue 
> operational log message



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to