[
https://issues.apache.org/jira/browse/AXIS2C-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe updated AXIS2C-501:
-------------------------------------
Fix Version/s: (was: 1.0.0)
It looks to me a if this is something to be solved at Sandesha level. But not
sure of the right solution right now. Hence postponing the issue to post 1.0.0
> 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
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
