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,
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 upg
I've been meaning to change this for a while:
http://jira.jboss.com/jira/browse/JBAS-1645
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872764#3872764
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872764
---
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.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopi
