I downloaded the 5.6 source and added trace logging in StompWireFormat.java
and LegacyFrameTranslator.java and it's starting to look like there's
something happening between the Net::Stomp library and the ActiveMQ input
stream - that something is somehow related to the use of SSL. The problem
onl
Hi Dejan,
UTF-8 encoded characters can be 1 to 3 bytes in length; characters less than
or equal to 127 (hex 0x7F) is one byte, 128 to 2048 (0x07FF) is two bytes,
2049 to 65535 (0x) is three bytes. e.g. the smiley character in my test
encodes to three bytes (0xE2, 0x98, and 0xBB) and the Ö e
Thanks, Dejan. Fiddling with sending a "BytesMessage" results in another
interesting error.
When I send a plain ASCII-containing bytes message specifying a
content-length equal
to the length of the message body not including the terminating null byte,
everything
is fine. But when I send a messag
Oops, somehow lost the ability to attach the script to the previous post, so
here it is.
http://activemq.2283324.n4.nabble.com/file/n3679606/stomptest3.pl
stomptest3.pl
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Non-ASCII-messages-via-Stomp-being-dropped-or-mangled-
Hi all, I'm running into a problem sending Stomp messages with anything
other than ASCII text in them. I'm connecting from a perl client and I'm
trying to send simple textual messages to a single queue, some of these
messages contain latin1 characters, others unicode characters, others plain
asci