On 8/25/06, Manuel Teira <[EMAIL PROTECTED]> wrote:
James Strachan escribió:
> So a few things going on here.
>
> * on a restart not all queues appear in JMX until they are actually
> used. This page describes why along with explaining how to work around
> this
> http://incubator.apache.org/activemq/how-do-i-create-new-destinations.html
>
Anyway, it seems that if there are messages in the database for the
SUNRECV queue, it is created by ActiveMQ on restart. With the cases:
1.-The messages are sent to the bridged broker.
2.-The messages are not sent to the bridged broker, and on a new message
arriving, older are dropped.
I find (2) to be a problem.
I don't understand what (2) means. Could you try explain that again please?
> * the database is not always in sync with the broker as we use a high
> performance journal; so the database is checkpointed periodically and
> is usually a bit behind the broker. You can avoid this by disabling
> the high performance journal (but its pretty slow to do that). Here's
> an example config if you want
> http://incubator.apache.org/activemq/jdbc-master-slave.html
Well, I've found the reason for this. It's because messages sent with
the JMX sendTextMessage operation are not persistent, and that's the
reason they're not inserted in the database (I think).
I don't follow. Persistence is defined not by the type of the message
but by the deliveryMode of the MessageProducer
> BTW I looked at the code for the JMS bridge and if a connection is
> lost with the remote broker, the bridge just stops - so no messages
> should be lost. Though it will require a bounce of the broker to
> reconnect.
I'm going to open a JIRA for this.
Great
--
James
-------
http://radio.weblogs.com/0112098/
