Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 58018 invoked from network); 28 May 2008 10:04:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 May 2008 10:04:34 -0000 Received: (qmail 7958 invoked by uid 500); 28 May 2008 10:04:21 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 7941 invoked by uid 500); 28 May 2008 10:04:21 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 7930 invoked by uid 99); 28 May 2008 10:04:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 May 2008 03:04:21 -0700 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [164.164.106.53] (HELO mssbgw4.in.ness.com) (164.164.106.53) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 May 2008 10:03:29 +0000 Received: from mailsrv ([192.168.105.27]) by mssbgw4.in.ness.com with InterScan Messaging Security Suite; Wed, 28 May 2008 15:29:39 +0530 Received: from CAAMLAN ([125.16.140.43] RDNS failed) by mailsrv with Microsoft SMTPSVC(6.0.3790.3959); Wed, 28 May 2008 15:33:36 +0530 Reply-To: From: "adisesha" To: Subject: RE: Axis2 with JMS Transport Date: Wed, 28 May 2008 15:33:33 +0530 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0019_01C8C0D8.31FCF730" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <483BF98F.8000704@wso2.com> Thread-Index: Aci/8meHg6qNoumhT7OnAoTbIcTSzAAtzApg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Message-ID: X-OriginalArrivalTime: 28 May 2008 10:03:36.0311 (UTC) FILETIME=[18344070:01C8C0AA] X-imss-version: 2.051 X-imss-result: Passed X-imss-approveListMatch: *@in.ness.com X-Virus-Checked: Checked by ClamAV on apache.org ------=_NextPart_000_0019_01C8C0D8.31FCF730 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, I tried both options as suggested; still I am getting same error 1.urn:echoString 2. I would suggest the Synapse JMS transport implementation Can you please look in to this issue? Adi _____ From: Asankha C. Perera [mailto:asankha@wso2.com] Sent: Tuesday, May 27, 2008 5:38 PM To: axis-user@ws.apache.org Subject: Re: Axis2 with JMS Transport Hi Adi Can you go through the following links: http://marc.info/?l=axis-dev &m=120000476710938&w=2 http://www.nabble.com/Axis2-JMS-Transport-to-WebSphere-MQ-td14738492.html https://issues.apache.org/jira/browse/AXIS2-2816 Related questions have been asked on the axis dev and user lists and these should be helpful to you.. I am sorry I am unable to look at this issue in detail right now, but if the above does not help resolve your issue, please ping again.. asankha adisesha wrote: HI Asankha, Firstly thanks a lot for replying, I have been sending mails since last week & I got one from you :-) My Requirement: I want to use Axis2Service with jms & websphereMQ (Soap Message). In net I haven't seen any article related to this combination. Kindly correct me if I am wrong 1. Axis2.Xml (Created SampleQCF connection factory in MQ using JMSAdmin & sampleconfig.scp) com.ibm.mq.jms.context.WMQInitialContextF actory localhost:1414/SYSTEM.DEF.SVRCONN SampleQCF com.ibm.mq.jms.context.WMQInitialContextF actory localhost:1414/SYSTEM.DEF.SVRCONN SampleQCF 2. services.xml Echo Service urn:echoString Echo myQueueConnectionFactory SampleQueue 3. Echo.java (Axis2Service, i.e Created .class & then .aar & then copied it to tomcat.\axis2\....services) public class Echo { public String echoString(String in) { return "thanks:"; } } 4. Soap Message (I am putting directly in to Queue using "Put Text Message" in websphere MQ explorer) "http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC= "http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi= "http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd= "http://www.w3.org/2001/XMLSchema"StringWelcome to sample Let me know if I need synapse.jar & urn:echoString Thanks in advance Adi _____ From: Asankha C. Perera [mailto:asankha@wso2.com] Sent: Tuesday, May 27, 2008 4:45 PM To: axis-user@ws.apache.org Subject: Re: Axis2 with JMS Transport Adi Error: 1. Now when I put text message in to Queue "Echo" immediately it disappears from MQ. In tomcat log I can see "Exception in thread "JMSWorker-1" java.lang.NullPointerException at org.apache.axis2.transport.jms.JMSMessageReceiver.createMessageContext(JMSMe ssageReceiver.java:190)" What is the content type of your message? if your payload is text/plain, it could be due to a MessageBuilder problem. I would suggest the Synapse JMS transport implementation (which is an updated version of the same JMS transport available with Axis2) for you here. You can drop the Jar from here [http://repo1.maven.org/maven2/org/apache/synapse/synapse-transports/1.1.2/s ynapse-transports-1.1.2.jar] A typical configuration on your axis2.xml would be like: .... 2. If I put message using "standalonewmq" program, I can see "[ERROR] Cannot find operation : urn:mediate on the service Echo Exception in thread "JMSWorker-1" org.apache.axis2.transport.jms.AxisJMSException: Cannot find operation : urn:mediate on the service Echo at org.apache.axis2.transport.jms.JMSUtils.handleException(JMSUtils.java:464) at org.apache.axis2.transport.jms.JMSUtils.getSOAPEnvelope(JMSUtils.java:378)" With the JMS transport, unless you specify the operation name in your services.xml with the parameter "Operation", this defaults to an operation named "mediate" urn:sayHello asankha 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 MailAdmin@ness.com 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. ------=_NextPart_000_0019_01C8C0D8.31FCF730 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

I tried both options as suggested; = still I am getting same error

        =
1.<parameter =
name=3D"Operation">urn:echoString</parameter>

   2. I would suggest the Synapse JMS transport implementation

 

Can you please look in to this = issue?

 

Adi

From: Asankha C. Perera [mailto:asankha@wso2.com]
Sent: Tuesday, May 27, = 2008 5:38 PM
To: axis-user@ws.apache.org
Subject: Re: Axis2 with = JMS Transport

 

Hi Adi

Can you go through the following links:

http://marc.info/?l=3Daxis-dev&m=3D120000476710938&w=3D2
= http://www.nabble.com/Axis2-JMS-Transport-to-WebSphere-MQ-td147= 38492.html
https://issues.= apache.org/jira/browse/AXIS2-2816

Related questions have been asked on the axis dev and user lists and = these should be helpful to you..

I am sorry I am unable to look at this issue in detail right now, but if = the above does not help resolve your issue, please ping again..

asankha


adisesha wrote:

HI = Asankha,

 

Firstly thanks a lot for replying, = I have been sending mails since last week & I got one from you = J

 

= My Requirement: I want to use Axis2Service with jms & websphereMQ (Soap Message). In net I = haven’t seen any article related to this combination. Kindly correct me if I am = wrong

  1. Axis2.Xml = (Created SampleQCF connection factory in = MQ using JMSAdmin & = sampleconfig.scp)

<transportReceiver name=3D"jms" class=3D"org.apache.axis2.transport.jms.JMSListener">

    <parameter name=3D"myQueueConnectionFactory" = locked =3D"false">

            <parameter = name=3D"java.naming.factory.initial">com.ibm.mq.jms.context.WMQInitialContextFactory</parameter>

            <parameter = name=3D"java.naming.provider.url">localhost:1414/SYSTEM.DEF.SVRCONN</parameter>

          <parameter name=3D"transport.jms.ConnectionFactoryJNDIName">SampleQCF</parameter>

        = </parameter>

</transportReceiver>

<transportSender name=3D"jms"

         &n= bsp;           class=3D"org.apache.axis2.transport.jms.JMSSender">

      <parameter name=3D"myQueueConnectionFactory" = locked =3D"false">

        <parameter name=3D"java.naming.factory.initial">com.ibm.mq.jms.context.WMQInitialContextFactory</parameter>

        <parameter name=3D"java.naming.provider.url">localhost:1414/SYSTEM.DEF.SVRCONN</parameter>

        <parameter name=3D"transport.jms.ConnectionFactoryJNDIName">SampleQCF</parameter>

      </parameter>

    </transportSender>

  1. services.xml<= /o:p>

<service name=3D"Echo">

      <description>   Echo Service  </description>   =

     <operation = name=3D"echoString">

       <messageReceiver class=3D"org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>

             <actionMapping>urn:echoString</actionMapping>

     </operation>

  <parameter = name=3D"ServiceClass" = locked=3D"true">Echo</parameter>    =

  <parameter = name=3D"transport.jms.ConnectionFactory" locked=3D"true">myQueueConnectionFactory</parameter>

  <parameter = name=3D"transport.jms.Destination" = locked=3D"true">SampleQueue</parameter> 

</service>

  1. Echo.java (Axis2Service, i.e Created .class & then .aar & then copied = it to = tomcat…\axis2\....services)

public = class Echo

{

        &n= bsp;         public = String echoString(String = in)

        &n= bsp;               = {

        &n= bsp;               = return "thanks:";

        &n= bsp;               }     =

}

  1. Soap Message (I = am putting directly in to Queue using “Put Text Message” in = websphere MQ explorer)

<?xml version=3D"1.0" = encoding=3D"UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV=3D"http://schemas.x= mlsoap.org/soap/envelope/" xmlns:SOAP-ENC=3D"http://schemas.x= mlsoap.org/soap/encoding/" xmlns:xsi=3D"http://www.w3.or= g/2001/XMLSchema-instance" xmlns:xsd=3D"http://www.w3.org/2001/XM= LSchema"<SOAP-ENV:Body><ns:Echo xmlns:ns=3D"urn:echoString"><UserInfo>= ;String</UserInfo><Input>Welcome to = sample</Input></ns:Echo></SOAP-ENV:Body></= SOAP-ENV:Envelope>

 

Let me know if I need synapse.jar & =
<parameter name=3D"Operation">urn:echoString</parameter>
 
Thanks in =
advance
Adi















From: Asankha C. Perera [mailto:asankha@wso2.com]


Sent: Tuesday, May 27, =
2008 4:45
PM

To: axis-user@ws.apache.org

Subject: Re: Axis2 with =
JMS
Transport








 


Adi














Error:



1. Now =
when I put
text message in to Queue “Echo” =
immediately it
disappears from MQ. In tomcat log I can see “Exception in thread
"JMSWorker-1" =
java.lang.NullPointerException



     
at =
org.apache.axis2.transport.jms.JMSMessageReceiver.createMessageContext(JM=
SMessageReceiver.java:190)”





What is the content type of your message? if =
your payload is text/plain, it could be due to a MessageBuilder problem. =




I would suggest the Synapse JMS transport
implementation (which is an updated version of the same JMS transport =
available
with Axis2) for you here. You can drop the Jar from here
[http://repo1.maven.org/maven2/org/apache/synapse/synapse-transports/1.1.=
2/synapse-transports-1.1.2.jar]



A typical configuration on your axis2.xml would be like:

    <!--Uncomment this and configure as appropriate =
for JMS
transport support, after setting up your JMS environment (e.g. =
ActiveMQ)

    <transportReceiver name=3D"jms"
class=3D"org.apache.synapse.transport.jms.JMSListener">

        <parameter
name=3D"myTopicConnectionFactory">

            =
<parameter
name=3D"java.naming.factory.initial">org.apache.activemq.jnd=
i.ActiveMQInitialContextFactory</parameter>

            =
<parameter
name=3D"java.naming.provider.url">tcp://localhost:61616</=
parameter>

            =
<parameter
name=3D"transport.jms.ConnectionFactoryJNDIName">TopicConnec=
tionFactory</parameter>

        <parameter
name=3D"transport.jms.ConnectionFactoryType"
locked=3D"false">topic</parameter>

        </parameter>



        <parameter
name=3D"myQueueConnectionFactory">

            =
<parameter
name=3D"java.naming.factory.initial">org.apache.activemq.jnd=
i.ActiveMQInitialContextFactory</parameter>

            =
<parameter
name=3D"java.naming.provider.url">tcp://localhost:61616</=
parameter>

            =
<parameter
name=3D"transport.jms.ConnectionFactoryJNDIName">QueueConnec=
tionFactory</parameter>

        <parameter =
name=3D"transport.jms.ConnectionFactoryType"
locked=3D"false">queue</parameter>

        </parameter>



        <parameter
name=3D"default">

            =
<parameter
name=3D"java.naming.factory.initial">org.apache.activemq.jnd=
i.ActiveMQInitialContextFactory</parameter>

            =
<parameter
name=3D"java.naming.provider.url">tcp://localhost:61616</=
parameter>

            =
<parameter
name=3D"transport.jms.ConnectionFactoryJNDIName">QueueConnec=
tionFactory</parameter>

        <parameter
name=3D"transport.jms.ConnectionFactoryType" =
locked=3D"false">queue</parameter>

        </parameter>

    </transportReceiver>-->



....

    <transportSender name=3D"jms"
class=3D"org.apache.synapse.transport.jms.JMSSender">

        <!-- uncomment this and =
configure
to use connection pools for sending messages

        <parameter
name=3D"myTopicConnectionFactory">

           
<parameter
name=3D"java.naming.factory.initial">org.apache.activemq.jnd=
i.ActiveMQInitialContextFactory</parameter>

           
<parameter
name=3D"java.naming.provider.url">tcp://localhost:61616</=
parameter>

           
<parameter
name=3D"transport.jms.ConnectionFactoryJNDIName">TopicConnec=
tionFactory</parameter>

        </parameter>

    

        <parameter
name=3D"myQueueConnectionFactory">

           
<parameter =
name=3D"java.naming.factory.initial">org.apache.activemq.jnd=
i.ActiveMQInitialContextFactory</parameter>

           
<parameter
name=3D"java.naming.provider.url">tcp://localhost:61616</=
parameter>

           
<parameter
name=3D"transport.jms.ConnectionFactoryJNDIName">QueueConnec=
tionFactory</parameter>

        </parameter>

    

        <parameter
name=3D"default">

           
<parameter
name=3D"java.naming.factory.initial">org.apache.activemq.jnd=
i.ActiveMQInitialContextFactory</parameter>

           
<parameter
name=3D"java.naming.provider.url">tcp://localhost:61616</=
parameter>

           
<parameter
name=3D"transport.jms.ConnectionFactoryJNDIName">QueueConnec=
tionFactory</parameter>


        </parameter> -->

    </transportSender>
















2. If I put message =
using
“standalonewmq” program, I can see “[ERROR] Cannot =
find operation : urn:mediate
on the service =
Echo



Exception in thread
"JMSWorker-1" org.apache.axis2.transport.jms.AxisJMSException: =
Cannot
find operation : urn:mediate on the service =
Echo



     
at =
org.apache.axis2.transport.jms.JMSUtils.handleException(JMSUtils.java:464=
)



     
at =
org.apache.axis2.transport.jms.JMSUtils.getSOAPEnvelope(JMSUtils.java:378=
)”






With the JMS transport, unless you specify =
the
operation name in your services.xml with the parameter =
"Operation",
this defaults to an operation named "mediate"











<parameter =
name=3D"Operation">urn:sayHello</parameter>
 
asankha<=
/pre>















 

  
  
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 MailAdmin@ness.com
  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.

  		
 





 
------=_NextPart_000_0019_01C8C0D8.31FCF730--