To solve the particular problem above, copy/paste the org.jboss.deployment.MainDeployer-xmbean.xml file from jboss-4.2.3.GA\server\default\conf\xmdesc\ to jboss-4.2.3.GA\server\<NEW PROFILE>\conf\xmdesc\ However, a new list of problems will appear. Those can be solved by placing org.jboss.deployment.JARDeployer-xmbean.xml in the same directory mentioned above, AND placing the following JARs in the jboss-4.2.3.GA\server\<NEW PROFILE>\lib\ directory: antlr.jar bsh.jar commons-codec.jar hibernate3.jar quartz.jar I now have a server profile built from the provided minimal profile in which Tomcat, JMX, JBM1.4.2 and JBESB4.4 are installed. I have a couple of warnings: 14:50:31,140 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover AND 14:50:31,140 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing BUT, I can send messages from a producer that pulls data from an eXist db to a queue / ESB / queue to a receiver with no immediate problems. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214286#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...