Are you using the java:/JmsXA adaptor?
Yes, I am.
are you using JBoss 4.0.2? We had the same problem some time ago. Actually, at least in our case, eventually MDB recovered, but it took about 20 mins for some reason.
Eventually we solved this by deploying MDB as ha-singleton. But if someone knows what the problem is I'd (still) be willing to know...
Yes, using 4.0.2, and we're using ha-singleton (as far as I can tell) i.e.:
app01:~/sptjboss/deploy-hasingleton/jms# ls jbossmq-destinations-service.xml jbossmq-service.xml mysql-jdbc2-service.xml uil2-service.xml jbossmq-httpil.sar jvm-il-service.xml mysql-jdbc-state-service.xml
app01:~/sptjboss/deploy/jms# ls hajndi-jms-ds.xml jms-ra.rar
No, I mean that we had to drop MDB load balancing altogether and deploy the MDB as ha-singleton (the EJB jar). The actual message queue is always ha-singleton, I think.
We had very limited time to solve this so didn't have time to research what's causing this...
IIRC, in JBoss 4.0.3 sp1 this worked ok, but other clustering problems there prevented our upgrade. If you have the possibility, you could try 4.0.4..?
But really I don't know what this was... Could even be some configuration error. And if you find a solution, I'd be willing to know... ;)