[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] [Commented] (AMQ-5301) Destination should not have numerical suffix for single-dest perf test
From:       "ASF GitHub Bot (JIRA)" <jira () apache ! org>
Date:       2014-07-31 17:37:39
Message-ID: JIRA.12731081.1406818858558.88008.1406828259941 () arcas
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/AMQ-5301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14081169#comment-14081169 \
] 

ASF GitHub Bot commented on AMQ-5301:
-------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/activemq/pull/38


> Destination should not have numerical suffix for single-dest perf tests
> -----------------------------------------------------------------------
> 
> Key: AMQ-5301
> URL: https://issues.apache.org/jira/browse/AMQ-5301
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Performance Test
> Affects Versions: 5.10.0
> Reporter: Jakub Korab
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 5.11.0
> 
> 
> The performance test module assumes that multiple destinations will be put under \
> load, and thereby assigns a numerical suffix to the destination name specified on \
> the command line. Thus a producer/consumer configured to topic://foo will actually \
> send/receive from topic://foo.0. This is annoying, as when load testing a \
> particular broker setup (such as with composite destinations), you need to be \
> explicit about which destination is being targeted and it is not always possible to \
> tweak the broker configuration. I propose that for single-destination tests, no \
> numerical suffix is added. Patch incoming.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[prev in list] [next in list] [prev in thread] [next in thread]