I was trying to use Message Size related stats provided in ActiveMQ v5.10 and
found that header size is 1028 bytes (send message of different sizes and
size returned by API is 1028 bytes more). I am not able to understand why
size is this.
Is it prefixed? Is there anyway to see what constitute
Thanks.
Lot of amq switches
The trick is to set broker url =
failover:(tcp://localhost:61616)?jms.rmIdFromConnectionId=truejms.prefetchPolicy.all=1randomize=falsejms.redeliveryPolicy.maximumRedeliveries=0
to disable client side redelivery, and let the broker take control.
2014-09-03
Hi,
We are using ActiveMQ in several of our production systems. It works
very well, but we would like to make the broker fail-over, for when the
broker application (which runs seperately of the consumers on other
machines) crashes.
To do this, we are already able to create a JDBC-based or a
first , I have copied file activemq.xml from src package.
---
?xml version=1.0 encoding=UTF-8?
beans
xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://www.springframework.org/schema/beans
Once in a while we're getting following exception in AMQ logs and there is no
other way than purging the queue. How can we overcome this issue? Is it okay
to use LevelDB store now? Any answers?
2014-09-01 13:25:52,065 [erSimpleAppMain] DEBUG AbstractRegion - localhost
adding destination:
Hi, I am using Fuse 6.1 and credentials for Active MQ in preference. Still I
am getting this error.
10:52:36,045 | INFO | pool-17-thread-1 | BrokerService|
146 - org.apache.activemq.activemq-osgi - 5.9.0.redhat-610379 | Apache
ActiveMQ 5.9.0.redhat-610379 (amq,
On 09/01/2014 10:09 AM, nfx wrote:
Once in a while we're getting following exception in AMQ logs and there is no
other way than purging the queue. How can we overcome this issue? Is it okay
to use LevelDB store now? Any answers?
2014-09-01 13:25:52,065 [erSimpleAppMain] DEBUG AbstractRegion -
The problem is that it's not possible to reproduce this issue. It happens
once a week and log messages don't hold any errors.
Some more insights to problem:
- XXX.index and XXX.log files exist
- XXX.index probably has some dirty changes inside
- XXX.log which is supposed to be used for recovery,
I am seeing activemq threads being blocked on
org.apache.activemq.transport.tcp.TcpTransport.run()
Could somebody help me understand what this means?
I suggest looking at replacing the broker for generating the messages with
simple Camel routes using the timer or quartz endpoints. Clustering scheduled
jobs is always a challenge. If you run Camel in a Karaf-based container
(ServiceMix, JBoss Fuse, etc) you can setup the containers to be
What version of ActiveMQ jars do you have listed in your dependencies?
On Sep 1, 2014, at 9:37 AM, b-brother yingchao@alibaba-inc.com wrote:
first , I have copied file activemq.xml from src package.
---
?xml version=1.0 encoding=UTF-8?
beans
Hi James-
ActiveMQ 5.5.1 is quite aged at this point. Any reason you aren’t looking at a
newer version?
Transactions and connection pooling is tricky— are you doing XA or JMS Local?
I suggest trying to get it all working, then tune.. CACHE_NONE first.
-Matt
On Sep 2, 2014, at 7:05 AM, James
12 matches
Mail list logo
