Is there a way to configure JBoss to load MDB's at startup? By default the
MDB's are not created until a message hits the queue.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186007#4186007
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=po
Is there a way to configure JBoss to load MDB's at startup? By default the
MDB's are not created until a message hits the queue.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185769#4185769
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=
I created a JIRA issue to attach the full thread dumps:
http://jira.jboss.org/jira/browse/JBMESSAGING-1159
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106766#4106766
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=410
During volume testing with 2 nodes I now see these deadlocks in the thread
dumps (platform AS 4.2.0.GA_CP01, JBM snapshot_stable 12-Nov-2007):
Node 1:
Found one Java-level deadlock:
| =
| "Messaging Timeout(3)-266":
| waiting to lock monitor 0x7548e274 (object
The DefaultMessageListenerContainer relates to the JmsTemplate in that it is
equally resource intensive with a cache level of CACHE_NONE. Our client works
with CACHE_CONSUMER, but with a level of CACHE_SESSION or less, consumption
halts and we quickly receive the following stacktrace in the serv
There is only one case where we use JmsTemplate to consume messages, and that
is for the purpose of aggregation. For that case we may use
jmsTemplate.execute(SessionCallback action, boolean startConnection) to
circumvent the resource impact of jmsTemplate.receive().
We also use JmsTemplate as
