[
http://jira.jboss.com/jira/browse/JBESB-1056?page=comments#action_12377302 ]
Martin Vecera commented on JBESB-1056:
--------------------------------------
Ok, as you can see from my previous comment I realized that the problem was caused by
wrong paths configuration during lookup for JBoss Messaging. Even if esb-config.xml will
be deleted there is still an error in product/tools/console/management-esb/build.xml path
definitions (this dwelling '../' in ${install.dir}).
Management console in ESB server uses JBossMQ instead of JBoss
Messaging
------------------------------------------------------------------------
Key: JBESB-1056
URL:
http://jira.jboss.com/jira/browse/JBESB-1056
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Tooling
Affects Versions: 4.2.1 IR1
Environment: Sun JVM, ant 1.6.5
Reporter: Martin Vecera
Assigned To: Mark Little
I've checked out the ESB from trunk and run 'ant dist'.
The file product/build/jbossesb-server-4.2.1IR1/server/default/deploy/management.esb
contains jbmq-queue-service.xml instead of jbm-queue-service.xml. This is because
product/tools/console/management-esb/build.xml is checking for JBoss Messaging in deploy
directory before Messaging is installed there and therefore it switches to JBossMQ. Using
JBossMQ in management.esb causes an exception being thrown during server startup.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira