Re: Broker Hangs after some time - or does nothing.

How about a stack trace on the client? Can you look for the consumer threads and see what they are doing? Note that with producers and consumers on the same connection, it's possible to reach a deadlock if producer-flow-control kicks in because the entire connection is blocked, not just the one p

Re: Runaway producer: Proper way to clean up a topic?

Perhaps persistence isn't needed for those messages at all. 30 seconds is bordering on too fast to restart a broker in many cases. With that said, it sounds like there may be at least one bug here. If a junit case can be written to prove this case, that would help a lot. Alternatively, a mini

Runaway producer: Proper way to clean up a topic?

Use deleteAllMessagesOnStartup option: https://activemq.apache.org/broker-uri.html From: jlindwall [via ActiveMQ] Date: 2014-02-08 05:26 To: kimmking Subject: Runaway producer: Proper way to clean up a topic? In a previous post I described a problem that occurred in a jdbc-backed 5.9.0 broker

Re: question about producer flow control

Also, what about the per-destination limits, are those enforced? -- View this message in context: http://activemq.2283324.n4.nabble.com/question-about-producer-flow-control-tp4677629p4677652.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: deleting durable subscriber exception

A data point: Just today I successfully deleted a durable subscriber using the hawtio console in 5.9.0 -- View this message in context: http://activemq.2283324.n4.nabble.com/deleting-durable-subscriber-exception-tp4677521p4677646.html Sent from the ActiveMQ - User mailing list archive at Nabble

Re: Broker Hangs after some time - or does nothing.

I didnt had slowConsumerStrategybefore but I thought if connection are not being closed properly this would help to shut those connection that's why I added it. Yes producers and consumer uses same connections. I dont see any problem with heap size or queue usage size. On Fri, Feb 7, 2014 at 3:

Runaway producer: Proper way to clean up a topic?

In a previous post I described a problem that occurred in a jdbc-backed 5.9.0 broker with a durable subscriber. The producers got way ahead of the consumer (which disconnected though did not unsubscribe). I had to restart activemq as it was hung. The messages in the topic had a 30 sec expiration

Re: Broker Hangs after some time - or does nothing.

slowConsumerStrategy definitely sounds like it could lead to what you see since it force closes the connection. How about the memory and store usage of the queue? Do you see messages on the broker that producer-flow-control is kicking in? I need to read up on slowConsumerStrategy to see how it w

Re: Broker Hangs after some time - or does nothing.

I am not using cpp client. I checked producer. It sends message to broker and doesnt return. So it is hanging at some point while sending. I see a message gets to borker but it never gets picked by consumer. One more thing I have slowConsumerStrategy defined. Do you think it might have anything t

Out of memory (Permgen?) + JMX attribute Health/CurrentStatus?

I have activemq configured with a durable subscriber to a topic backed by oracle. I left a publisher running at a rate of 100 msgs/sec; each msg is 1K. The msgs expire in 30 secs. The durable subscriber disconnected so, as expected, messages queued up in the db. After about 25 minutes I got an O

client failover to network of master/slave brokers

Trying to understand how to configure client failover connection to a network of masterslave brokers broker1 on Cluster 1: masterslave:(tcp://host1:61616,tcp://host2:61616,tcp://host3:61616) broker2 on Cluster 2: masterslave:(tcp://host4:61616,tcp://host5:61616,tcp://host6:61616) Is it possible

Re: Wire format negotiation timeout - auto retry

Good point. We will try the failover. Thanks -- View this message in context: http://activemq.2283324.n4.nabble.com/Wire-format-negotiation-timeout-auto-retry-tp4677624p4677630.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

question about producer flow control

i have a couple of questions about producer flow control. i've read a whole bunch of the documentation and various posts, but there are still some things not entirely clear to me. My first question is that i've seen various posts indicating that when it is enabled, it requires an extra thread _pe

Re: How to improve the performance of composite queue

If broker B is copying the message to 15 different queues from a source of 1 queue, then B will limit your performance at some point. Given that you are not seeing CPU reach limits (it would help to know what % is seen), I suspect PERSISTENT messages are being used, and so the real bottleneck is w

priorityBackup not supported with masterslave ?

Hi, randomize=false and priorityBackup are not working with the masterslave protocol - or is this by design ? A client-broker has a masterslave setup towards hostA and hostB. Would like to failover to hostB if ActiveMQ on hostA is not available, but if hostA becomes available again, would like

Re: Wire format negotiation timeout - auto retry

On 02/07/2014 10:49 AM, Jerry Cwiklik wrote: Under a heavy network load we occasionally are getting the dreaded "Wire format negotiation timeout..." exception when opening broker's connection in the client. We attempted to solve the problem with wireFormat.maxInactivityDurationInitalDelay=6

Wire format negotiation timeout - auto retry

Under a heavy network load we occasionally are getting the dreaded "Wire format negotiation timeout..." exception when opening broker's connection in the client. We attempted to solve the problem with wireFormat.maxInactivityDurationInitalDelay=6 url param, but even with that extended timeout

Re: [Apollo 1.6] MQTT via Websocket client stucks after connect

Could you post your test case? Does the MQTT over websocket example that comes with Apollo work for you? On Fri, Jan 24, 2014 at 11:08 AM, Finnfalter wrote: > I try to craft a client which sends MQTT messages as binary Websocket frames. > The client is based on Java/Paho

How to improve the performance of composite queue

Hi, We are using composite queue to make a message can be received by several services, but it seems that it has some performance issues. We applied two activemq brokers. We can call them A and B. A will connect to B by network connector. All message received in A will be send to B by the setting

Re: Logentry "Setup of JMS message listener invoker failed for destination"

Is there anything to help me on this as I get errors every 30 minutes on every client Thanks Thorsten Am 24.01.2014 15:53, schrieb artnaseef: > Wish I knew the internals there well enough to solve your problem. > > If I had this problem, I would pull down the sources for the Spring DMLC and > Act

Re: Errors because ActiveMQ is shutting down before CamelContext

Thanks for your reply. My config is already using the depends-on and the is defined before the element. The only difference I see is the missing within the element. But without that entry the CamelContext would not shutdown at all. As we are using a standalone ActiveMQ the useShutdownHook="fa