Bug 53833 - Enable using the same ConnectionFactory for Multiple threads while posting JMS messages
Summary: Enable using the same ConnectionFactory for Multiple threads while posting JM...
Status: NEW
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: 2.7
Hardware: All All
: P1 enhancement with 3 votes (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
: 61378 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-09-05 18:49 UTC by Philippe Mouawad
Modified: 2019-03-04 10:24 UTC (History)
5 users (show)


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe Mouawad 2012-09-05 18:49:10 UTC 
The Jmeter at present creates a new QueueConnection for each of the thread (as per the number of threads provided).

Usually when testing one application calling one broker, applications will pool Connection or share Connection using rather one Session per thread.

It would be useful to allow sharing Connection among threads + add an option to allow pooling connections.

See:
http://stackoverflow.com/questions/12280475/jmeter-use-the-same-connectionfactory-for-multiple-threads-while-posting-jms-me
Comment 1 tsvbuzuluk 2014-01-22 08:49:59 UTC 
When I test application using  JMS Point-to-Point Sampler Jmeter creates too much connections and WebSphere MQ is crashed. I think JMeter can use pool Connection. Does this is planned change? 

P.S. I apologize for the my language.
Comment 2 Philippe Mouawad 2017-08-27 13:05:15 UTC 
*** Bug 61378 has been marked as a duplicate of this bug. ***
Comment 3 The ASF infrastructure team 2022-09-24 20:37:51 UTC 
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2914