Did you ever figure this out? We have the same problem.
Unfortunately not. The only way we got around it was to make sure that prodjboss1 starts before prodjboss2. It seems that the first node in the cluster receives messages that fall into the DLQ. While this is a hack, it does seem to work for us. Unfortunately it kills the whole point of messaging, which was to have a true peer messaging service. If you come up with anything better, please post it here. I'd love to know how to fix this.