RE: Axis2 with JMS Transport
Finally it's an error in Axis2. If so do you have any idea who will fix it when? publish via an actual Axis 2 client - means we should use Axis2 client to put message in to MQseries? Or else use it directly to contact Axis2? Can you please provide more info or any reference? Mean while I will try using INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory suggested by others at http://www.mqseries.net/phpBB2/viewtopic.php?p=216263#216263 _ From: Anthony Bull [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2008 4:10 AM To: axis-user@ws.apache.org 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 at org.apache.axis2.transport.jms.JMSMessageReceiver.createMessageContext(JMSMe ssageReceiver.java:190) at org.apache.axis2.transport.jms.JMSMessageReceiver.access$000(JMSMessageRecei ver.java:50) at org.apache.axis2.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageRecei ver.java:246) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run Task(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:595) 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 w.r.to reading queue is guess. We can think of sending o/p to same/other queue later. 1. java.lang.NullPointerException at org.apache.axis2.transport.jms.JMSMessageReceiver.createMessageContext(JMSMe ssageReceiver.java:190) May be the settings I used are wrong? Can you cross check the axis2.xml services.xml I have sent? _ From: Anthony Bull [mailto:[EMAIL PROTECTED] Sent: Thursday, May 29, 2008 11:19 AM To: axis-user@ws.apache.org Subject: Re: Axis2 with JMS Transport MQ 6.0.2.3 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? _ From: Anthony Bull [mailto:[EMAIL PROTECTED] Sent: Thursday, May 29, 2008 3:43 AM To: axis-user@ws.apache.org Subject: Re: Axis2 with JMS Transport 1. Add the ws-addressing support to your service and your client. (go to the axis 2 site to see how to do this). This may/should help in getting your web service to be able work out what method needs to be invoked. 2. When you are configuring the JMS sender - your connection details (provider factory class, URL etc) can be configured in the code instead of in the axis2.xml. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Disclaimer 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 [EMAIL PROTECTED
RE: Axis2 with JMS Transport
No, output can be sent to other queue also. For now the problem I have is w.r.to reading queue is guess. We can think of sending o/p to same/other queue later. 1. java.lang.NullPointerException at org.apache.axis2.transport.jms.JMSMessageReceiver.createMessageContext(JMSMe ssageReceiver.java:190) May be the settings I used are wrong? Can you cross check the axis2.xml services.xml I have sent? _ From: Anthony Bull [mailto:[EMAIL PROTECTED] Sent: Thursday, May 29, 2008 11:19 AM To: axis-user@ws.apache.org Subject: Re: Axis2 with JMS Transport MQ 6.0.2.3 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? _ From: Anthony Bull [mailto:[EMAIL PROTECTED] Sent: Thursday, May 29, 2008 3:43 AM To: axis-user@ws.apache.org Subject: Re: Axis2 with JMS Transport 1. Add the ws-addressing support to your service and your client. (go to the axis 2 site to see how to do this). This may/should help in getting your web service to be able work out what method needs to be invoked. 2. When you are configuring the JMS sender - your connection details (provider factory class, URL etc) can be configured in the code instead of in the axis2.xml. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Disclaimer 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 [EMAIL PROTECTED] 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.
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 at org.apache.axis2.transport.jms.JMSMessageReceiver.createMessageContext(JMSMessageReceiver.java:190) at org.apache.axis2.transport.jms.JMSMessageReceiver.access$000(JMSMessageReceiver.java:50) at org.apache.axis2.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:246) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:595) 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 w.r.to reading queue is guess. We can think of sending o/p to same/other queue later. 1. java.lang.NullPointerException at org.apache.axis2.transport.jms.JMSMessageReceiver.createMessageContext(JMSMessageReceiver.java:190) May be the settings I used are wrong? Can you cross check the axis2.xml services.xml I have sent? From: Anthony Bull [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 29, 2008 11:19 AM To: axis-user@ws.apache.org Subject: Re: Axis2 with JMS Transport MQ 6.0.2.3 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 dont see the need of code if axis2 works correctly. What is your opinion on this? From: Anthony Bull [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 29, 2008 3:43 AM To: axis-user@ws.apache.org Subject: Re: Axis2 with JMS Transport 1. Add the ws-addressing support to your service and your client. (go to the axis 2 site to see how to do this). This may/should help in getting your web service to be able work out what method needs to be invoked. 2. When you are configuring the JMS sender - your connection details (provider factory class, URL etc) can be configured in the code instead of in the axis2.xml. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Disclaimer 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 [EMAIL PROTECTED] 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. -- Anthony - Anthony Bull Senior Developer Black Coffee Software Ltd PO Box 10-192 The Terrace Wellington, New Zealand [EMAIL PROTECTED] Ph +64 4 472 8818 Fax +64 4 472 8811 - www.bcsoft.co.nz --- This email may contain co
