It should be possible to either develop such a component in-house or to hire 
somebody to develop the component for you.

--emi 

> On 27 Sep 2017, at 20:13, hiren.pa...@intellectdesign.com wrote:
> 
> Hi, This option is evaluated. Thanks for sharing.
> 
> However, it doesn't help, bcos if we have 10 test cases for example, we 
> will still need 10 * 2 components (JMS + RabbitMQ) configured and 
> maintained. And we are expecting hundreds!
> 
> What is desired is single component where we specify:
> - Broker = JMS / RabbitMQ
> - Connection Factory = JMS one or RMQ one
> - Queue configuration = JMS one of RMQ one
> 
> And with all above as JMeter variables, we could very well just have one 
> single component configured to switch between ActiveMQ and RabbitMQ as and 
> when required.
> 
> Too wishful? :-)
> 
> Regards,
> Hiren
> 
> 
> 
> 
> 
> From:   Antonio Gomes Rodrigues <ra0...@gmail.com>
> To:     JMeter Users List <u...@jmeter.apache.org>
> Cc:     "JMeter Dev@" <dev@jmeter.apache.org>
> Date:   27-09-2017 10:30 PM
> Subject:        Re: JMeter - Common JMS/RabbitMQ component
> 
> 
> 
> Try with a variable pass to JMeter and use a IF to choose the right 
> sampler
> 
> Le 27 sept. 2017 18:40, <hiren.pa...@intellectdesign.com> a écrit :
> 
>> Yes, using the same RabbitMQ plugin you mentioned.
>> 
>> Was hoping for some component already out there supporting both
>> protocol's.
>> 
>> Nevertheless, if there is a need to create new plugin, where should I 
> look
>> for relevant guide?
>> 
>> Thanks,
>> Hiren
>> 
>> 
>> 
>> 
>> 
>> From:   Emilian Bold <emilian.b...@gmail.com>
>> To:     JMeter Users List <u...@jmeter.apache.org>
>> Cc:     "JMeter Dev@" <dev@jmeter.apache.org>
>> Date:   27-09-2017 09:57 PM
>> Subject:        Re: JMeter - Common JMS/RabbitMQ component
>> 
>> 
>> 
>> I imagine that for AMQP you use a 3rd party plugin like
>> https://github.com/
>> jlavallee/JMeter-Rabbit-AMQP ?
>> 
>> I guess it might be possible to create a custom plugin to bridge towards
>> those two underlying.
>> 
>> 
>> --emi
>> 
>> On Wed, Sep 27, 2017 at 7:00 PM, <hiren.pa...@intellectdesign.com> 
> wrote:
>> 
>>> Hi,
>>> 
>>> As part of our Integration Test Automation process, we have been
>> actively
>>> using Apache JMeter tool.
>>> 
>>> Some part of test automation needs Asynchronous Message
>>> Publisher/Subscriber. We have both ActiveMQ (JMS) and RabbitMQ brokers
>> to
>>> be supported in integration tests.
>>> 
>>> What we see is JMeter:
>>> 
>>>   - uses *JMS *Point-to-Point/ Publisher/ Subscriber for *ActiveMQ *
>>>   communication.
>>>   - and needs *AMQP *Publisher/ Consumer for *RabbitMQ* 
> communication.
>>> 
>>> 
>>> This works well in isolation. However, problem is when we want to 
> switch
>>> between RabbitMQ and ActiveMQ broker, depending on what environment we
>> are
>>> testing with (e.g. Dev, Test, QA etc).
>>> 
>>> Problem is we have to maintain completely two different Test Suite:
>>> 
>>>   - one with AMQP components (for RabbitMQ)
>>>   - another one with JMS components (for ActiveMQ)
>>> 
>>> 
>>> *Is there a way in JMeter *by which we use some common
>> publisher/consumer
>>> that can support both RabbitMQ and ActiveMQ, without us having to
>> maintain
>>> two different Test Suite? So that we can anytime switch between the
>> brokers.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> Thanks,
>>> Hiren
>>> 
>>> 
>>> 
>>> 
>>> 
>>> *------------------------------ This e-Mail may contain proprietary 
> and
>>> confidential information and is sent for the intended recipient(s) 
> only.
>> If
>>> by an addressing or transmission error this mail has been misdirected 
> to
>>> you, you are requested to delete this mail immediately. You are also
>> hereby
>>> notified that any use, any form of reproduction, dissemination, 
> copying,
>>> disclosure, modification, distribution and/or publication of this 
> e-mail
>>> message, contents or its attachment other than by its intended
>> recipient/s
>>> is strictly prohibited. Visit us at http://www.intellectdesign.com
>>> <http://www.intellectdesign.com> ------------------------------*
>> 
>> 
> 

Reply via email to