Hi Rob,
Yes - I haven't seen the issue in my application since updating. Many
thanks again.
Cheers,
David
Rob Davies wrote:
Hi David,
I had a test case that periodically could reproduce this - it now can't
after ensuring references are always freshed in the Kaha reference store
part of A
Hi David,
I had a test case that periodically could reproduce this - it now
can't after ensuring references are always freshed in the Kaha
reference store part of AMQ Store. Is your application now fixed?
thanks,
Rob
On Oct 8, 2007, at 2:48 AM, David Sitsky wrote:
Hi Rob,
Looks like you
Hi Rob,
Looks like you have fixed this issue - many thanks.
Cheers,
David
Rob Davies wrote:
Hi David,
I've had a look through the log you've attached to AMQ-1445 - but I
think i'll need some more information to successfully resolve whats
going on. Obviously there's an attempt to retrieve a
Hi David,
I've had a look through the log you've attached to AMQ-1445 - but I
think i'll need some more information to successfully resolve whats
going on. Obviously there's an attempt to retrieve a message that's
already been deleted - I just need to find out why ;)
Could I trouble you
Hi Rob,
I think I spoke too soon. While using AMQ store fixed the initial issue
I was dealing with, it seems to have other issues in my application,
where I see the following message before everything hangs:
RecoveryListenerAdapter - Message id ID... could not be recovered from
the data sto
AMQ Store is the combination of the journal (which itself now uses
Kaha) and Kaha to store message references
cheers,
Rob
http://rajdavies.blogspot.com/
On Oct 4, 2007, at 8:04 PM, Daryl Richter wrote:
On Oct 3, 2007, at 7:30 AM, Rob Davies wrote:
Do you get the same using AMQ store (t
On Oct 3, 2007, at 7:30 AM, Rob Davies wrote:
Do you get the same using AMQ store (the default in 5.0) - its the
prefered store over kaha in ActiveMQ 5.0
Hmm. When I start a very recent (revision 581630) build of ActiveMQ
with completely default config I get (among others) the following
ter.
>
Sorry I just see this issue is resolved -- haven't tried it yet though.
Pieter
--
View this message in context:
http://www.nabble.com/Duplicate-message-delivered-to-consumers-on-queue-with-kaha-persistence-tf4560327s2354.html#a13034801
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
rectly as well, but I still believe
this is a bug in the Kaha adapter.
Regards,
Pieter
--
View this message in context:
http://www.nabble.com/Duplicate-message-delivered-to-consumers-on-queue-with-kaha-persistence-tf4560327s2354.html#a13034799
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi Rob,
Looks like the AMQ store works correctly - thanks for the advice.
Cheers,
David
Rob Davies wrote:
Do you get the same using AMQ store (the default in 5.0) - its the
prefered store over kaha in ActiveMQ 5.0
cheers,
Rob
http://rajdavies.blogspot.com/
On Oct 3, 2007, at 8:50 AM,
Do you get the same using AMQ store (the default in 5.0) - its the
prefered store over kaha in ActiveMQ 5.0
cheers,
Rob
http://rajdavies.blogspot.com/
On Oct 3, 2007, at 8:50 AM, David Sitsky wrote:
I have discovered an issue with the latest activemq 5.0 (revision
581510) which seems
I have discovered an issue with the latest activemq 5.0 (revision
581510) which seems to have been present for some time, at least for the
last month.
I have an application using transactions, and kaha persistence, and two
consumers feeding off a queue.
I sometimes see the same message being
12 matches
Mail list logo
