File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes JBoss/WildFly and the fly likes JMS DestinationManager Not Yet Installed Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "JMS DestinationManager Not Yet Installed" Watch "JMS DestinationManager Not Yet Installed" New topic

JMS DestinationManager Not Yet Installed

Vanessa Hall

Joined: Dec 11, 2003
Posts: 15
I am using JBoss version 4.0.1 and trying to use JMS queues.

I have my queues defined in a file under the deploy directory of my configuration called myqueue-service.xml, with entries like the following:

<mbean code=""
<depends optional-attribute-name="DestinationManager"></depends>

I copied my configuration from the "all" configuration so that I would have everything including (hopefully) JMS.

When I start my JBoss server, it lists all my queues and then this error message:


Attempts to send a message to the queue fail. Also, I noticed that the Getting Started guide says to use the jmx-console and click on the DestinationManager under, but I don't have a link for DestinationManager. How does the DestinationManager get installed/configured?

Any suggestions would be most appreciated,

Vanessa<br />SCJP,SCJD,IBM OOAD w/UML,Project+
Heonkoo Lee
Ranch Hand

Joined: Feb 10, 2005
Posts: 85
I had no problems following the examples in the start guide using version 4.0.2. There were some changes between 4.0.1 and 4.0.2.

And the following excerpt is from the guide's About this book section just after table of contents.
At the time of writing, the latest release is version 4.0.2. You should use this version or later with the examples.

FYI, unless you don't need clustering feature, avoid to use 'all' server type. 'default' mode also includes the JMS feature.

Good luck.

[ October 10, 2005: Message edited by: Heonkoo Lee ]
[ October 10, 2005: Message edited by: Heonkoo Lee ]
I agree. Here's the link:
subject: JMS DestinationManager Not Yet Installed
It's not a secret anymore!