s and you generally
wouldn't expect message properties to affect the order of delivery unless
you're using a selector.
On Tue, Feb 26, 2008 at 8:59 AM, Ben Chobot <[EMAIL PROTECTED]> wrote:
Why wouldn't you want it to be this way?
Roger Hoover wrote:
Using STOMP o
Why wouldn't you want it to be this way?
Roger Hoover wrote:
Using STOMP on AMQ 5, if I enqueue some persistent and non-persistent
messages and then consume them, they don't get consumed in the order in
which they were produced. The non-persistent messages are delivered first
(with their relati
Rob Davies wrote:
Writes are usually fast because of the journaling part of the default
message store
Which version are you using btw?
I'm using 5.0, and like I said in another email, when writing safely
(syncOnWrite="true") performance isn't all that good without write
caching. How do you d
Well, I'm just starting to play with ActiveMQ myself, but just as a
datapoint, I found that when writing every durable message to disk using
the default Kaha store in 5.0, I maxed out at transferring a whopping 14
40KB msgs/s. That's using a single, low-performance 7200RPM drive
without write c
I think I need
to run the test for longer time to get a fair result. When consuming the
messages from the server, the speed is getting down much faster. Is 50 msg/s
in normal condition?
Ben Chobot wrote:
What is the underlying I/O system like for your broker? As I understand
the persistenc
What is the underlying I/O system like for your broker? As I understand
the persistence layer for ActiveMQ, 3,500 durable messages a second
sounds too good to be true, assuming you're writing them safely.
zaoliu wrote:
I am tuning the performance of ActiveMQ broker for Queue by using three
sep
I'm reading over Sun's JMS tutorial and it mentions several times that
JMS (and therefore ActiveMQ) can keep out duplicate messages if
consumers set their session to AUTO_ACKNOWLEDGE. But I don't see how
that's always the case. Consider this timeline:
1. Consumer registers an asynchronous list
I had precisely the same problem with a postgres datastore. Switching to
the default kaha store made the problem go away.
tuomo wrote:
Hello,
I have a very strange problem.
I'm running a basic instance of AMQ 5.0.0 with connection to a DB2-database.
The broker runs in persistent-mode. My prod
le session and only create a new
session if you require that some be transactional or use client ack
instead of auto ack etc.
Regards
Tim.
On Tue, 2008-02-19 at 12:25 -0800, Ben Chobot wrote:
Hey everybody. I'm playing around with the CMS client for ActiveMQ 5,
and I'm having s
Hey everybody. I'm playing around with the CMS client for ActiveMQ 5,
and I'm having some threading issues. It seems that every time I start a
session, I get a new thread to handle that session. Clearly, this won't
scale to lots of sessions, and in fact my OS won't let me create more
than 300 t
10 matches
Mail list logo
