Asynchoronous JMSWebService....getting no result

Question

Hi All,
Problem BackGround:
I am trying to run the asynchronous JMS WebService given in the example
http://otn.oracle.com/tech/webservices/htdocs/series/jms/content.html.
I have created the two destinations i.e a queue and a topic in the 9iDB as demonstrated in the exmaple.
The JMSWebService has two methods send() and recieve.
There is a MDB which acts as a JMSListener and listens at the Queue and then does the processing
of the messages found in the Queue in its onMessage(Element e) method.The MDB after doing the processing is
supposed to write the output of the processing in another destination...i,e a Topic .from this topic the
JMSWebService receive() reads the results posted by the MDB to the Topic.
Problem Context:
I have created a stub class out of the wsdl file and when i try to send a xml request wrapped in a w3c.Document
Element by invoking the send() method it writes to the Queue.After this the EJB Container needs to delegate the
posting of a new message in the Queue to the MDB which is not happening because the onMessage() of the MDB is
not invoked.The JMSWebService meanwhile invokes the read() method on the second destination i.e the Topic, where
the MDB is supposed to post the result of its onMessage().Since is finds nothing it waits in an infinite loop.
Queries:
Q1. Why is the onMessage() method not invoked by the container.
Q2. what are the pre-requisites for this..am i missing something.
Q3. How does a developer check the messages posted on a destination.
Its a bit urgent...iam in middle of putting a asynchronous framework for our on-going project.Any pointers
would be highly appreciated.
Rgds
Rishi.

Answer 1

Here are the gotchas that I encountered while writing the tutorial (I am to blame for any mistakes!):
1. Database version number. Make sure you have upgrade to 9.1.0.4 or 9.2.0.2. Unless that was done, I would always hang like you describe or get errors about wrong parameters being passed to AQ
2. In step 11, make sure you have the two queues displayed as shown in the picture. This also is a way to determine whether the messages made it into the queue by looking at the results of this query.
3. Make sure to deploy your MDB independent of the Web service. I sometimes deployed it as part of the Web service and this never took - step 16.
4. I found that if I re-deployed on top of a non-working example fixes, for some reason it did not work. I had to undeploy the configuration - both the Web service and the MDB to make sure I had a clean environment.
Unfortunately JDev does not have an automatic undeploy so you can use the command line version from OC4J or the delete directory/update-config-file way. The manual deletion is done as follows:
a. Delete the <oc4j_home>\j2ee\applications-deployment\mdb directory
b. Delete the <oc4j_home>\j2ee\applications-deployment\JMS-JMSWebService-WS directory
c. Delete the <oc4j_home>\j2ee\applications\mdb directory
d. Delete the <oc4j_home>\j2ee\applications\JMS-JMSWebService-WS directory
e. Delete the files:
<oc4j_home>\j2ee\applications\mdb.ear
<oc4j_home>\j2ee\applications\JMS-JMSWebService-WS.ear
f. Update the <oc4j_home>\j2ee\config\server.xml and delete the two lines:
     <application name="mdb" path="../applications/mdb.ear" auto-start="true" />
     <application name="JMS-JMSWebService-WS" path="../applications/JMS-JMSWebService-WS.ear" auto-start="true" />
The undeploy command for OC4J does this automatically for you, you just need to know the syntax.
Then re-deploy the MDB and Web Service.
5. When setting up the Web Service configuration make sure your second tab (step 21) really says Topic .... I accidently originally deployed using Queues for both send and receive and then ran into the problem in #4 which was redeploying with the correct configuration didn't work until I delete the original deployment - this might be a kink in my config but I thought it worthwhile mentioning.
Not sure if these help but hopefully.
Mike.