You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by LordOfTheCows <md...@golemlabs.com> on 2011/05/17 19:49:12 UTC

activemq-cpp invalid UTF-8 issue

Activemq : version 5.5.0
Activemq-cms : version 3.4.0

Hello,

A message consumer is currently throwing an exception with the following
message (caught with the exception listener) :

  "Invalid 2 byte UTF-8 encoding found, This method only supports encoded
ASCII values of (0-255)."

Sadly, I do not have the complete stack trace at this time. When this error
is encountered, the offending message is never retrieved from activemq which
causes our servers many troubles. I would like to reproduce the problem but
I am unable to do so and unsure of how to proceed to accomplish that goal.
Note that we do not use cms::TextMessage, but cms::BytesMessage to pack our
messages. 

We noticed in the web admin panel that the default behaviour of the library
is to include the computer name in the connection identification name (in
the form of "ID:mypcname-52983-1305654247574-1:0"). Since our clients come
from all around the world, some of the pc-name include UTF-16 characters.
Thinking that this could be the cause of our problems, we provided our own
identification string to the connection factory to avoid this issue, but the
issue is still seen at times. 

All of this to ask finally : does anyone have any idea on how I could
reproduce the problem, so that I can find a way around it (such as purging
the queue if necessary). Note also that I cannot contact the people running
the 'offending' clients. 

Thank you
Martin

--
View this message in context: http://activemq.2283324.n4.nabble.com/activemq-cpp-invalid-UTF-8-issue-tp3530020p3530020.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.