JBossDeveloper

Hi Asim,

you're right, MDB really does not get deployed after failback. Also I can see another issue. If I redeploy the MDB manually (after live activates) then it does not start consuming messages from queue. I tried to consume messages from the same queue by standalone JMS client - but it could not consume any message as well.  Messages seem to be stuck in the queue. Sending new messages to this queue is working well but still cannot consume any.

I did a thread dump of the server to check if there is a dead lock or something but nothing seems to be waiting. I'll return to it on Monday.

Thanks,

Mirek

Ok, the issue that I could not receive the messages was between my chair and monitor. So the issue is just deployment that MDB does not get deployed.

I did some tries to workaround it but without success. I can see 2 possible improvements here:

a) If deployment failed to deploy and later all missing dependencies for deployment are corrected then deployment would redeploy automatically. b) Add annotation/descriptor which would specify deployment dependency to JNDI resource. For example for JMS queue or connection factory. There was annotation @org.jboss.annotation.ejb.Depends; in JBossAS 6 which allowed to that but it seems those were dropped.

Hi Asim,

I've created 2 new jiras to improve this behavior:

[WFLY-7394] Redeploy deployment if all missing dependencies for deployment are corrected

[WFLY-7395] Allow to provide deployment dependency to JNDI resource

they might get rejected or not implemented but both seem to be a nice feature/enhancement.

Thanks,

Mirek