You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Bill Blough (Jira)" <ji...@apache.org> on 2020/04/07 15:53:00 UTC
[jira] [Updated] (AXIS2C-1377) switching to global/local pools when
used with apache module
[ https://issues.apache.org/jira/browse/AXIS2C-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bill Blough updated AXIS2C-1377:
--------------------------------
Fix Version/s: 1.7.0
> switching to global/local pools when used with apache module
> ------------------------------------------------------------
>
> Key: AXIS2C-1377
> URL: https://issues.apache.org/jira/browse/AXIS2C-1377
> Project: Axis2-C
> Issue Type: Improvement
> Components: util
> Environment: all
> Reporter: Damitha N.M. Kumarage
> Assignee: Damitha N.M. Kumarage
> Priority: Major
> Fix For: 1.7.0
>
> Attachments: allocator_switching.diff
>
>
> When Axis2/C is used with the httpd module to allocate memory in apache global pools one need to call the axutil function axutil_allocator_switch_to_global_pool. To switch back again to use apache local pool(request level allocation) one need to call the axutil_allocator_swith_to_local_pool.
> However there could be problematic situations if used this carelessly. For example consider the following scenario.
> swith_to_global
> ...do something...
> switch_to_global
> ...do something
> swith_to_local
> !!! Now am I using global memory or local memory?. Ideally now I should still be using global memory. But accoring to current Axis2/C implementation at this stage I'm using local memory. This could lead to unavoidable problems.
> Attached patch fix this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: c-dev-help@axis.apache.org