Yes, I think I have an idea.
You probably applied the "manual procedure" on a clustered (not default) intial
configuration.
A clustered configuration has its JBossMQ instance deployed in
deploy-hasingleton/jms,
instead of deploy/jms, hence the conflict.
I actually haven't extended the installation procedure for the clustered ("all")
configuration because that configuration comes with a lot of baggage that is
not needed to run Messaging.
However, it's not a big deal to do it. I plan to include the modified procedure
with the documentation we release with 1.0.1 (end of next week). If you want
to rush things, add a JIRA task, we tend to get those done first.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3935624#3935624
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3935624
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
