[
https://issues.apache.org/activemq/browse/AMQ-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eddie Epstein updated AMQ-1308:
-------------------------------
Attachment: HttpProblems.patch
Turns out there is another bug: the HTTP connector is completely broken for
multi-byte UTF-8 characters. The attached patch file includes fixes for both
the 64K limit (same fix as previously submitted) and for the bad decode of the
Http request body.
> Messages delivered from HttpTunnelServlet connected broker are limited to 64K
> bytes.
> ------------------------------------------------------------------------------------
>
> Key: AMQ-1308
> URL: https://issues.apache.org/activemq/browse/AMQ-1308
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 4.1.1
> Environment: Java consumer receiving messages using HTTP connector
> Reporter: Eddie Epstein
> Attachments: HttpProblems.patch
>
>
> In TextWireFormat.java: the methods writeUTF/readUTF are used in the code
> path to deliver messages from an HTTP connected broker.
> public void marshal(Object command, DataOutput out) throws IOException {
> out.writeUTF(marshalText(command));
> }
> public Object unmarshal(DataInput in) throws IOException {
> String text = in.readUTF();
> return unmarshalText(text);
> }
> These methods limit the max message size to 64K. Messages sent to an HTTP
> connected broker do not have the same limitation.
> Problem first reported in activemq-users with the subject
> "UTFDataFormatException in broker when using a http transportConnector".
> THanks,
> Eddie
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
