I suspect that the slowness has more to do with needing to set up and tear down a new HTTP connection for each message than with Jetty, though I'm still surprised it's that slow.
When you monitor the client and broker processes, what resource (CPU, memory, disk I/O, etc.) is the bottleneck, and for which process? On Dec 12, 2015 10:22 AM, "neo.li" <neo...@arcserve.com> wrote: > hello, > I am using http protocol for AMQ, but I find it is slower than using > tcp. I guess that the cause are these dependencise, like jetty. > I do no know how to optimize it, can u help me? > > Thanks > Neo. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/HTTP-transport-tp4014555p4704907.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
