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 "Manjula Peiris (JIRA)" <ji...@apache.org> on 2008/12/23 18:56:44 UTC
[jira] Resolved: (AXIS2C-1320) default logger not thread-safe =>
axutil_env_create_with_error_log not thread-safe
[ https://issues.apache.org/jira/browse/AXIS2C-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manjula Peiris resolved AXIS2C-1320.
------------------------------------
Resolution: Fixed
Patch applied. Thanks for the patch.
> default logger not thread-safe => axutil_env_create_with_error_log not thread-safe
> ----------------------------------------------------------------------------------
>
> Key: AXIS2C-1320
> URL: https://issues.apache.org/jira/browse/AXIS2C-1320
> Project: Axis2-C
> Issue Type: Bug
> Components: util
> Affects Versions: Current (Nightly)
> Reporter: Patrick van Beem
> Assignee: Manjula Peiris
> Fix For: 1.6.0
>
> Attachments: Do_not_create_default_logger.diff
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> The current default logger is not thread-safe. That's no problem as long as it's known. One can use his own logger. However, the axutil_env_create_with_error_log() function internally first creates the default logger and then deletes it again to be replaced by the specified logger. Since even creating / deleting the default logger is not thread-safe, this leads to problems (in my case an assertion in the vs runtime dll).
> When a logger is specified for axutil_env_create_with_error_log(), the default logger should not even be created.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.