Thanks for your reply, Hiram.
I have tried to configurate two brokers to use different databases. It was
not Master/Slave anymore. However, I got the same test result.
I have tried "Network of brokers" solution too. I met another issue which
was similar. Some messages were blocked in queue rand
If you disable database locking.. you need to use some other mechanism
to stop the slave broker from becoming active while the master is
online. If bother brokers become active on the same database scheme
data corruption can occur and will produce will produce a variety of
observable 'bugs'
On De
No. I am using AMQ4.1.1 stable with Spring2.0.
Thank you
Hiram Chirino wrote:
>
> You using AMQ 5.0.0 ??
>
> On Dec 14, 2007 6:23 AM, Dave Song <[EMAIL PROTECTED]> wrote:
>>
>> Hi,there
>>
>> I have a question when using JDBC Master/Slave. Some of the messages that
>> have sent to queue are
You using AMQ 5.0.0 ??
On Dec 14, 2007 6:23 AM, Dave Song <[EMAIL PROTECTED]> wrote:
>
> Hi,there
>
> I have a question when using JDBC Master/Slave. Some of the messages that
> have sent to queue are not consumed by messageListener
>
>
> I used ActiveMQ with spring. It worked perfect with one bro
