MQ Channels are not managed objects as far as JMS is concerned. The concurrentconsumers apply only to your destination (queue). You can use concurrentconsumers on topics, but it doesn't make sense.
...
Type: Posts; User: springmk; Keyword(s):
MQ Channels are not managed objects as far as JMS is concerned. The concurrentconsumers apply only to your destination (queue). You can use concurrentconsumers on topics, but it doesn't make sense.
...
Did you try Spring 2.0.4 and above?
For message consumers (DefaultMessageListenerContainer), it is as simple as setting the following attribute:
<property name="exceptionListener" ref="exceptionListener"/>
ofcourse, the...
I haven't worked on Oracle AQ, but seems like you are trying to use XA transactions using the JmsTransactionManager rather than using the JtaTransactionManager.
That could be the issue here,...
I have seen for transacted sessions, the DMLC (DefaultMessagListenerContainer) is actually doing a commit and not a rollback as you were assuming (when the session timeout happens).
Maybe you...
Try the following:
1. Check the EMS sessions and see if they are still active when the DMLC hangs.
2. Bring up a profiler and check for thread deadlocks.
3. Try to enable DEBUG level logging for...
If your intention is to stop consuming messages altogether, why not call the DMLC's destroy() method or the shutdown() method?
Assuming that you are using AUTO_ACK for your DMLC, could it be XA overhead?
Maybe you should try without the XA and see if you are getting the same throughput. I would be interested to know the...
Yep, that's what I meant, when you set "receiveTimeout" to a -ve value (blocks forever).
I haven't used any XA features yet, but would like to know if someone has used it and their thoughts :)
...
I guess you are configuring the container with a "receiveTimeout" value, and that is why you see the "invokeListener" being called many times. Maybe that's the reason it was buring some CPU cycles.
...
Very good question.
Based on what I understand, for stand-alone java servers(non-J2EE), the DefaultMessageListenerContainer is the choice as it has support for XA.
However, as you mentioned,...
Mine is not exactly the same issue, but while working with DefaultMessageListener container in one of my messaging projects, I had this scenario when I was testing for failure conditions.
The...
Is there a sample spring configuration file for using JTA (JOTM) with the DefaultMessageListener? I would appreciate if someone can point me to a sample test configuration or something available on...