Re: Inactivity Monitor Forces bridge to shutdown

Hi,, Did you find any solution to the issue mentioned? Kindly let me know if you have. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

RE: Broker hitting max memory with large persistent queue

Have you checked out http://activemq.apache.org/message-cursors.html 4.1.1 seems to store some kind of message reference in memory so broker may run out of memory even if persistence is enabled. Maarten Dirkse-2 wrote: Allright, the sleuthing continues. I did a heap dump of the broker vm

JMS transaction deadlocks producer

Hi All, I am using AMQ 4.1.1 but this issue can also be seen in 5.0 If a producer chooses to participate in a JMS transaction we found that AMQ will store all the messages in memory till producer calls commit (even if JMS_DELIVERY_MODE of each message is PERSISTENT and broker has persistence

Activemq message selectors performance

) Thanks, Vinod -- View this message in context: http://www.nabble.com/Activemq-message-selectors-performance-tp16562491s2354p16562491.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Journaled jdbc persistence and broker restarts

HI All, I am using AMQ 4.1.1 with journaled jdbc persistence (which I gather is the fastest form of persistence in 4.1.1) I observe that when I have around 100K messages (each of size 100KB) queued up and I try to stop the broker using a ^C it takes more then one hr to stop. During this time,

Re: Consumer forwarding and failover

I tried following test to see how network of brokers react to broker failure and new broker discovery (bringing dead broker back) : Based on following test I think ActiveMQ-5.0-SNAPSHOT is handling this senario properly. Not sure abt 4.1.1. 2 store and forward brokers (B1, B2) 3 consumer (C1

Re: ActiveMQ Sending Performance

Ur sender code looks fine to me, are u sure ur messages are not being persisted by ActiveMQ. Persistence can slow down send considerably. Check ur ActiveMQ config file for persistence. http://activemq.apache.org/persistence.html andriy_heikal wrote: Hi Guys, I'm newbie on ActiveMQ. I've

Re: network of Brokers

Network of brokers ensure that ur messaging topology doesnt have a single point of failure and distributes load across the network of brokers. If there is only a single broker and for some reason that broker goes down then ur clients (producers/consumers) will not be able to send/receive new

Re: ActiveMQ for dummies

://vinod:61616 --to-consume=2000 --sleep-millis=100 --q-name=testQ Producer --broker-url=tcp://vinod:61616 --batch-size=400 --sleep-millis=100 --msg-size=1024 --q-name=testQ Here sleep-millis param means consumer will take so many millis to consume a message and producer will sleep for so many

Store and forward brokers issue

networkConnectors !-- by default just auto discover the other brokers -- networkConnector name=default-nc uri=multicast://default/ /networkConnectors /broker Thanks, Vinod -- View this message in context: http://www.nabble.com/Store-and-forward-brokers-issue