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.