Also, JBoss Messaging 1.0.1.SP4 doesn't seem to work with 4.2.0.CR1. It starts ok, but the example ejb3mdb fails with the following: | [java] javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: error unmarshalling return; nested exception is: | [java] java.lang.ClassNotFoundException: org.jboss.mq.referenceable.ObjectRefAddr (no security manager: RMI class loader disabled)] | What version of JBoss Messaging is recommended for use with JBoss 4.2.x? anonymous wrote : | While JBoss Messaging only becomes the default JMS provider from JBoss AS 4.2.1 and JBoss 5.0, production users on JBoss AS 4.0.x can still take advantage of the performance improvements by easily replacing the JBossMQ module with JBoss Messaging. | Since JBoss Messaging will become the default JMS provider very soon, shouldn't it integrate fairly well at this point? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026351#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...