Performance Tuning for JMS consumption by MDB in JBoss
Issue
- AMQ messages consumption via MDB stuck and performance issues.
"default task-133" #1652 prio=5 os_prio=0 tid=0x000000000da2c000 nid=0x7209 in Object.wait() [0x00007f861411d000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:502)
at org.jboss.remoting3.util.BlockingInvocation.getResponse(BlockingInvocation.java:62)
- locked <0x00000007804662b0> (a java.util.ArrayDeque)
at org.wildfly.naming.client.remote.RemoteClientTransport.lookup(RemoteClientTransport.java:236)
at org.wildfly.naming.client.remote.RemoteContext.lambda$lookupNative$0(RemoteContext.java:190)
at org.wildfly.naming.client.remote.RemoteContext$$Lambda$901/1106462170.apply(Unknown Source)
at org.wildfly.naming.client.NamingProvider.performExceptionAction(NamingProvider.java:222)
at org.wildfly.naming.client.remote.RemoteContext.performWithRetry(RemoteContext.java:100)
...
Environment
- Red Hat JBoss Enterprise Application Platform (EAP) 7
- protocol "remote+http(s)" or "remote"
- Message Driven Bean (MDB)
- Enterprise Java Beans (EJB)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.