Vertx amqp bridge message decoding exception
0
We are trying receive messages from Amqp broker hosted on solace vmr using vertx amqp bridge. We are receiving the following exception when there is special character in the message. Please let us know how to handle this.
ERROR:
vert.x-eventloop-thread-0] null.null Unhandled exception
java.lang.IllegalArgumentException: Cannot parse String
vert.x solace solace-mq
asked Nov 20 at 21:33
Venkat N
32
|
show 1 more comment
0
We are trying receive messages from Amqp broker hosted on solace vmr using vertx amqp bridge. We are receiving the following exception when there is special character in the message. Please let us know how to handle this.
ERROR:
vert.x-eventloop-thread-0] null.null Unhandled exception
java.lang.IllegalArgumentException: Cannot parse String
vert.x solace solace-mq
asked Nov 20 at 21:33
Venkat N
32
It would be helpful if you can elaborate upon the problem a little more, like what is the special character that you are failing with and sample code around the message listener that you have coded. It can helpful to recreate the problem and provide you good suggestions here.
– y ramesh rao
Nov 21 at 9:12
We are getting the special character like ü in the input message. We are getting cannot parse string exception when AMQP message is getting converted in JsonObject (Vertx). This is happening only when the input message has special charaters as mentioned above. Its happening in the Qpid proton transport layer not in the vertx coding.Kindly let us know if you need any information.
– Venkat N
Nov 21 at 10:11
Below is code snippet: Here vertxMsg is getting null so we are getting java.lang.IllegalArgumentException: Cannot parse String consumer.handler(vertxMsg -> { try{ boolean ret; JsonObject amqpMsgPayload = vertxMsg.body(); String amqpBody = amqpMsgPayload.getString(AmqpConstants.BODY);
– Venkat N
Nov 21 at 10:11
What exactly was sent by the publishing application? It would appear that the publisher has sent the "special character" in some encoding that's Vertex is not expecting.
– Russell Sim
Nov 22 at 4:42
Publisher using UTF-8 for encoding , but it is the special emoji characters that they use that is causing a problem. Vertx client using UTF-8 character for decoding.
– Venkat N
Nov 22 at 19:33
|
show 1 more comment
0
0
0
We are trying receive messages from Amqp broker hosted on solace vmr using vertx amqp bridge. We are receiving the following exception when there is special character in the message. Please let us know how to handle this.
ERROR:
vert.x-eventloop-thread-0] null.null Unhandled exception
java.lang.IllegalArgumentException: Cannot parse String
vert.x solace solace-mq
asked Nov 20 at 21:33
Venkat N
32
We are trying receive messages from Amqp broker hosted on solace vmr using vertx amqp bridge. We are receiving the following exception when there is special character in the message. Please let us know how to handle this.
ERROR:
vert.x-eventloop-thread-0] null.null Unhandled exception
java.lang.IllegalArgumentException: Cannot parse String
vert.x solace solace-mq
vert.x solace solace-mq
asked Nov 20 at 21:33
Venkat N
32
asked Nov 20 at 21:33
Venkat N
32
asked Nov 20 at 21:33
Venkat N
32
asked Nov 20 at 21:33
Venkat N
32
asked Nov 20 at 21:33
Venkat N
32
32
It would be helpful if you can elaborate upon the problem a little more, like what is the special character that you are failing with and sample code around the message listener that you have coded. It can helpful to recreate the problem and provide you good suggestions here.
– y ramesh rao
Nov 21 at 9:12
We are getting the special character like ü in the input message. We are getting cannot parse string exception when AMQP message is getting converted in JsonObject (Vertx). This is happening only when the input message has special charaters as mentioned above. Its happening in the Qpid proton transport layer not in the vertx coding.Kindly let us know if you need any information.
– Venkat N
Nov 21 at 10:11
Below is code snippet: Here vertxMsg is getting null so we are getting java.lang.IllegalArgumentException: Cannot parse String consumer.handler(vertxMsg -> { try{ boolean ret; JsonObject amqpMsgPayload = vertxMsg.body(); String amqpBody = amqpMsgPayload.getString(AmqpConstants.BODY);
– Venkat N
Nov 21 at 10:11
What exactly was sent by the publishing application? It would appear that the publisher has sent the "special character" in some encoding that's Vertex is not expecting.
– Russell Sim
Nov 22 at 4:42
Publisher using UTF-8 for encoding , but it is the special emoji characters that they use that is causing a problem. Vertx client using UTF-8 character for decoding.
– Venkat N
Nov 22 at 19:33
|
show 1 more comment
It would be helpful if you can elaborate upon the problem a little more, like what is the special character that you are failing with and sample code around the message listener that you have coded. It can helpful to recreate the problem and provide you good suggestions here.
– y ramesh rao
Nov 21 at 9:12
We are getting the special character like ü in the input message. We are getting cannot parse string exception when AMQP message is getting converted in JsonObject (Vertx). This is happening only when the input message has special charaters as mentioned above. Its happening in the Qpid proton transport layer not in the vertx coding.Kindly let us know if you need any information.
– Venkat N
Nov 21 at 10:11
Below is code snippet: Here vertxMsg is getting null so we are getting java.lang.IllegalArgumentException: Cannot parse String consumer.handler(vertxMsg -> { try{ boolean ret; JsonObject amqpMsgPayload = vertxMsg.body(); String amqpBody = amqpMsgPayload.getString(AmqpConstants.BODY);
– Venkat N
Nov 21 at 10:11
What exactly was sent by the publishing application? It would appear that the publisher has sent the "special character" in some encoding that's Vertex is not expecting.
– Russell Sim
Nov 22 at 4:42
Publisher using UTF-8 for encoding , but it is the special emoji characters that they use that is causing a problem. Vertx client using UTF-8 character for decoding.
– Venkat N
Nov 22 at 19:33
It would be helpful if you can elaborate upon the problem a little more, like what is the special character that you are failing with and sample code around the message listener that you have coded. It can helpful to recreate the problem and provide you good suggestions here.
– y ramesh rao
Nov 21 at 9:12
It would be helpful if you can elaborate upon the problem a little more, like what is the special character that you are failing with and sample code around the message listener that you have coded. It can helpful to recreate the problem and provide you good suggestions here.
– y ramesh rao
Nov 21 at 9:12
We are getting the special character like ü in the input message. We are getting cannot parse string exception when AMQP message is getting converted in JsonObject (Vertx). This is happening only when the input message has special charaters as mentioned above. Its happening in the Qpid proton transport layer not in the vertx coding.Kindly let us know if you need any information.
– Venkat N
Nov 21 at 10:11
We are getting the special character like ü in the input message. We are getting cannot parse string exception when AMQP message is getting converted in JsonObject (Vertx). This is happening only when the input message has special charaters as mentioned above. Its happening in the Qpid proton transport layer not in the vertx coding.Kindly let us know if you need any information.
– Venkat N
Nov 21 at 10:11
Below is code snippet: Here vertxMsg is getting null so we are getting java.lang.IllegalArgumentException: Cannot parse String consumer.handler(vertxMsg -> { try{ boolean ret; JsonObject amqpMsgPayload = vertxMsg.body(); String amqpBody = amqpMsgPayload.getString(AmqpConstants.BODY);
– Venkat N
Nov 21 at 10:11
Below is code snippet: Here vertxMsg is getting null so we are getting java.lang.IllegalArgumentException: Cannot parse String consumer.handler(vertxMsg -> { try{ boolean ret; JsonObject amqpMsgPayload = vertxMsg.body(); String amqpBody = amqpMsgPayload.getString(AmqpConstants.BODY);
– Venkat N
Nov 21 at 10:11
What exactly was sent by the publishing application? It would appear that the publisher has sent the "special character" in some encoding that's Vertex is not expecting.
– Russell Sim
Nov 22 at 4:42
What exactly was sent by the publishing application? It would appear that the publisher has sent the "special character" in some encoding that's Vertex is not expecting.
– Russell Sim
Nov 22 at 4:42
Publisher using UTF-8 for encoding , but it is the special emoji characters that they use that is causing a problem. Vertx client using UTF-8 character for decoding.
– Venkat N
Nov 22 at 19:33
Publisher using UTF-8 for encoding , but it is the special emoji characters that they use that is causing a problem. Vertx client using UTF-8 character for decoding.
– Venkat N
Nov 22 at 19:33
|
show 1 more comment
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53401910%2fvertx-amqp-bridge-message-decoding-exception%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53401910%2fvertx-amqp-bridge-message-decoding-exception%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
It would be helpful if you can elaborate upon the problem a little more, like what is the special character that you are failing with and sample code around the message listener that you have coded. It can helpful to recreate the problem and provide you good suggestions here.
– y ramesh rao
Nov 21 at 9:12
We are getting the special character like ü in the input message. We are getting cannot parse string exception when AMQP message is getting converted in JsonObject (Vertx). This is happening only when the input message has special charaters as mentioned above. Its happening in the Qpid proton transport layer not in the vertx coding.Kindly let us know if you need any information.
– Venkat N
Nov 21 at 10:11
Below is code snippet: Here vertxMsg is getting null so we are getting java.lang.IllegalArgumentException: Cannot parse String consumer.handler(vertxMsg -> { try{ boolean ret; JsonObject amqpMsgPayload = vertxMsg.body(); String amqpBody = amqpMsgPayload.getString(AmqpConstants.BODY);
– Venkat N
Nov 21 at 10:11
What exactly was sent by the publishing application? It would appear that the publisher has sent the "special character" in some encoding that's Vertex is not expecting.
– Russell Sim
Nov 22 at 4:42
Publisher using UTF-8 for encoding , but it is the special emoji characters that they use that is causing a problem. Vertx client using UTF-8 character for decoding.
– Venkat N
Nov 22 at 19:33