Does fixing the activeMQ bug https://issues.apache.org/activemq/
browse/AMQ-1618 help with any of these problems? I would find it
very difficult to analyze other failures until this is fixed.
thanks
david jencks
On Mar 12, 2008, at 9:44 AM, Tomasz Mazan wrote:
Hi guys.
I still got problems with stopping of delivering messages to MDB. I
suspect
it's question of configuration of my thread pools, mdb instance
limit per
MDB container etc.
Could anyone help me to do it properly?
Let's say I got:
1. MDB class A1.. An - for each I have to define
maxMessagesPerSessions and
maxSessions
2. Each separable subset of [A1 .. An] use one of Resource Adapter
where
_each_ of RA uses it's own workmanager and ConnectionFactory - with
single-pool attributes MAX-SIZE and MIN-SIZE
3. Every workmanager has attribute minPoolSize and maxPoolSize
4. There is attribute Default\ MDB\ Container.InstanceLimit
5. Is there any other value for (i.e.) global thread (or
connection) pool to
set?
Please, help me. There's is many cases where messages are 'trapped' in
queue.
--
View this message in context: http://www.nabble.com/Relation-
between-MDB%27s-instances%2C-instanceLimit-and-threads-
tp16007429s134p16007429.html
Sent from the Apache Geronimo - Users mailing list archive at
Nabble.com.
