Hi,
I am trying to achieve request-response with ActiveMQ. This is how my
listener looks like. We are using JMSTemplate to send the messages. This is
the source code of producer who sends the messages and then wait for
specified time.
I just want to make sure whether we should use "send" call an
HI Agent,
Whats your amq broker url you specify.
When I had
I faced the same issue. I had 5 clients running with 15 maxconcurrent
connection. But instead of 75 conusers it actually increased to more than
120 consumers.
When I changes the url to
(Polling)
the number of consumers remained at
Hi Tim,
It depends on the day and time :(
It varies. Some times it stops at 16 messages to sometimes its 60. Sometimes
its jut 14.
I have re-written my clients annual Cancer DataBse build Architecture using
Camel, ActiveMQ, JTA, Spring and HIbernate. I have brought the processing
from 60 + hrs do
HI Tim,
I am still stuck on this issue. Any ideas please?
Thanks
Matt'M
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-Hangs-Large-volume-of-small-messages-Consumer-don-t-receive-msgs-tp4694305p4695944.html
Sent from the ActiveMQ - User mailing list archive at
Thanks for help, you are right. It'll exit as soon as it sends the message.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ClientConsumer-doesn-t-receive-the-message-tp4695859p4695943.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
The NMS.MSMQ provider is supported, and does compile with the latest NMS
1.7.0. It's just that a new binary hasn't been put out in a while.
On Apr 30, 2015 10:05 PM, "rjrizzuto" wrote:
> Thanks for the update. I am new to Apache.NMS and message oriented
> middleware in general. We currently are
I'm much more familiar with debugging the broker than the client, so I
don't know exactly how to look into the client to see what state it's in
(whether the missing messages are sitting in memory or were never received,
what the threads are doing, etc.). I'd start by taking a thread dump and a
mem
Thanks for the update. I am new to Apache.NMS and message oriented
middleware in general. We currently are using MSMQs in a product, and
finding it limiting. I'm looking at alternatives, and initally plan on
using Apache.NMS with Apollo. If Apache.NMS.MSMQ was supported, I was going
to use that
Have you stepped through it with a debugger? Do you successfully run to
the end of the client code?
If so, try running against a non-embedded broker. If you don't get
messages delivered there either but you've confirmed that you're really
executing the sendMessage() call, use the web console to
An NFS problem was the first thing I thought of when I saw out-of-order log
lines, especially since you've had that problem before. And this outage
lasted for over two minutes (which doesn't count as "slow" in my book;
that's "unavailable" or "down" to me), which is pretty crazy; hopefully
your op
We have a broker which is configured to use HTTP.
When a client wants to subscribe to a topic or sends a message on a queue,
it is issuing around 20 HTTP requests. Is it a normal behavior to send this
amount of HTTP requests just to subscribe to a topic or send a message or is
it something wrong i
I don't think the PersistenceAdapter is the problem. Could you post the
complete activemq.xml file?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Can-t-Start-ActiveMQ-after-Upgrade-from-5-10-to-5-11-tp4695913p4695925.html
Sent from the ActiveMQ - User mailing list archi
12 matches
Mail list logo
