[wsf-c-dev] [jira] Commented: (WSFC-57) Simple Axis server segfaults when a wrong oparation is called from math sample client while Savan is engaged.

[Evanthika Amarasiri (JIRA)]

    [ http://www.wso2.org/jira/browse/WSFC-57?page=comments#action_11389 ] 
            
Evanthika Amarasiri commented on WSFC-57:
-----------------------------------------

Tried running the security samples with invalid policy files and the Simple Axis Server segfaults. Seems that whenever a fault is occurred Savan is crashing and a segfault it given

> Simple Axis server segfaults when a wrong oparation is called from math sample client while Savan is engaged.
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: WSFC-57
>                 URL: http://www.wso2.org/jira/browse/WSFC-57
>             Project: WSO2 WSF/C
>          Issue Type: Bug
>          Components: Apache Savan/C (Eventing)
>    Affects Versions: 1.0alpha2
>         Environment: Linux ( Ubuntu 7.04)
>            Reporter: Dushshantha Chandradasa
>
> Simple Axis server segfaults when a wrong oparation is called from math sample client while Savan is engaged.
> Run math client as follows to reproduse the error. 
> ./math addd 
> gdb complains with following information. 
> ..
> Started Simple Axis2 HTTP Server ...
> [New Thread -1223398480 (LWP 27499)]
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1223398480 (LWP 27499)]
> 0x080582c3 in axis2_svc_get_name (svc=0x0, env=0x0) at svc.c:796
> 796         if (svc->qname)
> (gdb) bt
> #0  0x080582c3 in axis2_svc_get_name (svc=0x0, env=0x0) at svc.c:796
> #1  0xb7bb1bff in savan_out_handler_invoke (handler=0x80e92e0, env=0x819e698, msg_ctx=0x81a7328) at savan_out_handler.c:101
> #2  0xb7d68861 in axis2_handler_invoke (handler=0x81a7328, env=0x0, msg_ctx=0x0) at handler.c:91
> #3  0xb7d6b3d8 in axis2_phase_invoke (phase=0x80d0a08, env=0x819e698, msg_ctx=0x81a7328) at phase.c:199
> #4  0xb7d6e737 in axis2_engine_invoke_phases (engine=0x81a6238, env=0x819e698, phases=0x819cb08, msg_ctx=0x81a7328) at engine.c:574
> #5  0xb7d6e82a in axis2_engine_send_fault (engine=0x0, env=0x819e698, msg_ctx=0x81a7328) at engine.c:328
> #6  0xb7da16a3 in axis2_http_worker_process_request (http_worker=0x819e5f0, env=0x819e698, svr_conn=0x819e6b0, simple_request=0x819e768) at http_worker.c:353
> #7  0xb7d41d45 in axis2_svr_thread_worker_func (thd=0x819e618, data=0x819e600) at http_svr_thread.c:258
> #8  0xb7dbedc5 in dummy_worker (opaque=0x0) at thread_unix.c:86
> #9  0xb7d1d341 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
> #10 0xb7c9b4ee in clone () from /lib/tls/i686/cmov/libc.so.6

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://www.wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira