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 fo
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-
Are there any php transport implementations that support heart-beating?
We use php5-stomp and when connection lost consumer just hangs and i can't
catch that from my code and reconnect.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/PHP-transport-implementations-supporti
correct ConnectionFactory's url is
failover:(http://localhost:8015?maxReconnectDelay=1&timeout=3)
--
View this message in context:
http://activemq.2283324.n4.nabble.com/AMQ-uses-http-protocol-will-become-slow-tp4704905p4704906.html
Sent from the ActiveMQ - User mailing list archive at N
hi all,
when my AMQ uses tcp protocol, I find the transmission is very fast and
Q is not pending. but when I use http/https instead of tcp, Q will be
slower, if I send 1 ObjectMsg every 3s, Q will be pending. if I send 1
ObjectMsg every 2s, Q will dead.
I do not know the root cause. I gue
