As far as I know we never added such an option, but its needed so create a bug report in http://jira.jboss.com/jira/browse/JBAS
The availability is determined by being able to lookup and connect to the destination.
Scott, Adrian, thanks for que quick reply!
As JBAS-1645 already covers the problem pretty well, I wont create a new bug report as suggested by Scott. :-)
Is there any workaround we can take in order to prevent this situation in JBoss 3.2.6? We have that version in production environment and upgrading to 4.X it's something out os question. Also, JBoss 4.0.2, where the CreateJBossMQDestination option is supported, wasn't release yet!
We were trying to replicate the original problem in a test environment, but no "dummy" queue is created! Originally, we thought that the replacement queue was being created because of the connection loss, but removing the network cable from the machine where the MDB and the JMS proxy is running, caused nothing!
Can anyone explain me what's happening? What can cause the MDB to create a replacement queue in runtime and without deployments/changes going on?