You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by João Tiago Ferreira <jo...@novabase.pt> on 2010/06/17 13:08:29 UTC
Jmeter JMS support for Tibco EMS
Hi
I am using jmeter to perform some functional tests in our application. I need to send a request for the JMS server and wait for a response.
Our use case for the the use of correlation and message ids is that the messageID of the request is used to set the correlationID of the response.
Using jmeter JMS request response the correlation is not working as expected, neither in 2.3.4 or nightly builds.
I send the logs as attachments.
As far as I can understand the JMS Sampler is using the messageID of the response to match the messageID of the request, while it should use the correlationID of the response.
I easily modified the source to fit my needs, but wanted to contribute my testing with Tibco EMS. I also noted that several bug reports exist about this issue...
Thanks for this great tool
Best regards
João Ferreira
Re: Jmeter JMS support for Tibco EMS
Posted by sebb <se...@gmail.com>.
On 18/06/2010, João Tiago Ferreira <jo...@novabase.pt> wrote:
>
>
> > -----Original Message-----
> > From: sebb [mailto:sebbaz@gmail.com]
>
> > Sent: sexta-feira, 18 de Junho de 2010 11:57
> > To: JMeter Users List
> > Subject: Re: Jmeter JMS support for Tibco EMS
> >
>
> > On 18/06/2010, João Tiago Ferreira <jo...@novabase.pt>
> > wrote:
> > > Hi. I dont think there are so many use cases.
> > >
> > > First point is the sender of the message can't set the messageId. It
> > is an identifier of the message generated by the JMS provider.
> >
> > I know.
> >
> > > Moreover two different messages can't have the same messageID, so I
> > would say comparing "request:messageId == reply:messageId" makes no
> > sense.
> >
> > It *can* make sense in "echo" mode:
> >
> > The sampler can send to a queue and then receive the original message
> > from the same queue. Could be useful for checking queue throughput.
> >
> > In that case, *if* the correlationID is present of course one could
> > use that instead.
> >
> > > Here is a nice explanation of the different JMS request response
> > patterns [1].
> >
> > Does not work for me - I get an empty page.
>
>
> http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/interopjms/MsgIDPatternforJMS.html
>
>
> or search for "Understanding Message ID and Correlation ID Patterns for JMS Request/Response"
Of course, after I e-mailed, it just started working...
>
> >
> > > So when you check the option "Use Request Message Id As Correlation
> > Id" we are using the "JMS Message ID Pattern" where no correlationId is
> > necessary to set in the request and in the receiver we should check for
> > request:messageId == reply:correlationId instead of "request:messageId
> > == reply:messageId"
> >
> > That relies on the response correlation ID being set to the request
> > message ID - which does not happen automatically, as far as I can
> > tell.
> >
> > > When you uncheck the "Use Request Message Id As Correlation Id" we
> > are using the "JMS Correlation ID Pattern" and is necessary to set the
> > correlatioId in the request and in the receiver we should check for
> > "request:correlationId == reply:correlationId" as is implemented now.
> >
> > The service has to copy the correlationId from request to response.
> >
> > Your use cases both rely on checking the response correlationId which
> > it is assumed will be set from either the request correlationId or the
> > requestMessageId.
> >
> > The person who raised the original Bug 46142 reported that the
> > correlationId was null for JBoss, and the cited message thread says
> > that the same problem happens with Weblogic.
> >
> > If the JMeter receiver only looks at the response correlationId, it
> > seems this will cause problems for JBoss and Weblogic.
> >
> > So I think it is necessary to make the request and response fields
> > independently selectable. I don't think on can satisfy everyone
> > without.
> >
> > I've already done much of the work for this; it seems to work OK for
> > ActiveMQ in "echo" mode at least.
> >
> > > Note: when I say "receiver" I mean the client side receiver, i.e the
> > Jmeter receiver...
> > >
> > > Thanks for support
> > >
> > > João Ferreira
> > >
> > >
> > > [1]
> > http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/interopjms/M
> > sgIDPatternforJMS.html
> > >
> >
>
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
RE: Jmeter JMS support for Tibco EMS
Posted by João Tiago Ferreira <jo...@novabase.pt>.
> -----Original Message-----
> From: sebb [mailto:sebbaz@gmail.com]
> Sent: sexta-feira, 18 de Junho de 2010 11:57
> To: JMeter Users List
> Subject: Re: Jmeter JMS support for Tibco EMS
>
> On 18/06/2010, João Tiago Ferreira <jo...@novabase.pt>
> wrote:
> > Hi. I dont think there are so many use cases.
> >
> > First point is the sender of the message can't set the messageId. It
> is an identifier of the message generated by the JMS provider.
>
> I know.
>
> > Moreover two different messages can't have the same messageID, so I
> would say comparing "request:messageId == reply:messageId" makes no
> sense.
>
> It *can* make sense in "echo" mode:
>
> The sampler can send to a queue and then receive the original message
> from the same queue. Could be useful for checking queue throughput.
>
> In that case, *if* the correlationID is present of course one could
> use that instead.
>
> > Here is a nice explanation of the different JMS request response
> patterns [1].
>
> Does not work for me - I get an empty page.
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/interopjms/MsgIDPatternforJMS.html
or search for "Understanding Message ID and Correlation ID Patterns for JMS Request/Response"
>
> > So when you check the option "Use Request Message Id As Correlation
> Id" we are using the "JMS Message ID Pattern" where no correlationId is
> necessary to set in the request and in the receiver we should check for
> request:messageId == reply:correlationId instead of "request:messageId
> == reply:messageId"
>
> That relies on the response correlation ID being set to the request
> message ID - which does not happen automatically, as far as I can
> tell.
>
> > When you uncheck the "Use Request Message Id As Correlation Id" we
> are using the "JMS Correlation ID Pattern" and is necessary to set the
> correlatioId in the request and in the receiver we should check for
> "request:correlationId == reply:correlationId" as is implemented now.
>
> The service has to copy the correlationId from request to response.
>
> Your use cases both rely on checking the response correlationId which
> it is assumed will be set from either the request correlationId or the
> requestMessageId.
>
> The person who raised the original Bug 46142 reported that the
> correlationId was null for JBoss, and the cited message thread says
> that the same problem happens with Weblogic.
>
> If the JMeter receiver only looks at the response correlationId, it
> seems this will cause problems for JBoss and Weblogic.
>
> So I think it is necessary to make the request and response fields
> independently selectable. I don't think on can satisfy everyone
> without.
>
> I've already done much of the work for this; it seems to work OK for
> ActiveMQ in "echo" mode at least.
>
> > Note: when I say "receiver" I mean the client side receiver, i.e the
> Jmeter receiver...
> >
> > Thanks for support
> >
> > João Ferreira
> >
> >
> > [1]
> http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/interopjms/M
> sgIDPatternforJMS.html
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
RE: Jmeter JMS support for Tibco EMS
Posted by João Tiago Ferreira <jo...@novabase.pt>.
> -----Original Message-----
> From: sebb [mailto:sebbaz@gmail.com]
> Sent: sexta-feira, 18 de Junho de 2010 11:57
> To: JMeter Users List
> Subject: Re: Jmeter JMS support for Tibco EMS
>
> On 18/06/2010, João Tiago Ferreira <jo...@novabase.pt>
> wrote:
> > Hi. I dont think there are so many use cases.
> >
> > First point is the sender of the message can't set the messageId. It
> is an identifier of the message generated by the JMS provider.
>
> I know.
>
> > Moreover two different messages can't have the same messageID, so I
> would say comparing "request:messageId == reply:messageId" makes no
> sense.
>
> It *can* make sense in "echo" mode:
>
> The sampler can send to a queue and then receive the original message
> from the same queue. Could be useful for checking queue throughput.
>
> In that case, *if* the correlationID is present of course one could
> use that instead.
Why not a different jms sampler for the "echo" mode?
We could have this "request-response" sampler to simulate a client that sends a request and is expecting the response from the application being tested.
And another sampler that would allow that "echo" mode to test throughput by comparing request.messageID == reply.messageID,
>
> > Here is a nice explanation of the different JMS request response
> patterns [1].
>
> Does not work for me - I get an empty page.
>
> > So when you check the option "Use Request Message Id As Correlation
> Id" we are using the "JMS Message ID Pattern" where no correlationId is
> necessary to set in the request and in the receiver we should check for
> request:messageId == reply:correlationId instead of "request:messageId
> == reply:messageId"
>
> That relies on the response correlation ID being set to the request
> message ID - which does not happen automatically, as far as I can
> tell.
Correct. This the responsibility of the application being tested. But never is responsibility of the JMS provider to set it...
>
> > When you uncheck the "Use Request Message Id As Correlation Id" we
> are using the "JMS Correlation ID Pattern" and is necessary to set the
> correlatioId in the request and in the receiver we should check for
> "request:correlationId == reply:correlationId" as is implemented now.
>
> The service has to copy the correlationId from request to response.
Correct. Same as above
>
> Your use cases both rely on checking the response correlationId which
> it is assumed will be set from either the request correlationId or the
> requestMessageId.
>
> The person who raised the original Bug 46142 reported that the
> correlationId was null for JBoss, and the cited message thread says
> that the same problem happens with Weblogic.
>
> If the JMeter receiver only looks at the response correlationId, it
> seems this will cause problems for JBoss and Weblogic.
>
> So I think it is necessary to make the request and response fields
> independently selectable. I don't think on can satisfy everyone
> without.
>
> I've already done much of the work for this; it seems to work OK for
> ActiveMQ in "echo" mode at least.
It looks like the original bug was testing the "echo" mode. Then my idea of having different samplers for different things, but of course they can reuse much code.
>
> > Note: when I say "receiver" I mean the client side receiver, i.e the
> Jmeter receiver...
> >
> > Thanks for support
> >
> > João Ferreira
> >
> >
> > [1]
> http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/interopjms/M
> sgIDPatternforJMS.html
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Jmeter JMS support for Tibco EMS
Posted by sebb <se...@gmail.com>.
On 18/06/2010, João Tiago Ferreira <jo...@novabase.pt> wrote:
> Hi. I dont think there are so many use cases.
>
> First point is the sender of the message can't set the messageId. It is an identifier of the message generated by the JMS provider.
I know.
> Moreover two different messages can't have the same messageID, so I would say comparing "request:messageId == reply:messageId" makes no sense.
It *can* make sense in "echo" mode:
The sampler can send to a queue and then receive the original message
from the same queue. Could be useful for checking queue throughput.
In that case, *if* the correlationID is present of course one could
use that instead.
> Here is a nice explanation of the different JMS request response patterns [1].
Does not work for me - I get an empty page.
> So when you check the option "Use Request Message Id As Correlation Id" we are using the "JMS Message ID Pattern" where no correlationId is necessary to set in the request and in the receiver we should check for request:messageId == reply:correlationId instead of "request:messageId == reply:messageId"
That relies on the response correlation ID being set to the request
message ID - which does not happen automatically, as far as I can
tell.
> When you uncheck the "Use Request Message Id As Correlation Id" we are using the "JMS Correlation ID Pattern" and is necessary to set the correlatioId in the request and in the receiver we should check for "request:correlationId == reply:correlationId" as is implemented now.
The service has to copy the correlationId from request to response.
Your use cases both rely on checking the response correlationId which
it is assumed will be set from either the request correlationId or the
requestMessageId.
The person who raised the original Bug 46142 reported that the
correlationId was null for JBoss, and the cited message thread says
that the same problem happens with Weblogic.
If the JMeter receiver only looks at the response correlationId, it
seems this will cause problems for JBoss and Weblogic.
So I think it is necessary to make the request and response fields
independently selectable. I don't think on can satisfy everyone
without.
I've already done much of the work for this; it seems to work OK for
ActiveMQ in "echo" mode at least.
> Note: when I say "receiver" I mean the client side receiver, i.e the Jmeter receiver...
>
> Thanks for support
>
> João Ferreira
>
>
> [1] http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/interopjms/MsgIDPatternforJMS.html
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
RE: Jmeter JMS support for Tibco EMS
Posted by João Tiago Ferreira <jo...@novabase.pt>.
Hi. I dont think there are so many use cases.
First point is the sender of the message can't set the messageId. It is an identifier of the message generated by the JMS provider. Moreover two different messages can't have the same messageID, so I would say comparing "request:messageId == reply:messageId" makes no sense.
Here is a nice explanation of the different JMS request response patterns [1].
So when you check the option "Use Request Message Id As Correlation Id" we are using the "JMS Message ID Pattern" where no correlationId is necessary to set in the request and in the receiver we should check for request:messageId == reply:correlationId instead of "request:messageId == reply:messageId"
When you uncheck the "Use Request Message Id As Correlation Id" we are using the "JMS Correlation ID Pattern" and is necessary to set the correlatioId in the request and in the receiver we should check for "request:correlationId == reply:correlationId" as is implemented now.
Note: when I say "receiver" I mean the client side receiver, i.e the Jmeter receiver...
Thanks for support
João Ferreira
PS: I see that you have a wish to migrate your build tool to maven. If you want I could give some help, cause im a big fan of it, and would be easier to use Jmeter from 3rd party sources, for example JMeter plugin.
[1] http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/interopjms/MsgIDPatternforJMS.html
> -----Original Message-----
> From: sebb [mailto:sebbaz@gmail.com]
> Sent: sexta-feira, 18 de Junho de 2010 0:25
> To: JMeter Users List
> Subject: Re: Jmeter JMS support for Tibco EMS
>
>
> It looks like there are 4 options altogether, depending on which
> fields to use to correlate the messages:
>
> * request field: messageId or correlationId
> * response field: messageId or correlationId
>
> The current nightly code supports only the following 2 options:
>
> + request:messageId == reply:messageId
> + request:correlationId == reply:correlationId
>
> However AIUI your use case is
>
> request:messageId == reply:correlationId
>
> which is not currently supported.
>
> I think the solution is to allow the request and response "match"
> fields to be chosen independently.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Jmeter JMS support for Tibco EMS
Posted by sebb <se...@gmail.com>.
On 17/06/2010, João Tiago Ferreira <jo...@novabase.pt> wrote:
>
>
> > -----Original Message-----
> > From: sebb [mailto:sebbaz@gmail.com]
>
> > Sent: quinta-feira, 17 de Junho de 2010 15:57
> > To: JMeter Users List
> > Subject: Re: Jmeter JMS support for Tibco EMS
> >
> > On 17/06/2010, João Tiago Ferreira <jo...@novabase.pt>
> > wrote:
>
> > > Logs attached in jira.
> >
> > I think you mean Bugzilla ...
>
>
> Yes Bugzilla :p
>
>
> >
> > Can you also attach details of the source changes you needed to make?
>
>
> I modified org.apache.jmeter.protocol.jms.sampler.Receiver.run() line 84 in release 2.3.4 from:
> MessageAdmin.getAdmin().putReply(reply.getJMSMessageID(), reply);
> To:
> MessageAdmin.getAdmin().putReply(reply.getJMSCorrelationID(), reply);
>
>
> >
> > > Responses bellow
> > >
> > >
> > > -----Original Message-----
> > > From: sebb [mailto:sebbaz@gmail.com]
> > >
> > > Sent: quinta-feira, 17 de Junho de 2010 14:29
> > > To: JMeter Users List
> > > Subject: Re: Jmeter JMS support for Tibco EMS
> > >
> > > OK.
> > >
> > > On 17/06/2010, João Tiago Ferreira <jo...@novabase.pt>
> > wrote:
> > > > Hi, i will post my logs in this issue:
> > https://issues.apache.org/bugzilla/show_bug.cgi?id=46142 . You agree?
> > > >
> > > > João
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: sebb [mailto:sebbaz@gmail.com]
> > > > Sent: quinta-feira, 17 de Junho de 2010 13:33
> > > > To: JMeter Users List
> > > > Subject: Re: Jmeter JMS support for Tibco EMS
> > > >
> > > > On 17/06/2010, João Tiago Ferreira
> > <jo...@novabase.pt> wrote:
> > > > > Hi
> > > > >
> > > > > I am using jmeter to perform some functional tests in our
> > application. I
> > > > > need to send a request for the JMS server and wait for a
> > response.
> > > > >
> > > > > Our use case for the the use of correlation and message ids is
> > that the
> > > > > messageID of the request is used to set the correlationID of
> > the response.
> > > >
> > > > OK.
> > > >
> > > > > Using jmeter JMS request response the correlation is not
> > working as
> > > > > expected, neither in 2.3.4 or nightly builds.
> > > >
> > > > I'm not surprised about 2.3.4, however I thought the nightly
> > builds were better.
> > > >
> > > > Have you tried both settings of "Use Request Message Id As
> > Correlation Id"?
> > >
> > >
> > >
> > > Not checking that option requires setting the correlationID in JMS
> > Properties in the test, which I think makes no sense in Tibco EMS
> > neither other JMS servers...
> > >
> >
> > Why not?
> >
> > Surely one use case would be for the sender to supply the
> > correlationId that they want the service to return?
> >
> > This would allow the sender to choose something more meaningful than
> > the messageId - over which the sender has no control.
> >
> > >
> > > >
> > > > >
> > > > > I send the logs as attachments.
> > > >
> > > > Please don't send attachments to the list.
> > > > In this case they got lost anyway.
> > > >
> > > > Post them somewhere public and send the link, or create a
> > Bugzilla
> > > > issue and attach them there. That is probably best in this case.
> > > >
> > > > >
> > > > >
> > > > > As far as I can understand the JMS Sampler is using the
> > messageID of the
> > > > > response to match the messageID of the request,
> > > >
> > > > I don't think it does that, but I'll check.
> > > >
> > > > > while it should use the correlationID of the response.
> > > >
> > > > Sometimes - I think that depends on how the JMS service is
> > configured.
> > > >
> > > > > I easily modified the source to fit my needs, but wanted to
> > contribute my
> > > > > testing with Tibco EMS. I also noted that several bug reports
> > exist about
> > > > > this issue.
> > > >
> > > > Yes, this is a tricky area, partly because JMS knowledge within
> > the
> > > > team is limited, and partly because the protocol does not seem to
> > be
> > > > particularly well-defined with regard to how correlationId is
> > treated.
> > > >
> > > > AIUI, not all JMS providers behave the same way:
> > > > Some may copy the request messageId to the response
> > correlationId.
> > > > Others may copy the request correlationId to the response
> > correlationId.
> > > > There may be other behaviours.
> > > >
> > > > I could not find any documentation that defines what the
> > "correct" behaviour is.
> > > > As far as I could tell, the setting of the response correlationId
> > is
> > > > server- or application-defined. [If you have details, please post
> > a
> > > > link to the docs!]
> > >
> > >
> > > In my application is responsibility of the application to set the
> > correlationID from the request messageID.
> >
> > OK.
> >
> > This tends to confirm what I wrote about the lack of a standard, and
> > therefore the JMeter behaviour needs to be confgurable.
>
>
> Yes the reference isn't clear and some use cases tend to break other, so making this configurable is the way to go...
It looks like there are 4 options altogether, depending on which
fields to use to correlate the messages:
* request field: messageId or correlationId
* response field: messageId or correlationId
The current nightly code supports only the following 2 options:
+ request:messageId == reply:messageId
+ request:correlationId == reply:correlationId
However AIUI your use case is
request:messageId == reply:correlationId
which is not currently supported.
I think the solution is to allow the request and response "match"
fields to be chosen independently.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
RE: Jmeter JMS support for Tibco EMS
Posted by João Tiago Ferreira <jo...@novabase.pt>.
> -----Original Message-----
> From: sebb [mailto:sebbaz@gmail.com]
> Sent: quinta-feira, 17 de Junho de 2010 15:57
> To: JMeter Users List
> Subject: Re: Jmeter JMS support for Tibco EMS
>
> On 17/06/2010, João Tiago Ferreira <jo...@novabase.pt>
> wrote:
> > Logs attached in jira.
>
> I think you mean Bugzilla ...
Yes Bugzilla :p
>
> Can you also attach details of the source changes you needed to make?
I modified org.apache.jmeter.protocol.jms.sampler.Receiver.run() line 84 in release 2.3.4 from:
MessageAdmin.getAdmin().putReply(reply.getJMSMessageID(), reply);
To:
MessageAdmin.getAdmin().putReply(reply.getJMSCorrelationID(), reply);
>
> > Responses bellow
> >
> >
> > -----Original Message-----
> > From: sebb [mailto:sebbaz@gmail.com]
> >
> > Sent: quinta-feira, 17 de Junho de 2010 14:29
> > To: JMeter Users List
> > Subject: Re: Jmeter JMS support for Tibco EMS
> >
> > OK.
> >
> > On 17/06/2010, João Tiago Ferreira <jo...@novabase.pt>
> wrote:
> > > Hi, i will post my logs in this issue:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=46142 . You agree?
> > >
> > > João
> > >
> > >
> > > -----Original Message-----
> > > From: sebb [mailto:sebbaz@gmail.com]
> > > Sent: quinta-feira, 17 de Junho de 2010 13:33
> > > To: JMeter Users List
> > > Subject: Re: Jmeter JMS support for Tibco EMS
> > >
> > > On 17/06/2010, João Tiago Ferreira
> <jo...@novabase.pt> wrote:
> > > > Hi
> > > >
> > > > I am using jmeter to perform some functional tests in our
> application. I
> > > > need to send a request for the JMS server and wait for a
> response.
> > > >
> > > > Our use case for the the use of correlation and message ids is
> that the
> > > > messageID of the request is used to set the correlationID of
> the response.
> > >
> > > OK.
> > >
> > > > Using jmeter JMS request response the correlation is not
> working as
> > > > expected, neither in 2.3.4 or nightly builds.
> > >
> > > I'm not surprised about 2.3.4, however I thought the nightly
> builds were better.
> > >
> > > Have you tried both settings of "Use Request Message Id As
> Correlation Id"?
> >
> >
> >
> > Not checking that option requires setting the correlationID in JMS
> Properties in the test, which I think makes no sense in Tibco EMS
> neither other JMS servers...
> >
>
> Why not?
>
> Surely one use case would be for the sender to supply the
> correlationId that they want the service to return?
>
> This would allow the sender to choose something more meaningful than
> the messageId - over which the sender has no control.
>
> >
> > >
> > > >
> > > > I send the logs as attachments.
> > >
> > > Please don't send attachments to the list.
> > > In this case they got lost anyway.
> > >
> > > Post them somewhere public and send the link, or create a
> Bugzilla
> > > issue and attach them there. That is probably best in this case.
> > >
> > > >
> > > >
> > > > As far as I can understand the JMS Sampler is using the
> messageID of the
> > > > response to match the messageID of the request,
> > >
> > > I don't think it does that, but I'll check.
> > >
> > > > while it should use the correlationID of the response.
> > >
> > > Sometimes - I think that depends on how the JMS service is
> configured.
> > >
> > > > I easily modified the source to fit my needs, but wanted to
> contribute my
> > > > testing with Tibco EMS. I also noted that several bug reports
> exist about
> > > > this issue.
> > >
> > > Yes, this is a tricky area, partly because JMS knowledge within
> the
> > > team is limited, and partly because the protocol does not seem to
> be
> > > particularly well-defined with regard to how correlationId is
> treated.
> > >
> > > AIUI, not all JMS providers behave the same way:
> > > Some may copy the request messageId to the response
> correlationId.
> > > Others may copy the request correlationId to the response
> correlationId.
> > > There may be other behaviours.
> > >
> > > I could not find any documentation that defines what the
> "correct" behaviour is.
> > > As far as I could tell, the setting of the response correlationId
> is
> > > server- or application-defined. [If you have details, please post
> a
> > > link to the docs!]
> >
> >
> > In my application is responsibility of the application to set the
> correlationID from the request messageID.
>
> OK.
>
> This tends to confirm what I wrote about the lack of a standard, and
> therefore the JMeter behaviour needs to be confgurable.
Yes the reference isn't clear and some use cases tend to break other, so making this configurable is the way to go...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Jmeter JMS support for Tibco EMS
Posted by sebb <se...@gmail.com>.
On 17/06/2010, João Tiago Ferreira <jo...@novabase.pt> wrote:
> Logs attached in jira.
I think you mean Bugzilla ...
Can you also attach details of the source changes you needed to make?
> Responses bellow
>
>
> -----Original Message-----
> From: sebb [mailto:sebbaz@gmail.com]
>
> Sent: quinta-feira, 17 de Junho de 2010 14:29
> To: JMeter Users List
> Subject: Re: Jmeter JMS support for Tibco EMS
>
> OK.
>
> On 17/06/2010, João Tiago Ferreira <jo...@novabase.pt> wrote:
> > Hi, i will post my logs in this issue: https://issues.apache.org/bugzilla/show_bug.cgi?id=46142 . You agree?
> >
> > João
> >
> >
> > -----Original Message-----
> > From: sebb [mailto:sebbaz@gmail.com]
> > Sent: quinta-feira, 17 de Junho de 2010 13:33
> > To: JMeter Users List
> > Subject: Re: Jmeter JMS support for Tibco EMS
> >
> > On 17/06/2010, João Tiago Ferreira <jo...@novabase.pt> wrote:
> > > Hi
> > >
> > > I am using jmeter to perform some functional tests in our application. I
> > > need to send a request for the JMS server and wait for a response.
> > >
> > > Our use case for the the use of correlation and message ids is that the
> > > messageID of the request is used to set the correlationID of the response.
> >
> > OK.
> >
> > > Using jmeter JMS request response the correlation is not working as
> > > expected, neither in 2.3.4 or nightly builds.
> >
> > I'm not surprised about 2.3.4, however I thought the nightly builds were better.
> >
> > Have you tried both settings of "Use Request Message Id As Correlation Id"?
>
>
>
> Not checking that option requires setting the correlationID in JMS Properties in the test, which I think makes no sense in Tibco EMS neither other JMS servers...
>
Why not?
Surely one use case would be for the sender to supply the
correlationId that they want the service to return?
This would allow the sender to choose something more meaningful than
the messageId - over which the sender has no control.
>
> >
> > >
> > > I send the logs as attachments.
> >
> > Please don't send attachments to the list.
> > In this case they got lost anyway.
> >
> > Post them somewhere public and send the link, or create a Bugzilla
> > issue and attach them there. That is probably best in this case.
> >
> > >
> > >
> > > As far as I can understand the JMS Sampler is using the messageID of the
> > > response to match the messageID of the request,
> >
> > I don't think it does that, but I'll check.
> >
> > > while it should use the correlationID of the response.
> >
> > Sometimes - I think that depends on how the JMS service is configured.
> >
> > > I easily modified the source to fit my needs, but wanted to contribute my
> > > testing with Tibco EMS. I also noted that several bug reports exist about
> > > this issue.
> >
> > Yes, this is a tricky area, partly because JMS knowledge within the
> > team is limited, and partly because the protocol does not seem to be
> > particularly well-defined with regard to how correlationId is treated.
> >
> > AIUI, not all JMS providers behave the same way:
> > Some may copy the request messageId to the response correlationId.
> > Others may copy the request correlationId to the response correlationId.
> > There may be other behaviours.
> >
> > I could not find any documentation that defines what the "correct" behaviour is.
> > As far as I could tell, the setting of the response correlationId is
> > server- or application-defined. [If you have details, please post a
> > link to the docs!]
>
>
> In my application is responsibility of the application to set the correlationID from the request messageID.
OK.
This tends to confirm what I wrote about the lack of a standard, and
therefore the JMeter behaviour needs to be confgurable.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
RE: Jmeter JMS support for Tibco EMS
Posted by João Tiago Ferreira <jo...@novabase.pt>.
Logs attached in jira.
Responses bellow
-----Original Message-----
From: sebb [mailto:sebbaz@gmail.com]
Sent: quinta-feira, 17 de Junho de 2010 14:29
To: JMeter Users List
Subject: Re: Jmeter JMS support for Tibco EMS
OK.
On 17/06/2010, João Tiago Ferreira <jo...@novabase.pt> wrote:
> Hi, i will post my logs in this issue: https://issues.apache.org/bugzilla/show_bug.cgi?id=46142 . You agree?
>
> João
>
>
> -----Original Message-----
> From: sebb [mailto:sebbaz@gmail.com]
> Sent: quinta-feira, 17 de Junho de 2010 13:33
> To: JMeter Users List
> Subject: Re: Jmeter JMS support for Tibco EMS
>
> On 17/06/2010, João Tiago Ferreira <jo...@novabase.pt> wrote:
> > Hi
> >
> > I am using jmeter to perform some functional tests in our application. I
> > need to send a request for the JMS server and wait for a response.
> >
> > Our use case for the the use of correlation and message ids is that the
> > messageID of the request is used to set the correlationID of the response.
>
> OK.
>
> > Using jmeter JMS request response the correlation is not working as
> > expected, neither in 2.3.4 or nightly builds.
>
> I'm not surprised about 2.3.4, however I thought the nightly builds were better.
>
> Have you tried both settings of "Use Request Message Id As Correlation Id"?
Not checking that option requires setting the correlationID in JMS Properties in the test, which I think makes no sense in Tibco EMS neither other JMS servers...
>
> >
> > I send the logs as attachments.
>
> Please don't send attachments to the list.
> In this case they got lost anyway.
>
> Post them somewhere public and send the link, or create a Bugzilla
> issue and attach them there. That is probably best in this case.
>
> >
> >
> > As far as I can understand the JMS Sampler is using the messageID of the
> > response to match the messageID of the request,
>
> I don't think it does that, but I'll check.
>
> > while it should use the correlationID of the response.
>
> Sometimes - I think that depends on how the JMS service is configured.
>
> > I easily modified the source to fit my needs, but wanted to contribute my
> > testing with Tibco EMS. I also noted that several bug reports exist about
> > this issue.
>
> Yes, this is a tricky area, partly because JMS knowledge within the
> team is limited, and partly because the protocol does not seem to be
> particularly well-defined with regard to how correlationId is treated.
>
> AIUI, not all JMS providers behave the same way:
> Some may copy the request messageId to the response correlationId.
> Others may copy the request correlationId to the response correlationId.
> There may be other behaviours.
>
> I could not find any documentation that defines what the "correct" behaviour is.
> As far as I could tell, the setting of the response correlationId is
> server- or application-defined. [If you have details, please post a
> link to the docs!]
In my application is responsibility of the application to set the correlationID from the request messageID.
>
> If changes need to be made to support Tibco JMS, we need to ensure
> that these don't prevent JMeter from working with other JMS providers
> - or indeed with other different configurations of Tibco.
>
> This probably means adding some optional behaviour to the correlation
> processing so users can configure it as needed.
>
> I think the first stage would be to get JMeter working with Tibco, and
> then look at how to provide configuration options for any changes that
> might be needed.
>
> So please create a Bugzilla with your suggested changes, and logs from
> current JMeter.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Jmeter JMS support for Tibco EMS
Posted by sebb <se...@gmail.com>.
OK.
On 17/06/2010, João Tiago Ferreira <jo...@novabase.pt> wrote:
> Hi, i will post my logs in this issue: https://issues.apache.org/bugzilla/show_bug.cgi?id=46142 . You agree?
>
> João
>
>
> -----Original Message-----
> From: sebb [mailto:sebbaz@gmail.com]
> Sent: quinta-feira, 17 de Junho de 2010 13:33
> To: JMeter Users List
> Subject: Re: Jmeter JMS support for Tibco EMS
>
> On 17/06/2010, João Tiago Ferreira <jo...@novabase.pt> wrote:
> > Hi
> >
> > I am using jmeter to perform some functional tests in our application. I
> > need to send a request for the JMS server and wait for a response.
> >
> > Our use case for the the use of correlation and message ids is that the
> > messageID of the request is used to set the correlationID of the response.
>
> OK.
>
> > Using jmeter JMS request response the correlation is not working as
> > expected, neither in 2.3.4 or nightly builds.
>
> I'm not surprised about 2.3.4, however I thought the nightly builds were better.
>
> Have you tried both settings of "Use Request Message Id As Correlation Id"?
>
> >
> > I send the logs as attachments.
>
> Please don't send attachments to the list.
> In this case they got lost anyway.
>
> Post them somewhere public and send the link, or create a Bugzilla
> issue and attach them there. That is probably best in this case.
>
> >
> >
> > As far as I can understand the JMS Sampler is using the messageID of the
> > response to match the messageID of the request,
>
> I don't think it does that, but I'll check.
>
> > while it should use the correlationID of the response.
>
> Sometimes - I think that depends on how the JMS service is configured.
>
> > I easily modified the source to fit my needs, but wanted to contribute my
> > testing with Tibco EMS. I also noted that several bug reports exist about
> > this issue.
>
> Yes, this is a tricky area, partly because JMS knowledge within the
> team is limited, and partly because the protocol does not seem to be
> particularly well-defined with regard to how correlationId is treated.
>
> AIUI, not all JMS providers behave the same way:
> Some may copy the request messageId to the response correlationId.
> Others may copy the request correlationId to the response correlationId.
> There may be other behaviours.
>
> I could not find any documentation that defines what the "correct" behaviour is.
> As far as I could tell, the setting of the response correlationId is
> server- or application-defined. [If you have details, please post a
> link to the docs!]
>
> If changes need to be made to support Tibco JMS, we need to ensure
> that these don't prevent JMeter from working with other JMS providers
> - or indeed with other different configurations of Tibco.
>
> This probably means adding some optional behaviour to the correlation
> processing so users can configure it as needed.
>
> I think the first stage would be to get JMeter working with Tibco, and
> then look at how to provide configuration options for any changes that
> might be needed.
>
> So please create a Bugzilla with your suggested changes, and logs from
> current JMeter.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
RE: Jmeter JMS support for Tibco EMS
Posted by João Tiago Ferreira <jo...@novabase.pt>.
Hi, i will post my logs in this issue: https://issues.apache.org/bugzilla/show_bug.cgi?id=46142 . You agree?
João
-----Original Message-----
From: sebb [mailto:sebbaz@gmail.com]
Sent: quinta-feira, 17 de Junho de 2010 13:33
To: JMeter Users List
Subject: Re: Jmeter JMS support for Tibco EMS
On 17/06/2010, João Tiago Ferreira <jo...@novabase.pt> wrote:
> Hi
>
> I am using jmeter to perform some functional tests in our application. I
> need to send a request for the JMS server and wait for a response.
>
> Our use case for the the use of correlation and message ids is that the
> messageID of the request is used to set the correlationID of the response.
OK.
> Using jmeter JMS request response the correlation is not working as
> expected, neither in 2.3.4 or nightly builds.
I'm not surprised about 2.3.4, however I thought the nightly builds were better.
Have you tried both settings of "Use Request Message Id As Correlation Id"?
>
> I send the logs as attachments.
Please don't send attachments to the list.
In this case they got lost anyway.
Post them somewhere public and send the link, or create a Bugzilla
issue and attach them there. That is probably best in this case.
>
>
> As far as I can understand the JMS Sampler is using the messageID of the
> response to match the messageID of the request,
I don't think it does that, but I'll check.
> while it should use the correlationID of the response.
Sometimes - I think that depends on how the JMS service is configured.
> I easily modified the source to fit my needs, but wanted to contribute my
> testing with Tibco EMS. I also noted that several bug reports exist about
> this issue.
Yes, this is a tricky area, partly because JMS knowledge within the
team is limited, and partly because the protocol does not seem to be
particularly well-defined with regard to how correlationId is treated.
AIUI, not all JMS providers behave the same way:
Some may copy the request messageId to the response correlationId.
Others may copy the request correlationId to the response correlationId.
There may be other behaviours.
I could not find any documentation that defines what the "correct" behaviour is.
As far as I could tell, the setting of the response correlationId is
server- or application-defined. [If you have details, please post a
link to the docs!]
If changes need to be made to support Tibco JMS, we need to ensure
that these don't prevent JMeter from working with other JMS providers
- or indeed with other different configurations of Tibco.
This probably means adding some optional behaviour to the correlation
processing so users can configure it as needed.
I think the first stage would be to get JMeter working with Tibco, and
then look at how to provide configuration options for any changes that
might be needed.
So please create a Bugzilla with your suggested changes, and logs from
current JMeter.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Jmeter JMS support for Tibco EMS
Posted by sebb <se...@gmail.com>.
On 17/06/2010, João Tiago Ferreira <jo...@novabase.pt> wrote:
> Hi
>
> I am using jmeter to perform some functional tests in our application. I
> need to send a request for the JMS server and wait for a response.
>
> Our use case for the the use of correlation and message ids is that the
> messageID of the request is used to set the correlationID of the response.
OK.
> Using jmeter JMS request response the correlation is not working as
> expected, neither in 2.3.4 or nightly builds.
I'm not surprised about 2.3.4, however I thought the nightly builds were better.
Have you tried both settings of "Use Request Message Id As Correlation Id"?
>
> I send the logs as attachments.
Please don't send attachments to the list.
In this case they got lost anyway.
Post them somewhere public and send the link, or create a Bugzilla
issue and attach them there. That is probably best in this case.
>
>
> As far as I can understand the JMS Sampler is using the messageID of the
> response to match the messageID of the request,
I don't think it does that, but I'll check.
> while it should use the correlationID of the response.
Sometimes - I think that depends on how the JMS service is configured.
> I easily modified the source to fit my needs, but wanted to contribute my
> testing with Tibco EMS. I also noted that several bug reports exist about
> this issue…
Yes, this is a tricky area, partly because JMS knowledge within the
team is limited, and partly because the protocol does not seem to be
particularly well-defined with regard to how correlationId is treated.
AIUI, not all JMS providers behave the same way:
Some may copy the request messageId to the response correlationId.
Others may copy the request correlationId to the response correlationId.
There may be other behaviours.
I could not find any documentation that defines what the "correct" behaviour is.
As far as I could tell, the setting of the response correlationId is
server- or application-defined. [If you have details, please post a
link to the docs!]
If changes need to be made to support Tibco JMS, we need to ensure
that these don't prevent JMeter from working with other JMS providers
- or indeed with other different configurations of Tibco.
This probably means adding some optional behaviour to the correlation
processing so users can configure it as needed.
I think the first stage would be to get JMeter working with Tibco, and
then look at how to provide configuration options for any changes that
might be needed.
So please create a Bugzilla with your suggested changes, and logs from
current JMeter.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org