Darryl,
First off (and I know you have probably already checked this but just
in case) have you uncommented the jms.xml attribute in your server.xml
file? Next if you are using Queues and QueueConnectionFactories inside
orion's jms implementation you do not need to use resource-ref tag in
your ejb-jar.xml your message-driven tag describes everything the
container needs to know about your administered objects resourc-ref is
used for attaching objects to the jndi tree but in this case all of the
objects declared in your jms.xml file are already on the jndi tree. So
try removing your resource-ref tags from your ejb-jar.xml and your
orion-ejb-jar.xml files.
Let me know if that works,
SaxPosition
Java Developer
Exim Technologies
131 Falls St. Suite 201
Greenville, SC 29607
On 10 Sep 2001 22:32:14 -0400, Darryl Dieckman wrote:
> I'm trying to setup a message driven bean and am getting an error
> during deployment that I don't understand. Here is the error the
> I am getting:
>
> Auto-deploying jmsdemoEjb.jar (ejb-jar.xml had been touched since the
> previous deployment)... done.
> Error deploying
> file:/C:/utils/oc4j/j2ee/home/applications/jmsdemo/jmsdemoEjb.jar homes: No
> javax.jms.Destination found at the specified destination-location
> (java:comp/env/jms/theQueue) for MessageDrivenBean cache/CacheMDBean
>
> This seems to be telling me that 'theQueue' is not of the type
> javax.jms.Destination, correct?
>
> Here is my jms.xml:
>
> <jms-server port="9127">
>
> <queue-connection-factory
> location="java:comp/env/jms/theQueueConnectionFactory" />
>
> <queue
> name="The Queue"
> location="java:comp/env/jms/theQueue" >
> <description>The JMS Demo Queue</description>
> </queue>
>
> <!-- path to the log-file where JMS-events/errors are stored -->
> <log>
> <file path="../log/jms.log" />
> </log>
> </jms-server>
>
> And here is my ejb-jar.xml:
>
> <message-driven>
> <ejb-name>cache/CacheMDBean</ejb-name>
> <ejb-class>com.optimaxx.server.rms.CacheMDBean</ejb-class>
> <transaction-type>Container</transaction-type>
> <acknowledge-mode>auto-acknowledge</acknowledge-mode>
>
> <message-driven-destination>
> <destination-type>javax.jms.Queue</destination-type>
> </message-driven-destination>
>
> <resource-ref>
>
> <res-ref-name>java:comp/env/jms/theQueueConnectionFactory</res-ref-name>
> <res-type>javax.jms.QueueConnectionFactory</res-type>
> <res-auth>Container</res-auth>
> </resource-ref>
>
> <resource-ref>
> <res-ref-name>java:comp/env/jms/theQueue</res-ref-name>
> <res-type>javax.jms.Queue</res-type>
> <res-auth>Container</res-auth>
> </resource-ref>
>
> </message-driven>
>
> And finally here is my orion-ejb-jar.xml:
>
> <message-driven-deployment name="cache/CacheMDBean"
>
> connection-factory-location="java:comp/env/jms/theQueueConnectionFactory"
> destination-location="java:comp/env/jms/theQueue" >
> <resource-ref-mapping name="java:comp/env/jms/theQueueConnectionFactory"
> />
> </message-driven-deployment>
>
> Any ideas? When I pull up a JNDI browser and look at what's registered, my
> browser
> shows theQueueConnectionFactory being of type
> com.evermind.server.jms.EvermindXAQueueConnectionFactory, and thQueue being
> of
> type com.evermind.server.jms.EvermindQueue. So I think everything is setup
> correctly,
> but I must be missing one silly little thing. help! ;)
>
> Darryl Dieckman
>
>
>
>
