axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Damitha Kumarage (JIRA)" <>
Subject [jira] Commented: (AXIS2C-1188) SOAP fault not working with axis2c latest revision(663886) from code generated from axis2/java using adb
Date Mon, 30 Jun 2008 09:41:45 GMT


Damitha Kumarage commented on AXIS2C-1188:

There are following scenarios to consider in in-out case

1) If the service implementor returns NULL or some fault status in the serivce function. But
implement the on_fault in his service implementation. In this case I nicely get the soap fault
saying something like service implementation not found.

2) Service function return NULL or some fault status. on_fault also returns NULL.
    In this case we just get accepted 202.

3) Service return NULL or some error status. A on_fault function is not implemented at all.
i.e it is set to NULL in skeleton.
 In this case server segfault with 

#0  0x00000000 in ?? ()
#1  0xb7ef5675 in axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync (msg_recv=0x80b0c20,
    msg_ctx=0x80cf7a0, new_msg_ctx=0x80d58b0) at raw_xml_in_out_msg_recv.c:291
#2  0xb7ef48f4 in axis2_msg_recv_invoke_business_logic (msg_recv=0x80b0c20, env=0x80cec70,
    out_msg_ctx=0x80d58b0) at msg_recv.c:397
#3  0xb7ef4f02 in axis2_msg_recv_receive_impl (msg_recv=0x80b0c20, env=0x80cec70, msg_ctx=0x80cf7a0,

    callback_recv_param=0x0) at msg_recv.c:319
#4  0xb7ef4974 in axis2_msg_recv_receive (msg_recv=0x80b0c20, env=0x80cec70, msg_ctx=0x80cf7a0,
    at msg_recv.c:436
#5  0xb7eea066 in axis2_engine_receive (engine=0x80d4488, env=0x80cec70, msg_ctx=0x80cf7a0)
at engine.c:318
#6  0xb7f3a83b in axis2_http_transport_utils_process_http_post_request (env=0x80cec70, msg_ctx=0x80cf7a0,

    in_stream=0x80ceca0, out_stream=0x80ceeb0, content_type=0x80cecd0 "application/soap+xml;charset=UTF-8",

    content_length=512, soap_action_header=0x0, request_uri=0x80cfba8 "")
    at http_transport_utils.c:658
#7  0xb7f375c3 in axis2_http_worker_process_request (http_worker=0x80ce1b8, env=0x80cec70,
    simple_request=0x80ced48) at http_worker.c:908
#8  0xb7eab011 in axis2_svr_thread_worker_func (thd=0x80ceba0, data=0x80ceb88) at http_svr_thread.c:259
#9  0xb7f5b226 in dummy_worker (opaque=0x80ceba0) at thread_unix.c:93
#10 0xb7e6b4fb in start_thread () from /lib/i686/cmov/
#11 0xb7dd5d7e in clone () from /lib/i686/cmov/

My suggestion to fix this is in raw_xml_msg_receiver
if there is a errror in service invoke then first check whether on_fault function is set.
if set and return NULL then handle it and send a soap fualt appropriately. If not set then

send a soap fault.

> SOAP fault not working with axis2c latest revision(663886) from code generated from axis2/java
using adb
> --------------------------------------------------------------------------------------------------------
>                 Key: AXIS2C-1188
>                 URL:
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: core/engine
>    Affects Versions: Current (Nightly)
>         Environment: axis2c revision number 663886.
> axis2/java 1.4 and also axis2/java nighlty build
>            Reporter: naveen bhat
>            Assignee: Supun Kamburugamuva
>         Attachments: raw_xml_recv.patch, raw_xml_recv_corrected.patch, readable_macro_correction2.patch
>   Original Estimate: 72h
>  Remaining Estimate: 72h
> Hello group,
> I used axis2/java 1.4 to generate server side code from wsdl.
> I did not write the business logic in the service skeleton(i.e all empty operations returning
> I compiled the code to generate
> I deployed the service( and services.xml).
> I made a request from the axis2/java client.
> Ideally client should receive a soap fault from server.
> But server is not sending any response.
> I monitored the soap messages using tcpmon and found that the server is sending only
http header, and there was no soap message in response.
> I also experimented the same steps using axis2/java nightly build(available at
but the result remained the same.
> Need help in this regard.Let me know if you need more details
> PS: command used to generate the server side code
> -uri <wsdl path> -ss -sd -d adb -u.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message