Could this be a bug? Or am I missing something?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/What-is-the-correct-way-to-throttle-ActiveMQ-producers-who-send-persistent-messages-in-batches-to-a--tp4701204p4701233.html
Sent from the ActiveMQ - User mailing list archive
I see no references to a Map or to a field called callbacks in
http://www.grepcode.com/file/repo1.maven.org/maven2/org.apache.activemq/activemq-client/5.11.1/org/apache/activemq/usage/MemoryUsage.java
Can you give more details of what you're seeing?
On Aug 20, 2015 1:25 PM, yang.yang.zz
Hey James.
The PFC documentation is very clear that async producers will not be
notified when PFC kicks in, and that per-producer PFC will not be used. It
does not say that whole-connection PFC won't kick in, and I believe that it
will, as I outlined in my first response. From the Advantage
Since this is happening in production, I assume it's not acceptable to
attach a debugger and set a breakpoint on the line where the exception is
thrown. If you could, that would let you step into the
MemoryUsage.isFull() call and see what's going on, but it'll hang the
broker when it happens and
It looks like the mailing list ignored or rejected my response below. It
also didn't accept your email with the second stack trace (which is the
only relevant one). Weird.
Looking at the second stack trace, it's even more clear that this error has
nothing to do with client connection removal.
You'll see messages in the broker logs if PFC is kicking in.
Are full GCs taking place? 10 to 15 minutes seems like far too long for
that to be likely as an explanation, but it's worth checking.
You can always use a profiler and take thread dumps to figure out what's
going on when this happens.
The broker can't discard the message till all subscribers have consumed it,
so a single slow consumer will result in increased memory/store usage and
eventually PFC. You could set up a slow consumer abortion strategy if
you're worried about that possibility.
On Aug 20, 2015 10:13 AM, Daniel
The producer continues to send and message build in the queue. The consumers
resume on their own usually and empty the queue but a while later the same
thing happens again.
--
View this message in context:
Have you configured your machine to allow for JMX connections? You might
see if you can connect via something like jconsole and see what the state
of memory and cpu is, the active threads, etc.
On Thu, Aug 20, 2015 at 8:49 AM Richard Sinek rsi...@intouchgps.com wrote:
The producer continues to
As we can see that before 'ArrayIndexOutOfBoundsException' we got below logs:
20150817 18:24:42.582 EDT (ActiveMQ NIO Worker 6)
org.apache.activemq.leveldb.util.Log$class#debug 112 DEBUG] - on rollback,
the transaction TX:ID:app1.net-38906-1439632105449-7:13:42 does not exist
That's why I am
I have an issue where my consumer stops receiving messages for 10 or 15
minutes, then resumes. This is load dependent - the faster the message rate
the more frequently it occurs. We have assumed that it is an issue at the
consumer level but have not been able to pin down the cause.
However,
Does the producer stop sending messages or is the producer still sending
and the Consumer is hung?
If the producer is blocked and waiting it could be flow control kicking on:
http://activemq.apache.org/producer-flow-control.html
On Thu, Aug 20, 2015 at 11:37 AM, Richard Sinek
Hi:
When I tested our product wtih ActiveMQ 5.11.1, we observed a high memory
usage spike in a ActiveMQ broker process.
This broker has 9G memory configured. It's using memoryCursor to cache
messages. But for each Queue it has a memory limit for 200M.
Then we observed a high memory usage spike
According to the following issue:
https://issues.apache.org/jira/browse/AMQ-5176?jql=project%20%3D%20AMQ%20AND%20text%20~%20%22java%208%22
It is my understanding that Apache Open Source ActiveMQ 5.10, 5.10.2 and
5.10.3 support Java 8 JDK.
and it is my understanding that Apache Open source
On 08/20/2015 04:54 PM, Abrahan wrote:
According to the following issue:
https://issues.apache.org/jira/browse/AMQ-5176?jql=project%20%3D%20AMQ%20AND%20text%20~%20%22java%208%22
It is my understanding that Apache Open Source ActiveMQ 5.10, 5.10.2 and
5.10.3 support Java 8 JDK.
and it is my
Yes, we have done that and there doesn't seem to be any sign of trouble.
Threads are ~ 100 and memory is well below maximum.
The way the system works we have producers publishing to a single queue, the
consuming application then processes those messages and publishes to a bunch
of secondary
Oooh, that's a good idea to add another subber. I may be able to try that.
Also, could something on the client side cause a backup? Or will the broker
just fall through if a client hangs?
On 8/20/15, 7:18 AM, tbai...@gmail.com on behalf of Tim Bain
tbai...@gmail.com on behalf of
17 matches
Mail list logo
