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 2016/03/29 15:48:38 UTC
[Bug 59245] New: JMS Point to Point custom request headers
https://bz.apache.org/bugzilla/show_bug.cgi?id=59245
Bug ID: 59245
Summary: JMS Point to Point custom request headers
Product: JMeter
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P2
Component: Main
Assignee: issues@jmeter.apache.org
Reporter: mdiianni@gmail.com
Increasing security threads force service providers to increase security levels
on their backend applications to communicate across the network.
Publishing and Subscribing to message queues requires more and more the use of
TLS security to validate source and destination of the messages (signing). Some
companies or developers has opted for including a custom header on the JMS
request with a signature which is a valid approach but not possible to test it
using JMeter as custom headers are not allowed yet on JMS Point to Point
sampler.
The only way to test the service so far is to disable TLS or include a JSR223
Pre-processor to deal with it, but actually building a pre-processor means
re-implement the whole JMS Point to Point sampler which is a bit of a nonsense.
Thank you,
Maurizio
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59245] JMS Point to Point custom request headers
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59245
mdiianni <md...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59245] JMS Point to Point custom request headers
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59245
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |p.mouawad@ubik-ingenierie.c
| |om
Status|NEW |NEEDINFO
--- Comment #1 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
Hello,
So that your request is clear for us, could you attach your JSR223 preprocessor
code ?
AFAIU JMS Header as of 1.1 are restricted to :
JMSCorrelationId
JMSMessageId
JMSTimestamp
JMSType
JMSExpiration
JMSPriority
JMSDestination
Message header field references are restricted to JMSDeliveryMode, JMSPriority,
JMSMessageID, JMSTimestamp, JMSCorrelationID, and JMSType.
JMSMessageID, JMSCorrelationID, and JMSType values may be null and if so are
treated as a NULL value.
What is the Header that you need to add ?
Thanks for clarification
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59245] JMS Point to Point custom request headers
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59245
--- Comment #3 from mdiianni <md...@gmail.com> ---
Created attachment 33711
--> https://bz.apache.org/bugzilla/attachment.cgi?id=33711&action=edit
jmsclient snippet
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 59245] JMS Point to Point custom request headers
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59245
--- Comment #2 from mdiianni <md...@gmail.com> ---
Hi Phillipe, thanks your reply,
Basically I'm trying to run a test injecting messages into a JMS queue using
JMeter Point-to-Point Sampler using Request Only mode (fire and forget).
On application side, provider has implemented a solution using Apache
ServiceMix stack which implements ActiveMQ, Camel, CXF and Karaf.
Camel in this case is handling the signing and verification on application side
using camel:crypto (http://camel.apache.org/crypto.html). What is does is
generate a message signature and put it into the 'CamelDigitalSignature' JMS
header.
So far, I don't have yet a preprocessor to handle this yet, still work in
progress.
Attached there is a java snippet with the skeleton of what I have done so far
to sign the message, I still need to sort out adding the header and send the
jms request.
--
You are receiving this mail because:
You are the assignee for the bug.