May be client is using StockQuoteService and the server is listening on queue/StockQuoteService. Start jboss and the server and see whether service is listening to the destination. You can check that from the JBoss jmx-console, going to the relevent destination page and checking the receiversCount or something. Also check where client is sending the message from the console by the message count listed in the relevent destination.
Upul On Thu, Apr 3, 2008 at 6:05 PM, Ines Dannehl < [EMAIL PROTECTED]> wrote: > Hi Asankha, > > > > I can't find out the correct full JNDI name of the queue. I get the log > message: > > > > 2008-04-03 14:23:24,659 INFO > [org.jboss.mq.server.jmx.Queue.StockQuoteService] Bound to JNDI name: > queue/StockQuoteService > > > > But when I use queue/StockQuoteService as JNDI name it's still the same. > > > > I also wonder that there is no exception when I give a sure non-existing > JNDI name in the configuration you recommended (e.g. BLABLA). > > > > Do you have some experiences with the JBoss configuration? > > > > Regards > > Ines > > > ------------------------------ > > *Von:* Asankha C. Perera [mailto:[EMAIL PROTECTED] > *Gesendet:* Mittwoch, 2. April 2008 10:44 > *An:* [email protected] > *Betreff:* Re: AW: SOAP with JMS and JBoss > > > > Ines > > It seems like the request was sent to the right queue but the webservice > is not listening to the queue. I did no special configuration for the > webservice. Therefore I think it should listen to a queue with the service > name (StockQuoteService). Do I need a special message receiver? The > StockQuoteService from the Axis2 example has the message receiver > > Yes, now its getting into a Queue, but the Queue name is not properly > bound to the service. On your services' services.xml add the following > parameter > > <parameter name="transport.jms.Destination" > locked="true">thefullJNDINameOfYourDestination</parameter> > > > > Ref: http://ws.apache.org/axis2/1_3/jms-transport.html > > > > asankha > > >
