camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Babak Vahdat (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-6942) itest - JmsMediumQueuePerformanceTest - Look into itest that takes a long time
Date Wed, 06 Nov 2013 20:57:17 GMT

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

Babak Vahdat commented on CAMEL-6942:
-------------------------------------

The root cause of the problem is that there's no usage of JMS connection pooling as we produce
the JMS messages up front through {{template}}. In case of {{JmsPerformanceTest}} there are
100 messages being produced and in case of it's subclass {{JmsMediumQueuePerformanceTest}}
it is 1000!

> itest - JmsMediumQueuePerformanceTest - Look into itest that takes a long time
> ------------------------------------------------------------------------------
>
>                 Key: CAMEL-6942
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6942
>             Project: Camel
>          Issue Type: Test
>          Components: tests
>    Affects Versions: 2.13.0
>            Reporter: Claus Ibsen
>            Assignee: Babak Vahdat
>            Priority: Minor
>
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 310.62 sec - in org.apache.camel.itest.jms.JmsMediumQueuePerformanceTest
> A potential issue here with a test that shouldn't take 300 sec. normally



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message