axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "adisesha" <>
Subject RE: Axis2 with JMS Transport
Date Tue, 03 Jun 2008 08:58:43 GMT

Anthony, I tried setting JNDI using MQ explorer, resulted in same error. Can
you give sample Axis2 client? 



From: Anthony Bull [] 
Sent: Friday, May 30, 2008 4:10 AM
Subject: Re: Axis2 with JMS Transport


Your axis2.xml looks correct - as long as your MQ is setup as a JNDI
provider.  Note that you can setup all your JMS stuff in MQ explorer
visually if you have the correct support packs installed - you don't need to
use the JMS admin tool.

I just tried your approach with publishing a message via MQ explorer and got
the same error:

Exception in thread "JMSWorker-1" java.lang.NullPointerException

This looks like an error in Axis 2 - so it looks like you'll have to publish
via an actual Axis 2 client.  I had a look at the Axis 2 code and its
something around the reply-to code - including a reply-to SOAP addressing
header didn't resolve it.

adisesha wrote: 

No, output can be sent to other queue also. For now the problem I have is reading queue is guess. We can think of sending o/p to same/other
queue later.

1. java.lang.NullPointerException at

May be the settings I used are wrong? Can you cross check the axis2.xml &
services.xml I have sent?



From: Anthony Bull [] 
Sent: Thursday, May 29, 2008 11:19 AM
Subject: Re: Axis2 with JMS Transport


MQ is good as the JNDI provider.  It sounds like you want your web
service to respond to the same queue?  I've only done asynchronous web
services over JMS, for synchronous I use HTTP, so can't help on responding
to the same queue - i.e. all my JMS web services are one way traffic from MQ
to Axis2/Tomcat.  If you have addressing information in the SOAP header in
your message envelope, then it should resolve your issue where it can't find
the correct operation to invoke on your web service.  Certainly, if you can
configure axis2 to suit all your needs then go with that - I tend to keep
environment specific JMS stuff out of my axis2.xml files because I have to
deploy to the customer development, testing and production environments and
don't like constantly changing axis2.xml files with every deployment.

adisesha wrote: 

We want to work on existing settings, with out need of code. i.e create WS
with one method, & set connection details in axis2.xml & then create JNDI
either in tomcat or in websphereMQ. Now when user puts info in MQ
automatically WS should be called & then return xxx to o/p Queue. 

For this sequence I don't see the need of code if axis2 works correctly.
What is your opinion on this?


--------------------------------------------------------------------- To
unsubscribe, e-mail: For additional
commands, e-mail:


The information contained in this communication is intended solely for the use of the individual
or entity to whom it is addressed and others authorized to receive it.   It may contain confidential
or legally privileged information.   If you are not the intended recipient you are hereby
notified that any disclosure, copying, distribution or taking any action in reliance on the
contents of this information is strictly prohibited and may be unlawful. If you have received
this communication in error, please notify us immediately by forwarding this email to
and then delete it from your system. Ness technologies is neither liable for the proper and
complete transmission of the information contained in this communication nor for any delay
in its receipt.
View raw message