Messages delivered from HttpTunnelServlet connected broker are limited to 64K bytes.

• Key: AMQ-1308
• Type: Bug
• Status: Open
• Priority: Major
• Assignee: Unassigned
• Reporter: Eddie Epstein
• Component/s: Transport
• Affects Version/s: 4.1.1
• Fix Version/s: NEEDS_REVIEWED

Description

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

Comments

[Eddie Epstein]

TextWireFormat.patch fixes this issue. The data is written out in UTF8, which has the same size wire format as that previously created by writeUTF, and is preceded by a 4 byte length. There is an extra copy of the data created on both sending and receiving sides, but then again, it works.

[Eddie Epstein]

The patch submitted did in fact "work", but only for restricted message content: ascii characters.

Somewhat embarrassed,
Eddie

[Eddie Epstein]

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.