Sorry for the long delay responding. I resolved this issue, it was a bug in
our client code. A temporary queue was being cleaned up too early.
rajdavies wrote:
>
> Are you using networks as well ?
>
> On 22 Apr 2008, at 04:01, alanmc wrote:
>
>>
>> We're seeing the same behavior with 5.1.0.
Are you using networks as well ?
On 22 Apr 2008, at 04:01, alanmc wrote:
We're seeing the same behavior with 5.1.0. We're basically running
the
default broker configuration, with advisory support turned off. We
were
using 5.0.0, but saw memory leakage and wanted to try out 5.1.0 and
af
We're seeing the same behavior with 5.1.0. We're basically running the
default broker configuration, with advisory support turned off. We were
using 5.0.0, but saw memory leakage and wanted to try out 5.1.0 and after
switching over with the exact same configuration we started seeing
intermittent
Further to this I'd like to add that the broker shows that all 2
messages have been enqueued and dequeued. So the broker queue has no
messages remaining on it.
On Thu, Apr 17, 2008 at 2:24 PM, Dhruba Bandopadhyay <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Using spring 2.5.3 mdps, tomcat 6.0.16 and
