An additional note:
Up to and including installing JBoss Messaging 1.4.2.GA (and making the necessary adjustments), everything works perfectly ...
I wrote a program to deploy a queue and a producer to send xml data from an eXist DB to a receiver ... and another program to destroy the queue ... works like a charm.
Also, the JMX console (JMX Agent View) is showing in a browser.
To solve the particular problem above, copy/paste the org.jboss.deployment.MainDeployer-xmbean.xml file from
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,
placing the following JARs in the jboss-4.2.3.GA\server\<NEW PROFILE>\lib\ directory:
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
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.