Is Message Driven Bean (MDB) restrained by the thread-pool definition in "ejb3" subsystem ?
Issue
- There is a
defaultthread-pool definition inejb3subsystem, is Message Driven Bean (MDB) restrained by this ?
<thread-pools>
<thread-pool name="default">
<max-threads count="10"/>
<keepalive-time time="100" unit="milliseconds"/>
</thread-pool>
</thread-pools>
- How to setup
bean-instance-pools/strict-max-poolandthread-pool/maxSessionfor MDB to improve the message consumption throughput ? - I find there is a
consumer-countproperty for my JMS queue, it is 15, how can I increase this to get more consumer instances to consume my messages faster ?
[standalone@10.10.10.10:9999 /] /subsystem=messaging/hornetq-server=default/jms-queue=MyQueue:read-resource(recursive=true, include-runtime=true)
{
"outcome" => "success",
"result" => {
"consumer-count" => 15,
"dead-letter-address" => "jms.queue.DLQ",
"delivering-count" => 0,
"durable" => false,
"entries" => ["java:jboss/exported/jms/queue/MyQueue"],
"expiry-address" => "jms.queue.ExpiryQueue",
"message-count" => 0L,
"messages-added" => 100L,
"paused" => false,
"queue-address" => "jms.queue.MyQueue",
"scheduled-count" => 0L,
"selector" => undefined,
"temporary" => false
}
}
- Is there a way of monitoring MDB's in JBOSS EAP6.X.
- We would like to monitor MDB pools defined and want to see if we are having issues. We also want to know what kind of errors we would see if MDB pools are exhausted.
Environment
- Red Hat JBoss Enterprise Application Platform
- 6.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
