Thank you Adrian. I will post to the WSMQ forum.
My concern is this is not a WSMQ issue. There could be some settings inside the JBoss container that removes an idle MDB after a certain period. Are you sure this is not the case? Thanks for your help.
Positive. WSMQ has (or at least used to have) a default "one hour timeout"
on all listeners after which it stops delivering messages.
We are using MQ 5.3 on solaris. I wrote a java program that keeps receiving with wait on a queue and it works fine even after 10 hours of idle time.
Using MDB inside JBoss, does it ultimately makes client connection to MQ and do a receive with unlimited wait time?
Thanks for your help.
The MDB uses a ConnectionConsumer not a MessageConsumer so your comparison is
invalid though probably not completely worthless.
This is all IBM code anyway. If I did debug the problem, there is nothing I can do to fix it.
I would do it if you bought a support contract, but debugging non JBoss
software is way beyond the scope of a free help forum.
I appreciate all your time. I just need to make sure there is no setting inside JBoss that I am not aware of. I can focus on debugging the non-JBoss portion of the code myself.