Rob,
This looks to have done the trick. I've tested with our application, which
was hitting the problem every time, and it is fine.
Thanks for your attentiveness to this issue!
Kevin
rajdavies wrote:
>
> Hopefully!
> On 16 Apr 2008, at 18:39, yaussy wrote:
>
>>
&g
Rob,
So, I would find this under the 5.2 SNAPSHOT tomorrow morning (USA central
standard time)?
Kevin
rajdavies wrote:
>
> yep - being able to reproduce - this is now fixed in trunk - but too
> late for the 5.1 release
>
> thanks,
>
> Rob
>
> On 16 Apr 2
thing more reproduceable,
while adding some debug code to IndexManager.
Kevin
yaussy wrote:
>
> Still working on a consistent test case. But, I've run into something
> along the way, and I'm not sure if it's related to the original exception
> I've logged here. I wa
nsumer / supplier test code?
Kevin
rajdavies wrote:
>
> ok - thx for checking! - let me know when you have a test case
>
> On 15 Apr 2008, at 15:06, yaussy wrote:
>
>>
>> Bad news - problem still happens with "5.2" snapshot dated 4/13. I
>> did not
&g
any more debug
information. I have not been able to reproduce it with a test program yet.
yaussy wrote:
>
> Rob,
>
> This is good news - I will try using last nights snapshot.
>
> I started out using AMQMessageStore, but I've never had good performance
> luck with AM
such as a few hundred events per second to a handful of
consumers, on one of our clusters. It has not performed well, whereas Kaha
by itself is excellent.
Kevin
rajdavies wrote:
>
>
> On 14 Apr 2008, at 14:07, yaussy wrote:
>
>>
>> I have not been able to reproduc
I have not been able to reproduce this problem outside of our application,
but I'm still trying.
Anyway, I'm using regular Kaha persistence (not AMQMessageStore), and during
a Durable Topic test, I'm eventually getting the following exception in the
AMQBroker, after which the broker stops forward
A while back, with AMQ 4.2, which is now 5.0, I ran into a similar problem.
I don't recall that there was a thread leak, but there was definitely a
memory leak. Check out AMQ-1202. Again, this may be different now with the
more recent 5.0. I've not taken 5.0 yet, as I made a handful of changes
What is the purpose of the prefetchExtension counter in
TopicSubscription.java (AMQ 4.2)? Not sure what is trying to be
accomplished, but one way or another, the way it is implemented / used is
causing the isFull method to never return true. In fact, PrefetchSize in
jconsole shows an ever increa
