You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-c-dev@ws.apache.org by "S.Uthaiyashankar (JIRA)" <ji...@apache.org> on 2008/08/28 06:34:44 UTC

[jira] Updated: (RAMPARTC-125) httpd segfaults for WSSeconvSign scenarios

     [ https://issues.apache.org/jira/browse/RAMPARTC-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

S.Uthaiyashankar updated RAMPARTC-125:
--------------------------------------

    Component/s: SecureConversation

axutil_hash_t keeps internal env. When running with httpd, env is created in local pool per request. so we have to set hash's env per request basis. Not setting that, was the cause of the failure. Fixed in revision 689715

> httpd segfaults for WSSeconvSign scenarios
> ------------------------------------------
>
>                 Key: RAMPARTC-125
>                 URL: https://issues.apache.org/jira/browse/RAMPARTC-125
>             Project: Rampart/C
>          Issue Type: Bug
>          Components: SecureConversation
>            Reporter: Manjula Peiris
>            Assignee: S.Uthaiyashankar
>             Fix For: 1.3.0
>
>
> When I try to interop WSSeconvSign all the scenarios together by deploying in httpd it segfaults. following is the backtrace.
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1210946880 (LWP 24751)]
> 0xb7c3c54f in axutil_hash_find_entry (ht=0xb76ca980, key=0xb76cbde0, klen=28, val=0xb76cbd50) at hash.c:320
> 320             he = AXIS2_MALLOC(ht->env->allocator, sizeof(*he));
> (gdb) bt
> #0  0xb7c3c54f in axutil_hash_find_entry (ht=0xb76ca980, key=0xb76cbde0, klen=28, val=0xb76cbd50) at hash.c:320
> #1  0xb7c3c784 in axutil_hash_set (ht=0xb76ca980, key=0xb76cbde0, klen=4294967295, val=0xb76cbd50) at hash.c:395
> #2  0xb6ed32ce in sct_provider_hash_map_store_token (env=0x82814a0, msg_ctx=0x8281548, 
>     sct_global_id=0xb76cbde0 "urn:uuid:-72127408-7488-1dd1", sct_local_id=0xb76cbd80 "#sctId-7213c380-7488-1dd1", sct=0xb76cbd50, 
>     user_params=0x0) at sct_provider_hash_map.c:182
> #3  0xb715aa48 in rahas_store_security_context_token (env=0x82814a0, sct=0xb76cbd50, msg_ctx=0x8281548) at rahas_request_processor.c:462
> #4  0xb7159fc0 in rahas_process_issue_request (env=0x82814a0, rst=0x823d348, rstr=0x823e1c0, msg_ctx=0x8281548, trust_version=1)
>     at rahas_request_processor.c:136
> #5  0xb7159c33 in rahas_request_security_token (env=0x82814a0, node=0x81e0998, msg_ctx=0x8281548, trust_version=1, request_type=1)
>     at rahas_in_handler.c:318
> #6  0xb7159750 in rahas_in_handler_invoke (handler=0xb71bf1e8, env=0x82814a0, msg_ctx=0x8281548) at rahas_in_handler.c:167
> #7  0xb7cb632b in axis2_handler_invoke (handler=0xb71bf1e8, env=0x82814a0, msg_ctx=0x8281548) at handler.c:91
> #8  0xb7cbaca8 in axis2_phase_invoke (phase=0xb7651008, env=0x82814a0, msg_ctx=0x8281548) at phase.c:230
> #9  0xb7cc25f0 in axis2_engine_invoke_phases (engine=0x81f3b48, env=0x82814a0, phases=0xb764d7d8, msg_ctx=0x8281548) at engine.c:691
> #10 0xb7cc1723 in axis2_engine_receive (engine=0x81f3b48, env=0x82814a0, msg_ctx=0x8281548) at engine.c:272
> #11 0xb7d1dbef in axis2_http_transport_utils_process_http_post_request (env=0x82814a0, msg_ctx=0x8281548, in_stream=0x81a6018, 
>     out_stream=0x82816f8, content_type=0x828083e "application/soap+xml; charset=utf-8", content_length=7583, soap_action_header=0x0, 
>     request_uri=0x8281518 "http://127.0.0.1:9090/axis2/services/XSC") at http_transport_utils.c:699
> #12 0xb7d1ad96 in axis2_apache2_worker_process_request (apache2_worker=0xb7199320, env=0x82814a0, request=0x827f998) at apache2_worker.c:637
> #13 0xb7d1821f in axis2_handler (req=0x827f998) at mod_axis2.c:361
> #14 0x0807e035 in ap_run_handler (r=0x827f998) at config.c:157
> #15 0x0807e77f in ap_invoke_handler (r=0x827f998) at config.c:372
> #16 0x0809da50 in ap_process_request (r=0x827f998) at http_request.c:258
> #17 0x0809a5d2 in ap_process_http_connection (c=0x8196730) at http_core.c:184
> #18 0x08086d8b in ap_run_process_connection (c=0x8196730) at connection.c:43
> #19 0x0808720c in ap_process_connection (c=0x8196730, csd=0x8196598) at connection.c:178
> #20 0x080b751f in child_main (child_num_arg=0) at prefork.c:640
> #21 0x080b7609 in make_child (s=0x80e6c80, slot=0) at prefork.c:680
> #22 0x080b7bad in ap_mpm_run (_pconf=0x80e20a8, plog=0x81201a0, s=0x80e6c80) at prefork.c:956
> #23 0x08067417 in main (argc=Cannot access memory at address 0x1c

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