[wsf-c-dev] [jira] Closed: (WSFC-103) rm_ping_1_0 segfaults after recieving first request from service sqlite.

[Dushshantha Chandradasa (JIRA)]

     [ http://www.wso2.org/jira/browse/WSFC-103?page=all ]

Dushshantha Chandradasa closed WSFC-103.
----------------------------------------


reviewed. can be closed.

> rm_ping_1_0 segfaults after recieving first request from service sqlite.
> ------------------------------------------------------------------------
>
>                 Key: WSFC-103
>                 URL: http://www.wso2.org/jira/browse/WSFC-103
>             Project: WSO2 WSF/C
>          Issue Type: Bug
>          Components: Apache Sandesha/C (RM)
>    Affects Versions: 1.0.1
>         Environment: Linux
>            Reporter: Dushshantha Chandradasa
>         Assigned To: Samisa Abeysinghe
>             Fix For: 1.1.0
>
>
> rm_ping_1_0 segfaults after recieving first request from service sqlite.
> Here is the gdb trace
> (gdb) bt
> #0  0xb7f02450 in axis2_ctx_get_property (ctx=0x1c, env=0x81d9628, key=0x1c <Address 0x1c out of bounds>) at ctx.c:98
> #1  0xb7f0346c in axis2_msg_ctx_get_property (msg_ctx=0x81d8320, env=0x81d9628, key=0xb7f61e1b "WSAddressingVersion") at msg_ctx.c:1196
> #2  0xb7f439e0 in sandesha2_permanent_storage_mgr_store_msg_ctx (storage_mgr=0x81d29b8, env=0x81d9628, key=0x81eed88 "1f4a2e92-3f1d-1dc1-3f74-001302c29070",
>     msg_ctx=0x81d8320) at permanent_storage_mgr.c:1053
> #3  0xb7f43db6 in sandesha2_permanent_storage_mgr_update_msg_ctx (storage_mgr=0x1c, env=0x1c, key=0x1c <Address 0x1c out of bounds>, msg_ctx=0x1c)
>     at permanent_storage_mgr.c:569
> #4  0xb7f39e09 in sandesha2_storage_mgr_update_msg_ctx (storage_mgr=0xb7f61e1b, env=0x1c, key=0x1c <Address 0x1c out of bounds>, msg_ctx=0x1c) at storage_mgr.c:165
> #5  0xb7f36708 in sandesha2_create_seq_res_msg_processor_process_in_msg (msg_processor=0x81ecb60, env=0x81d9628, rm_msg_ctx=0x81ed478) at create_seq_res_msg_processor.c:450
> #6  0xb7f37bfa in sandesha2_msg_processor_process_in_msg (msg_processor=0xb7f61e1b, env=0x1c, rm_msg_ctx=0x1c) at msg_processor_creator.c:97
> #7  0xb7f2eb74 in sandesha2_in_handler_invoke (handler=0x80b01b0, env=0x81d9628, msg_ctx=0x81dfe78) at sandesha2_in_handler.c:224
> #8  0xb7ee6921 in axis2_handler_invoke (handler=0xb7f61e1b, env=0x1c, msg_ctx=0x1c) at handler.c:91
> #9  0xb7ee9498 in axis2_phase_invoke (phase=0x80ae7a8, env=0x81d9628, msg_ctx=0x81dfe78) at phase.c:199
> #10 0xb7eec81d in axis2_engine_invoke_phases (engine=0x81e5a18, env=0x81d9628, phases=0x80adcd0, msg_ctx=0x81dfe78) at engine.c:578
> #11 0xb7eed386 in axis2_engine_receive (engine=0x81e5a18, env=0x81d9628, msg_ctx=0x81dfe78) at engine.c:255
> #12 0xb7f566ed in sandesha2_sender_worker_worker_func (thd=0x81de560, data=0x81dfe78) at sender_worker.c:667
> #13 0xb7e60fcd in dummy_worker (opaque=0x1c) at thread_unix.c:86
> #14 0xb7dd2341 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
> #15 0xb7c1e4ee 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