You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Hadrian Zbarcea (JIRA)" <ji...@apache.org> on 2008/11/07 16:27:52 UTC

[jira] Created: (CAMEL-1062) PipelineConcurrentTest.java fails randomly

PipelineConcurrentTest.java fails randomly
------------------------------------------

                 Key: CAMEL-1062
                 URL: https://issues.apache.org/activemq/browse/CAMEL-1062
             Project: Apache Camel
          Issue Type: Bug
          Components: camel-core
    Affects Versions: 1.5.0
            Reporter: Hadrian Zbarcea
            Assignee: Hadrian Zbarcea
            Priority: Minor


The test fails with an IllegalStateException: Queue full.  I believe the reason for this is that there are 10000 messages sent, but the default queue size is 1000.   On a fast machine, the queue fills up before the consumer gets a chance to pop the messages from the queue.


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


[jira] Resolved: (CAMEL-1062) PipelineConcurrentTest.java fails randomly

Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hadrian Zbarcea resolved CAMEL-1062.
------------------------------------

    Fix Version/s: 1.5.1
                   2.0.0
       Resolution: Fixed

> PipelineConcurrentTest.java fails randomly
> ------------------------------------------
>
>                 Key: CAMEL-1062
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1062
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 1.5.0
>            Reporter: Hadrian Zbarcea
>            Assignee: Hadrian Zbarcea
>            Priority: Minor
>             Fix For: 1.5.1, 2.0.0
>
>
> The test fails with an IllegalStateException: Queue full.  I believe the reason for this is that there are 10000 messages sent, but the default queue size is 1000.   On a fast machine, the queue fills up before the consumer gets a chance to pop the messages from the queue.

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