I have done performance testing for kahadb, leveldb and replication leveldb.
Details:
*Scenario: *
> ActiveMQ : 5.10
> Machine : Unix
> I tested performance by sending messages to the broker continuously with
> any sleep or wait on producer side and measure the throughput by messages
> sent per se
Hi,
If I specify "replica=1" in the replicated leveldb configuration; one node
can become the master even if other nodes are down. And other nodes will
replicate from master once they come up. I have couple of questions for this
configuration.
1. Here replicas = 1: The master will store the upda
I have a question about Topic names. I am attempting to create an MQTT
Topic queue with the name:
test/testing
in the Apollo UI console. I see a 500: Server error message displayed
after clicking the submit button. I looked and found the following error
in the log file:
2014-12-02 15:27:13,
Hello,
Over several thousands of messages consumed, occasionally I got the
following WARN in the log.
/[ActiveMQMessageConsumer:1434] ( ) acking duplicate delivery as poison,
redelivery must be pending to another consumer on this connection,
failoverRedeliveryWaitPeriod=0. /
(1) What is duplic
Thanks!
I think I'll leave everything as it is. Given what's going on with this
particular network environment, I'd wager it was a hiccup. I haven't seen this
error since then.
Steve
Good point Tim. One example where those log lines is important to diagnose -
when a broker is running out of memory (usually due to a slow-consumer
problem).
--
View this message in context:
http://activemq.2283324.n4.nabble.com/when-should-you-set-maxInactivityDuration-0-tp4688281p4688291.htm
As Art says, the advantages are minor, and the disadvantages (such as the
inability to detect disconnections due to network problems) are not. So
your default should be to use a non-zero value unless you come up with a
clear reason why you think a value of zero would be better for you, and
clearly
Setting maxInactivityDuration to 0 disables the activity monitor. The
advantages include reducing the overhead when there are large numbers of
idle connections, and eliminating forced disconnects on slow connections
that are otherwise active.
These seem like minor advantages. The overhead is rea
Try looking at XMPP, such as OpenFire
(http://www.igniterealtime.org/projects/openfire/).
It is specifically designed for chat (point-to-point -- i.e. two parties, or
group chat). JMS is not designed for chat. For example, JMS does not
provide facilities for storing messages (and it's a bad prac
What method is used to simulate the network outage to the NFS server?
If the original master loses network connection to the NFS server, writes
should fail. Although there could be NFS settings that affect just how it
operates (e.g. sync vs async and timeouts). It's been a long time since I
twea
Some time ago I noticed a dropped connection, and saw an error along the lines
of "Channel was inactive for too long". I made note of various folks here and
elsewhere saying that the way to prevent this from happening is adding
wireFormat.maxInactivityDuration=0
So now I've got the time to lo
11 matches
Mail list logo