You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2008/07/22 18:49:31 UTC

[jira] Created: (QPID-1187) Java Broker apears to be stuck in a loop

Java Broker apears to be stuck in a loop
----------------------------------------

                 Key: QPID-1187
                 URL: https://issues.apache.org/jira/browse/QPID-1187
             Project: Qpid
          Issue Type: Bug
          Components: Java Broker
    Affects Versions: M3
            Reporter: Martin Ritchie
             Fix For: M3


Summary:

>From a Java Cruise Control run on a slow machine (20080722122553) the FlowControlTest.testBasicBytesFlowControl  failed as an expected message was not received.

However the log file was filled with over 100k entries of this:
pool-6-thread-1 2008-07-22 12:28:14,956 DEBUG [qpid.server.subscription.SubscriptionImpl] (15575005) checking filters for message ((HC:10486941 ID:3 Ref:1)

This appears to be a transient error as it does not fail on every test run. 

The log file does show a second thread taking over the logging right before it fails. 

The logging does not provide complete coverage of the threads activities as it shows the thread delivering the message to the client then it starts the 'checking filters' loop.

Log Attached

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (QPID-1187) Java Broker appears to be stuck in a loop

Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Ritchie updated QPID-1187:
---------------------------------

    Summary: Java Broker appears to be stuck in a loop  (was: Java Broker apears to be stuck in a loop)

> Java Broker appears to be stuck in a loop
> -----------------------------------------
>
>                 Key: QPID-1187
>                 URL: https://issues.apache.org/jira/browse/QPID-1187
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: M3
>            Reporter: Martin Ritchie
>             Fix For: M3
>
>         Attachments: TEST-org.apache.qpid.test.client.FlowControlTest.testBasicBytesFlowControl.out.short.txt
>
>
> Summary:
> From a Java Cruise Control run on a slow machine (20080722122553) the FlowControlTest.testBasicBytesFlowControl  failed as an expected message was not received.
> However the log file was filled with over 100k entries of this:
> pool-6-thread-1 2008-07-22 12:28:14,956 DEBUG [qpid.server.subscription.SubscriptionImpl] (15575005) checking filters for message ((HC:10486941 ID:3 Ref:1)
> This appears to be a transient error as it does not fail on every test run. 
> The log file does show a second thread taking over the logging right before it fails. 
> The logging does not provide complete coverage of the threads activities as it shows the thread delivering the message to the client then it starts the 'checking filters' loop.
> Log Attached

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (QPID-1187) Java Broker appears to be stuck in a loop

Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Ritchie updated QPID-1187:
---------------------------------

    Status: Ready To Review  (was: In Progress)

> Java Broker appears to be stuck in a loop
> -----------------------------------------
>
>                 Key: QPID-1187
>                 URL: https://issues.apache.org/jira/browse/QPID-1187
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: M3
>            Reporter: Martin Ritchie
>            Assignee: Martin Ritchie
>             Fix For: M4
>
>         Attachments: TEST-org.apache.qpid.test.client.FlowControlTest.testBasicBytesFlowControl.out.short.txt
>
>
> Summary:
> From a Java Cruise Control run on a slow machine (20080722122553) the FlowControlTest.testBasicBytesFlowControl  failed as an expected message was not received.
> However the log file was filled with over 100k entries of this:
> pool-6-thread-1 2008-07-22 12:28:14,956 DEBUG [qpid.server.subscription.SubscriptionImpl] (15575005) checking filters for message ((HC:10486941 ID:3 Ref:1)
> This appears to be a transient error as it does not fail on every test run. 
> The log file does show a second thread taking over the logging right before it fails. 
> The logging does not provide complete coverage of the threads activities as it shows the thread delivering the message to the client then it starts the 'checking filters' loop.
> Log Attached

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (QPID-1187) Java Broker appears to be stuck in a loop

Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
    [ https://issues.apache.org/jira/browse/QPID-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615983#action_12615983 ] 

Martin Ritchie commented on QPID-1187:
--------------------------------------

A more rigorous test is required for the provided fix to the issue.

> Java Broker appears to be stuck in a loop
> -----------------------------------------
>
>                 Key: QPID-1187
>                 URL: https://issues.apache.org/jira/browse/QPID-1187
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: M3
>            Reporter: Martin Ritchie
>            Assignee: Martin Ritchie
>             Fix For: M3
>
>         Attachments: TEST-org.apache.qpid.test.client.FlowControlTest.testBasicBytesFlowControl.out.short.txt
>
>
> Summary:
> From a Java Cruise Control run on a slow machine (20080722122553) the FlowControlTest.testBasicBytesFlowControl  failed as an expected message was not received.
> However the log file was filled with over 100k entries of this:
> pool-6-thread-1 2008-07-22 12:28:14,956 DEBUG [qpid.server.subscription.SubscriptionImpl] (15575005) checking filters for message ((HC:10486941 ID:3 Ref:1)
> This appears to be a transient error as it does not fail on every test run. 
> The log file does show a second thread taking over the logging right before it fails. 
> The logging does not provide complete coverage of the threads activities as it shows the thread delivering the message to the client then it starts the 'checking filters' loop.
> Log Attached

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (QPID-1187) Java Broker appears to be stuck in a loop

Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Ritchie reassigned QPID-1187:
------------------------------------

    Assignee: Rob Godfrey  (was: Martin Ritchie)

Hi Rob,

Can you review this patch we discussed around bytes flow control.

I'm concerned that we are still seeing failures from the FlowControlTest.

Any thoughts? Was this patch not enough?

> Java Broker appears to be stuck in a loop
> -----------------------------------------
>
>                 Key: QPID-1187
>                 URL: https://issues.apache.org/jira/browse/QPID-1187
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: M3
>            Reporter: Martin Ritchie
>            Assignee: Rob Godfrey
>             Fix For: M4
>
>         Attachments: TEST-org.apache.qpid.test.client.FlowControlTest.testBasicBytesFlowControl.out.short.txt
>
>
> Summary:
> From a Java Cruise Control run on a slow machine (20080722122553) the FlowControlTest.testBasicBytesFlowControl  failed as an expected message was not received.
> However the log file was filled with over 100k entries of this:
> pool-6-thread-1 2008-07-22 12:28:14,956 DEBUG [qpid.server.subscription.SubscriptionImpl] (15575005) checking filters for message ((HC:10486941 ID:3 Ref:1)
> This appears to be a transient error as it does not fail on every test run. 
> The log file does show a second thread taking over the logging right before it fails. 
> The logging does not provide complete coverage of the threads activities as it shows the thread delivering the message to the client then it starts the 'checking filters' loop.
> Log Attached

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (QPID-1187) Java Broker appears to be stuck in a loop

Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Ritchie reassigned QPID-1187:
------------------------------------

    Assignee: Martin Ritchie

> Java Broker appears to be stuck in a loop
> -----------------------------------------
>
>                 Key: QPID-1187
>                 URL: https://issues.apache.org/jira/browse/QPID-1187
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: M3
>            Reporter: Martin Ritchie
>            Assignee: Martin Ritchie
>             Fix For: M3
>
>         Attachments: TEST-org.apache.qpid.test.client.FlowControlTest.testBasicBytesFlowControl.out.short.txt
>
>
> Summary:
> From a Java Cruise Control run on a slow machine (20080722122553) the FlowControlTest.testBasicBytesFlowControl  failed as an expected message was not received.
> However the log file was filled with over 100k entries of this:
> pool-6-thread-1 2008-07-22 12:28:14,956 DEBUG [qpid.server.subscription.SubscriptionImpl] (15575005) checking filters for message ((HC:10486941 ID:3 Ref:1)
> This appears to be a transient error as it does not fail on every test run. 
> The log file does show a second thread taking over the logging right before it fails. 
> The logging does not provide complete coverage of the threads activities as it shows the thread delivering the message to the client then it starts the 'checking filters' loop.
> Log Attached

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (QPID-1187) Java Broker apears to be stuck in a loop

Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Ritchie updated QPID-1187:
---------------------------------

    Attachment: TEST-org.apache.qpid.test.client.FlowControlTest.testBasicBytesFlowControl.out.short.txt

> Java Broker apears to be stuck in a loop
> ----------------------------------------
>
>                 Key: QPID-1187
>                 URL: https://issues.apache.org/jira/browse/QPID-1187
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: M3
>            Reporter: Martin Ritchie
>             Fix For: M3
>
>         Attachments: TEST-org.apache.qpid.test.client.FlowControlTest.testBasicBytesFlowControl.out.short.txt
>
>
> Summary:
> From a Java Cruise Control run on a slow machine (20080722122553) the FlowControlTest.testBasicBytesFlowControl  failed as an expected message was not received.
> However the log file was filled with over 100k entries of this:
> pool-6-thread-1 2008-07-22 12:28:14,956 DEBUG [qpid.server.subscription.SubscriptionImpl] (15575005) checking filters for message ((HC:10486941 ID:3 Ref:1)
> This appears to be a transient error as it does not fail on every test run. 
> The log file does show a second thread taking over the logging right before it fails. 
> The logging does not provide complete coverage of the threads activities as it shows the thread delivering the message to the client then it starts the 'checking filters' loop.
> Log Attached

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (QPID-1187) Java Broker appears to be stuck in a loop

Posted by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Godfrey resolved QPID-1187.
-------------------------------

    Resolution: Fixed

> Java Broker appears to be stuck in a loop
> -----------------------------------------
>
>                 Key: QPID-1187
>                 URL: https://issues.apache.org/jira/browse/QPID-1187
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: M3
>            Reporter: Martin Ritchie
>            Assignee: Rob Godfrey
>             Fix For: M4
>
>         Attachments: TEST-org.apache.qpid.test.client.FlowControlTest.testBasicBytesFlowControl.out.short.txt
>
>
> Summary:
> From a Java Cruise Control run on a slow machine (20080722122553) the FlowControlTest.testBasicBytesFlowControl  failed as an expected message was not received.
> However the log file was filled with over 100k entries of this:
> pool-6-thread-1 2008-07-22 12:28:14,956 DEBUG [qpid.server.subscription.SubscriptionImpl] (15575005) checking filters for message ((HC:10486941 ID:3 Ref:1)
> This appears to be a transient error as it does not fail on every test run. 
> The log file does show a second thread taking over the logging right before it fails. 
> The logging does not provide complete coverage of the threads activities as it shows the thread delivering the message to the client then it starts the 'checking filters' loop.
> Log Attached

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.