Return-Path: X-Original-To: apmail-axis-c-user-archive@www.apache.org Delivered-To: apmail-axis-c-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ACE1310F3A for ; Wed, 10 Jul 2013 06:05:49 +0000 (UTC) Received: (qmail 75898 invoked by uid 500); 10 Jul 2013 06:05:49 -0000 Delivered-To: apmail-axis-c-user-archive@axis.apache.org Received: (qmail 75712 invoked by uid 500); 10 Jul 2013 06:05:48 -0000 Mailing-List: contact c-user-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache AXIS C User List" Delivered-To: mailing list c-user@axis.apache.org Received: (qmail 75693 invoked by uid 99); 10 Jul 2013 06:05:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jul 2013 06:05:48 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rajika.kumarasiri@gmail.com designates 209.85.220.181 as permitted sender) Received: from [209.85.220.181] (HELO mail-vc0-f181.google.com) (209.85.220.181) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jul 2013 06:05:42 +0000 Received: by mail-vc0-f181.google.com with SMTP id lf11so4898880vcb.40 for ; Tue, 09 Jul 2013 23:05:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=68fJh9TvrjDuICeC4VFiT/mJg6uU/dAKSK6gvEisM5c=; b=mI5Zwcdbg9nAcBsE/BjrOLAPHwP8ELVA+0EqzStwUi5e9tE/jParTIGXkdeAvJ3Fzq pmbKGUaBJh3wQFKg9dzTD+5vCb8ovtXt4M4Tm4Is3lYoXMtr48oHUhn2nsQYLxdCc+np CwFXljNcSutCH6h4kHymm5hnCcxojoaHPQGHtSz+ddxXIoYE5GE8ysVOXFIiJvxRkaiF /rxVWQbb6NBuA03a+GZuOhqHm8PKmA83m8ZWNhGbfoLlj02P8voiHjSsbeg8q2weRZSO p5ldrBrp/3R5gbADAFeMPg4uR52qxp6ok4iDRQGPDI7dMoNePx2Uys8Ymvqc/YQ4eni1 L5gA== MIME-Version: 1.0 X-Received: by 10.58.128.71 with SMTP id nm7mr2542937veb.51.1373436322180; Tue, 09 Jul 2013 23:05:22 -0700 (PDT) Received: by 10.220.75.147 with HTTP; Tue, 9 Jul 2013 23:05:22 -0700 (PDT) In-Reply-To: References: Date: Wed, 10 Jul 2013 02:05:22 -0400 Message-ID: Subject: Re: Axis2c-1.6.0: Issue with sending "No Error" soap fault From: Rajika Kumarasiri To: Apache AXIS C User List Content-Type: multipart/alternative; boundary=047d7b60518c1af45d04e1221090 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b60518c1af45d04e1221090 Content-Type: text/plain; charset=ISO-8859-1 The request hasn't even reached the service. You need to check why the request is not dispatched to service. Check the server log. As I said as far as client is concern the invocation is successful with a fault. Rajika On Wed, Jul 10, 2013 at 1:48 AM, Pavani J wrote: > But service is not failing and so service is not setting any fault or > error. And yet service skeletons on_fault code is called. > > Thanks, > Pavani > > > On Tue, Jul 9, 2013 at 10:39 PM, Rajika Kumarasiri < > rajika.kumarasiri@gmail.com> wrote: > >> axis2_status_t returns the status of the invocation. As you have seen the >> invocation has been successful with a fault. >> >> Rajika >> >> >> On Wed, Jul 10, 2013 at 1:02 AM, Pavani J wrote: >> >>> Hi, >>> >>> I am developing a web service using Axis2c-1.6.0 based on WSDL generated >>> C code and I am on server side. >>> >>> I have some ADB APIs that return axis2_status_t. >>> Even if these APIs are returning AXIS2_SUCCESS (no other errors from >>> server side business logic), it calls service skeletons on_fault code and >>> sends "No Error" soap fault. >>> >>> Please see below for packet trace for response >>> >>> ***Server*** >>> HTTP/1.1 500 Internal Server Error >>> Date: Tue Jul 9 12:10:05 2013 GMT >>> Server: Axis2C/1.6.0 (Simple Axis2 HTTP Server) >>> Content-Type: application/soap+xml;charset=UTF-8 >>> Transfer-Encoding: chunked >>> >>> >>> >>> >>> >>> soapenv:Sender >>> >>> >>> >> xml:lang="en">No Error >>> >>> >>> myService|http://com.abcd.efg.hijk/2.0/ failed >>> >>> >>> >>> >>> >>> Below is ADB function for one such API: >>> >>> axis2_status_t axis2_skel_myService_myTask(const axutil_env_t *env , >>> axis2_msg_ctx_t *msg_ctx, >>> adb_cancelTask_t* >>> _cancelTask, >>> >>> axis2_skel_myService_myTask_fault *fault ); >>> >>> >>> Looks like it cannot handle when ADB does not have any output params to >>> return (so it returns NULL) and status is AXIS2_SUCCESS. >>> >>> Changing WSDL is not an option for my project. >>> >>> My problem is different from the issue at >>> https://issues.apache.org/jira/browse/AXIS2C-1279 >>> >>> I apologize if this question is already answered and please point me to >>> that link. >>> >>> This is kind of a blocker for me right now. Any help is greatly >>> appreciated. >>> >>> Thanks, >>> Pavani >>> >>> >> > --047d7b60518c1af45d04e1221090 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
The request hasn't even reached the service. You need = to check why the request is not dispatched to service. Check the server log= . As I said as far as client is concern the invocation is=A0successful=A0wi= th a fault.=A0

Rajika


<= div class=3D"gmail_quote">On Wed, Jul 10, 2013 at 1:48 AM, Pavani J <jpa= vani07@gmail.com> wrote:
But service is not failing = and so service is not setting any fault or error. And yet service skeletons= on_fault code is called.

Thanks,
Pavani


On Tue, Jul 9, 2013 at 10:39 PM, Rajika = Kumarasiri <rajika.kumarasiri@gmail.com> wrote:
axis2_status_t returns the status of the invocation. As yo= u have seen the invocation has been successful with a fault.=A0

Rajika


On Wed, Jul 10, 2013 at 1:02 AM, Pavani J <jpavani07@gmail.com> wrote:
Hi,

I am developing a web service using= Axis2c-1.6.0 based on WSDL generated C code and I am on server side.
=

I have some ADB APIs that return axis2_status_t.= =A0
Even if these APIs are returning AXIS2_SUCCESS (no other errors from s= erver side business logic), it calls service skeletons on_fault code and se= nds "No Error" soap fault.

Please see be= low for packet trace for response

***Server***
HTTP/1.1 500 Internal Server Err= or
Date: Tue Jul =A09 12:10:05 2013 GMT
Server: Axis2C/= 1.6.0 (Simple Axis2 HTTP Server)
Content-Type: application/soap+x= ml;charset=3DUTF-8
Transfer-Encoding: chunked

<soapenv:Envelo= pe xmlns:soapenv=3D"http://www.w3.org/2003/05/soap-envelope">
=A0 <soapenv:Body>
=A0 =A0 <soapenv:Fault>
=A0 =A0 =A0 <soapenv:Code&g= t;
=A0 =A0 =A0 =A0 <soapenv:Value>soapenv:Sender</soapen= v:Value>
=A0 =A0 =A0 </soapenv:Code>
=A0 =A0 = =A0 <soapenv:Reason>
=A0 =A0 =A0 =A0 <soapenv:Text xmlns:xml=3D"http://www.w3.org/XML/1998/= namespace" xml:lang=3D"en">No Error</soapenv:Text&= gt;
=A0 =A0 =A0 </soapenv:Reason>
=A0 =A0 =A0 <soapenv:Detail>
=A0 =A0 =A0 =A0 <fault= >myService|h= ttp://com.abcd.efg.hijk/2.0/ failed</fault>
=A0 =A0 =A0= </soapenv:Detail>
=A0 =A0 </soapenv:Fault>
=A0 </soapenv:Body>
</soapenv:Envelope>

Below is ADB function for one such API:

axis2_status_t =A0axis2_skel_myService_myTask(const axutil_env_t *en= v , axis2_msg_ctx_t *msg_ctx,
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 adb_cancelTask_t* _cancelTask,
=A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= axis2_skel_myService_myTask_fault *fault );
=A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0

Looks like it cannot handle when ADB does not have any = output params to return (so it returns NULL) and status is AXIS2_SUCCESS.

Changing WSDL is not an option for my project.

My problem is different from the issue at https://= issues.apache.org/jira/browse/AXIS2C-1279

I ap= ologize if this question is already answered and please point me to that li= nk.

This is kind of a blocker for me right now. Any help is= greatly appreciated.

Thanks,
Pavani




--047d7b60518c1af45d04e1221090--