Bug 52054

Summary:	"Post Regular Expression Extractor" using with JMS Publisher
Product:	JMeter	Reporter:	Yaroslav <slavko_h>
Component:	Main	Assignee:	JMeter issues mailing list <issues>
Status:	RESOLVED FIXED
Severity:	enhancement	CC:	p.mouawad
Priority:	P2
Version:	2.5.1
Target Milestone:	---
Hardware:	All
OS:	All
Attachments:	Debug Pub RegExpExtr JMS Publisher Test Plan

Description Yaroslav 2011-10-18 21:41:36 UTC

The issue is that user can not get any info from Headers.

JMS Publisher sends message to a queue and AMQ returns some header-info (including JMSMEssageId, etc) - see YH1179 screenshot.

I'm using Post RegExpExtr - see 1180 screenshot.
The extractor supposes to extract "JMSMessageId" value into TT_PUB variable.

See Debug screenshot - the value is not extracted.

ER: user is able to use Post RegExpExtr with JMS Publisher to extract any info from returned Header.

Comment 1 Yaroslav 2011-10-18 21:42:02 UTC

Created attachment 27814 [details]
Debug

Comment 2 Yaroslav 2011-10-18 21:42:41 UTC

Created attachment 27815 [details]
Pub RegExpExtr

Comment 3 Yaroslav 2011-10-18 21:43:04 UTC

Created attachment 27816 [details]
JMS Publisher

Comment 4 Yaroslav 2011-10-18 21:44:03 UTC

Created attachment 27817 [details]
Test Plan

Comment 5 Philippe Mouawad 2011-10-19 21:06:50 UTC

JMS is an asynchronous protocol so doing this seems to me weird.
Furthermore, JMSMessageId is in Request Headers no response headers.

So if we decide to implement it it is more an enhancement than a bug.

Regards
Philippe

Comment 6 Sebb 2011-10-20 08:10:14 UTC

(In reply to comment #5)
> JMS is an asynchronous protocol so doing this seems to me weird.

However, the id is set on return from the send message call; as such this part is synchronous.

> Furthermore, JMSMessageId is in Request Headers not response headers.
>
> So if we decide to implement it it is more an enhancement than a bug.

The Regex Extractor was written assuming that the request details are already known, so it was not felt necessary to allow access to the request headers, only the response headers.

However, there are probably other samplers where not all of the request details are known in advance - or easy to access - so it probably would be worthwile enhancing some of the PostProcessors accordingly. See Bug 52061.

As a workround in the meantime, you can use the BSH or BSF postprocessor to access the response request headers. 

Resolving this issue, as the work is now to be done as part of Bug 52061.

Comment 7 Yaroslav 2011-10-20 16:16:00 UTC

Agree.