Hello, I am in the same situation as you where on March, I am migrating the implementation of jms from jboss mq to jboss messaging in a jboss 4.2.x
My difference with you is that the error appears when I am starting the second server before I had problems with de data base and I restart one of them. If I start both servers in normal conditions I don’t have any problems.
But, if I analyse the error and code I must have the same problem as you because I use EJB3 in jboss 4.2.x and with jboss messaging.
Could you say me witch changes did you did with de class DestinationManagerJMSDestinationFactory?
So thanks.