axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2C-501) Freeing the thread_env crash sandeshaya
Date Sat, 17 Mar 2007 04:38:09 GMT

    [ https://issues.apache.org/jira/browse/AXIS2C-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481819
] 

Samisa Abeysinghe commented on AXIS2C-501:
------------------------------------------

One obvious solution would be to avoid using the stuff allocated in one thread form another
thread beyond the first thread's lifetime. However I am not sure the implications of this
on Sandesha2. Does not the DB based persistance solve this sitiation?

> Freeing the thread_env crash sandeshaya
> ---------------------------------------
>
>                 Key: AXIS2C-501
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-501
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: util
>            Reporter: Damitha Kumarage
>             Fix For: 1.0.0
>
>
> I see now the thread_env is freed at the end of each thread as a fix to memory leaks.
This is perfect. But if the resourced allocatoed by the thread env  is used after thread's
life cycle then that would lead to problems. That's what has happened in Sandesha2. There
I use a hash table  which allocated by a axis2 thread but is used by the sandesha2 sender
thread even after the original thread exit. Please give suggestions to solve this problem

-- 
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


Mime
View raw message