activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Commented: (AMQ-1632) PrefetchSubscription may not wake up if messages delivered in transaction
Date Mon, 24 Mar 2008 22:45:32 GMT


David Jencks commented on AMQ-1632:

I talked with Hiram a bit and we decided that the real problem was that prefetchSize was being
calculated wrong.  MDBs instances for an activation spec all share a single multithreaded
consumer.  So the prefetch size ought to be maxMessagesPerSession * maxSessions, so each mdb
gets a chance at maxMessagesPerSession.  Previously prefetchSize = maxMessagesPerSession which
resulted in some mdbs never getting a chance to process anything if maxMessagesPerSession
< maxSessions.

Still haven't looked at trunk.

> PrefetchSubscription may not wake up if messages delivered in transaction
> -------------------------------------------------------------------------
>                 Key: AMQ-1632
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 4.1.1
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 4.1.2
> we noticed mdbs w/transaction on don't work if the prefetch size is less than the number
of sessions for the mdb.  There's an error in calculating the prefetchExtension in afterCommit
and there's no notification that it might be time to send more messages.  Apparently if the
prefetch size is large enough one of the earlier acks triggers delivery of the next batch.
> There are also a bunch of synchronization errors in some classes...

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message