Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JMS Publisher sampler forces Byte Messages in Text Message textfield via XStream #4903

Open
asfimport opened this issue Oct 26, 2018 · 1 comment

Comments

@asfimport
Copy link
Collaborator

Andrew Burton (Bug 62856):
The JMS Publisher sampler passes Bytes messages that are specified in the Text Message textfield via an XML stream.

If a PreProcessor converts the text to a byte encoded string and passes the variable in the Text Message textfield as a workaround, then this is converted back to String before being sent.

In my use case, I am supplying a byte-encoded JSON text string to the JMS queue/topic, it doesn't need to be converted to XML first.

The only way to have this work is to supply the JSON text in a file.

The desired approach would be to have an option for Bytes Messages to be created directly from the string (either the Text Message textfield or the file), without going via the XML XStream converter.

OS: All

@asfimport
Copy link
Collaborator Author

Andrew Burton (migrated from Bugzilla):
The restriction is due to Message Source = Text Area is not supported when choosing a Message Type = Bytes Message.

If choosing Message Type = Object Message, the message is converted to an XML source first (which in the case of a JSON string is not correct).

Probably the help for this sampler (https://jmeter.apache.org/usermanual/component_reference.html#JMS_Publisher) needs to also describe the difference between the Message Types as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant