axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Damitha Kumarage (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2C-26) Server crashes on the second call to service struct create
Date Thu, 26 Jan 2006 07:52:10 GMT
    [ http://issues.apache.org/jira/browse/AXIS2C-26?page=comments#action_12364065 ] 

Damitha Kumarage commented on AXIS2C-26:
----------------------------------------

I today gave more finer solution to this issue. Instead of unloading the service I keep the
dll_handler in dll_desc. This dll_desc is kept in axis2_svc.
So next time same service is called I get that dll_desc and use it's dll_hanlder instead of
reloading the library again. I plan to use this tecnique not
only for service loading. I can use this for module loading, messaage receicer loading, handler
loading etc


> Server crashes on the second call to service struct create
> ----------------------------------------------------------
>
>          Key: AXIS2C-26
>          URL: http://issues.apache.org/jira/browse/AXIS2C-26
>      Project: Axis2-C
>         Type: Bug
>   Components: core/deployment
>     Reporter: Samisa Abeysinghe
>     Assignee: Damitha Kumarage
>     Priority: Critical
>      Fix For: M0.3

>
> When I send a second request to create a service struct instance using the create function
got from the service DLL, the server crashes. See the below trace:
> Breakpoint 1, axis2_class_loader_create_dll (env=0xbf8db774, impl_info_param=0x979a240)
at class_loader.c:105
> 105         create_funct = AXIS2_DLL_DESC_GET_CREATE_FUNCT(dll_desc, env);
> (gdb) n
> 107         if (!create_funct)
> (gdb) n
> 110         dll_type = AXIS2_DLL_DESC_GET_TYPE(dll_desc, env);
> (gdb) n
> 111         if(AXIS2_SVC_DLL == dll_type)
> (gdb)
> 113             create_funct(&svc_skeli, env);
> (gdb)
> Program received signal SIGSEGV, Segmentation fault.
> 0x0060417b in nullserv () from /lib/libc.so.6
> (gdb) bt
> #0  0x0060417b in nullserv () from /lib/libc.so.6
> #1  0x00b9163f in axis2_class_loader_create_dll (env=0xbf8db774, impl_info_param=0x979a240)
at class_loader.c:113
> #2  0x00b9e2c2 in axis2_msg_recv_make_new_svc_obj (msg_recv=0x979b530, env=0xbf8db774,
msg_ctx=0x97b7f40)
>     at msg_recv.c:182
> #3  0x00b9e64f in axis2_msg_recv_get_impl_obj (msg_recv=0x979b530, env=0xbf8db774, msg_ctx=0x97b7f40)
at msg_recv.c:256
> #4  0x00b9eaca in axis2_raw_xml_in_out_msg_recv_invoke_business_logic (msg_recv=0x979b530,
env=0xbf8db774,
>     msg_ctx=0x97b7f40, new_msg_ctx=0x97be9f8) at raw_xml_in_out_msg_recv.c:88
> #5  0x00b9f241 in axis2_raw_xml_in_out_msg_recv_receive (msg_recv=0x979b530, env=0xbf8db774,
msg_ctx=0x97b7f40)
>     at raw_xml_in_out_msg_recv.c:258
> #6  0x0090d588 in axis2_engine_receive (engine=0x97bde08, env=0xbf8db774, msg_ctx=0x97b7f40)
at engine.c:326
> #7  0x0096a558 in axis2_http_transport_utils_process_http_post_request (env=0xbf8db774,
msg_ctx=0x97b7f40,
>     in_stream=0x97b0328, out_stream=0x97b7c20, content_type=0x97b7bb0 " application/soap+xml;\r\n",
content_length=1174,
>     soap_action_header=0x0, request_uri=0x97b7bd0 "/axis2/services/echo/echo") at http_transport_utils.c:230
> #8  0x00969545 in axis2_http_worker_process_request (http_worker=0x97ae178, env=0xbf8db774,
svr_conn=0x97ade40,
>     simple_request=0x97b6f18) at http_worker.c:272
> #9  0x00148310 in axis2_http_svr_thread_run (svr_thread=0x97adff8, env=0xbf8db774) at
http_svr_thread.c:174
> #10 0x001491ab in axis2_http_server_start (server=0x976c078, env=0xbf8db774) at http_server.c:191
> #11 0x08048be1 in main (argc=1, argv=0xbf8db814) at http_server_main.c:101

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


Mime
View raw message