Hi,

thanks for raising the issue. Is there a chance you can provide a
reproducible test case?

Cheers
--
Dejan Bosanac - http://twitter.com/dejanb

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net


On Tue, Feb 16, 2010 at 10:05 AM, muadd <kszyn...@gmail.com> wrote:

>
> Hi,
>
> I've encountered similar problem with http transport. When I try to get a
> message with 100KB+ payload (tried TextMessage and MapMessage), I get:
>
> 2010-02-16 09:37:28,147 | WARN  | / | org.mortbay.log | btpool0-1 - /
> 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)
>
> I tried 5.2.0 and 5.3.0 versions. If I switch to tcp transport it works ok.
> I'll submit Jira for this because I don't think there is one already.
>
> thanks
>
>
>
> Dejan Bosanac wrote:
> >
> > Hi,
> >
> > The max message size use can send over HTTP is limited by max POST size
> > Jetty server will accept. I thinks it's 1MB by default, so it shouldn't
> > cause the problem you're seeing. Can you reproduce the problem reliably
> > (with the test case ideally) and file it as a Jira issue?
> >
> > Cheers
> > --
> > Dejan Bosanac
> >
> > Open Source Integration - http://fusesource.com/
> > ActiveMQ in Action - http://www.manning.com/snyder/
> > Blog - http://www.nighttale.net
> >
> >
> > On Thu, Feb 12, 2009 at 12:45 PM, libert <a...@a-l.fr> wrote:
> >
> >>
> >> Hi,
> >>
> >> I'm trying to send a BytesMessage (size : 1 MB max) using HTTP transport
> >> but
> >> it does not work.
> >>
> >> In the ActiveMQ console, I get this :
> >> java.io.UTFDataFormatException: encoded string too long: 208555 bytes
> >>
> >> If I switch to openwire TCP, program is working fine ...
> >>
> >> Is there any message size limit on HTTP transport ?
> >>
> >> I'm using ActiveMQ 5.2.0 win32
> >>
> >> Thanks.
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/Bytesmessage-and-http-transport-tp21974419p21974419.html
> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
> > -----
> > Dejan Bosanac
> >
> > Open Source Integration - http://fusesource.com/
> > ActiveMQ in Action - http://www.manning.com/snyder/
> > Blog - http://www.nighttale.net
> >
>
> --
> View this message in context:
> http://old.nabble.com/Bytesmessage-and-http-transport-tp21974419p27605308.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>

Reply via email to