auto-ack
> mode, committing transactions or calling message.acknowledge()?
>
> On 8/1/07, ocoolio <[EMAIL PROTECTED]> wrote:
>>
>> Hello!
>>
>> I've just bumped into a strange problem. Sometimes, but not always, on a
>> fast producer/slow consumer case th
Hello!
I've just bumped into a strange problem. Sometimes, but not always, on a
fast producer/slow consumer case the consumer leaves exactly 500 messages in
the queue.
When restarting the consumer, the 500 is processed.
It happens when I send a lot (>100 000) of messages in the queue, but not
alw
Hi everyone!
I've found out that it's a postgres concurrency bug: postgres is just bad at
concurrent transactions updating the same row/page. Switching to DB2 Express
solved it.
Cheers.
ocoolio wrote:
>
> Hello!
>
> I have a bad performance problem:
>
> Im usin
anything I've tried with ActiveMQ. An uninstallation solved it :)
So, still no reply? :)
Thanks,
Adam
ocoolio wrote:
>
> Hello!
>
> Just a short extra info:
> the producer's first transaction is fast as usually! Then after commit, in
> the second transaction the
, new process I mean)
which can commit fast once, then slows down just like the first process.
What it has to do with processes?
What is happening?
Thanks,
Adam
ocoolio wrote:
>
> Hello!
>
> I have a bad performance problem:
>
> Im using NMS with .NET (C#) and two Qs:
> SUB
Hello!
I have a bad performance problem:
Im using NMS with .NET (C#) and two Qs:
SUBMITQ
DESTQ
A server component listens on SUBMITQ. When message received, transforms it
and submits it to DESTQ. All done in one transaction
(AcknowledgementMode.Transactional and sess.Commit(), PrefetchSize=1).
