atani writes:
> 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 o
Thanks for closing the loop.
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
The experts in open source integration and messaging - http://fusesource.com
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Thu, Jul 28, 2011 at 2:03 AM, a
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,
you can always set some traces on
https://fisheye6.atlassian.com/browse/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/transport/stomp/LegacyFrameTranslator.java?hb=true
and see what's going on. Or create a test case similar to
https://fisheye6.atlassian.com/browse/activemq/
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
As far as I know unicode chars are two-bytes long, so that could be a cause.
You should convert it explicitly to byte array and then send it.
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
The experts in open source integration and messaging - http://fusesource.com
ActiveM
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
Hi,
Stomp protocol supports simple text messages and binary (byte) messages. See
in your Perl library how to send binary messages and convert your payload to
byte arrays and it should work (or use base64 encoding to convert it to
text).
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
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
10 matches
Mail list logo
