[
https://issues.apache.org/jira/browse/AXIS2C-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504562
]
Samisa Abeysinghe commented on AXIS2C-612:
------------------------------------------
Aparently, going through the mail thread again, you are not using a WSDL.
Please attach the code, the service.xml file as well as the command that you
used to compile the service to this issue
> Axis HTTP Server crash (segmentation fault).
> --------------------------------------------
>
> Key: AXIS2C-612
> URL: https://issues.apache.org/jira/browse/AXIS2C-612
> Project: Axis2-C
> Issue Type: Bug
> Components: samples
> Affects Versions: 1.0.0
> Environment: Ubuntu Linux
> Reporter: JL LESIEUR
>
> When I try to invoke a service (based on hello.c example), the axis simple
> http server crashes...
> Here's the output :
> Started Simple Axis2 HTTP Server ...
> Erreur de segmentation (core dumped)
> Here's the log :
> [Tue Jun 5 15:50:06 2007] [info] addr_in_handler.c
> [Tue Jun 5 15:50:06 2007] [debug] engine.c(571) Invoking phase Dispatch
> [Tue Jun 5 15:50:06 2007] [debug] phase.c(195) Invoke the handler
> soap_message_body_based_dispatcher within the phase Dispatch
> [Tue Jun 5 15:50:06 2007] [debug] soap_body_disp.c(217) Checking for
> operation using SOAP message body's first child's local name : greet
> [Tue Jun 5 15:50:06 2007] [debug] soap_body_disp.c(226) Operation found
> using SOAP message body's first child's local name
> [Tue Jun 5 15:50:06 2007] [debug] phase.c(195) Invoke the handler
> addressing_based_dispatcher within the phase Dispatch
> [Tue Jun 5 15:50:06 2007] [debug] phase.c(195) Invoke the handler
> soap_action_based_dispatcher within the phase Dispatch
> [Tue Jun 5 15:50:06 2007] [debug] engine.c(571) Invoking phase PostDispatch
> [Tue Jun 5 15:50:06 2007] [debug] phase.c(195) Invoke the handler
> dispatch_post_conditions_evaluator within the phase PostDispatch
> [Tue Jun 5 15:50:06 2007] [debug] phase.c(195) Invoke the handler
> context_handler within the phase PostDispatch
> And here's the backtrace of the coredump :
> #0 0xb7e62b87 in axis2_msg_recv_make_new_svc_obj () from
> /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_engine.so.0
> #1 0xb7e62c98 in axis2_msg_recv_get_impl_obj () from
> /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_engine.so.0
> #2 0xb7e635d4 in axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync ()
> from /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_engine.so.0
> #3 0xb7e63311 in axis2_msg_recv_invoke_business_logic () from
> /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_engine.so.0
> #4 0xb7e63119 in axis2_msg_recv_receive_impl () from
> /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_engine.so.0
> #5 0xb7e6336d in axis2_msg_recv_receive () from
> /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_engine.so.0
> #6 0xb7e58092 in axis2_engine_receive () from
> /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_engine.so.0
> #7 0xb7f0d5de in axis2_http_transport_utils_process_http_post_request ()
> from
> /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_http_common.so.0
> #8 0xb7f0bf20 in axis2_http_worker_process_request () from
> /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_http_common.so.0
> #9 0xb7e140ca in axis2_svr_thread_worker_func () from
> /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxis2_http_receiver.so.0
> #10 0xb7ebf265 in dummy_worker () from
> /home/jllesieur/SVNROOT/axis2c-bin-1.0.0-linux/lib/libaxutil.so.0
> #11 0xb7cb931b in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
> #12 0xb7c2957e in clone () from /lib/tls/i686/cmov/libc.so.6
> Surely it's a problem in my webservice, but there's no other information
> message to help me find where my service is buggy ...
> I hope these information can help ! (If, as I think, the problem is in my
> service, it would be great to display a more explicit message !).
> Thanks a lot !
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
