activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-2609) HTTP transport fails with java.io.UTFDataFormatException exception for messages larger than 64k
Date Tue, 16 Feb 2010 13:40:40 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57596#action_57596
] 

Timothy Bish commented on AMQ-2609:
-----------------------------------

Have you tried using the 5.4 SNAPSHOT, the fix for AMQ-1308 addresses this same issue.

> HTTP transport fails with java.io.UTFDataFormatException exception for messages larger
than 64k
> -----------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2609
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2609
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.3.0
>         Environment: win32
>            Reporter: Krzysztof Szyntar
>
> When using activemq with http transport and trying to receive large messages (~100KB),
 the operation fails and the following exception is in the log file:
> java.io.UTFDataFormatException: encoded string too long: 219486 bytes
> 	at java.io.DataOutputStream.writeUTF(DataOutputStream.java:347)
> 	at java.io.DataOutputStream.writeUTF(DataOutputStream.java:306)
> 	at org.apache.activemq.transport.util.TextWireFormat.marshal(TextWireFormat.java:44)
> 	at org.apache.activemq.transport.http.HttpTunnelServlet.doGet(HttpTunnelServlet.java:86)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> 	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
> 	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
> 	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
> 	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726)
> 	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> 	at org.mortbay.jetty.Server.handle(Server.java:320)
> 	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
> 	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:828)
> 	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:514)
> 	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
> 	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
> 	at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
> 	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)
> It may be caused by DataOutputStream.writeUTF implementation being limited to 64k string
length.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message