You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2014/07/25 15:12:28 UTC
[Bug 56773] New: Unable to capture the responses from the JMS queue
after publishing JMS messages to the Request queue
https://issues.apache.org/bugzilla/show_bug.cgi?id=56773
Bug ID: 56773
Summary: Unable to capture the responses from the JMS queue
after publishing JMS messages to the Request queue
Product: JMeter
Version: 2.11
Hardware: PC
Status: NEW
Severity: blocker
Priority: P2
Component: Main
Assignee: issues@jmeter.apache.org
Reporter: sutapa_sarkar@infosys.com
I am trying to do a load testing for TIBCO EMS middleware by publishing
messages to the JMS queue using JMeter.The messages get published successfully
to the queue.However I am unable to capture the response.I have added the
correct Response queue name in the Subscriber as well as in the
Properties(added a property called "JMSReplyTo" with value as the name of the
Reply queue.
However the no response is received.When checked in the EMS server the messages
do have null value for the "JMSReplyTo"string and hence not able to find the
Response queue and timing out.
Request you to please suggest a solution for this as I am very new to Web
Services testing.
Thanks and Regards,
Sutapa Sarkar
+31616173171
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 56773] Unable to capture the responses from the JMS queue after
publishing JMS messages to the Request queue
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=56773
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |p.mouawad@ubik-ingenierie.c
| |om
Resolution|--- |INVALID
OS| |All
--- Comment #1 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
Bugzilla is not a support forum, please ask first on User Mailing list giving
as much details as possible.
--
You are receiving this mail because:
You are the assignee for the bug.