Alex Mantaut created AXIS2C-1634:
------------------------------------
Summary: Env management in hash
Key: AXIS2C-1634
URL: https://issues.apache.org/jira/browse/AXIS2C-1634
Project: Axis2-C
Issue Type: Bug
Components: core/engine
Affects Versions: 1.7.0
Reporter: Alex Mantaut
Attachments: hash_env.patch
It seems that axutil_hash was modified to have a reference of the environment,
but its use is not consistent across the hash interface...
This means that you can create the hash and work with one environment at first
(creating variables and such) and then switch to another environment, releasing
the variables in other environment, this could cause problems with the
allocator... (this happens specially when you use multiple threads, with an
environment for every thread)
The solution I've found is to uniformize the interface, just set the
environment at first and then use the same environment until destroying the
hash (because the hash increses the ref count of the environment it is sure the
environment stored exists)
If you copy or create a new hash you will have to set the environment for the
new hash...
I looked through all the calls of the hash in the code and it works fine (I
know it is a big patch, but I think is usefull)
Please let me know if any changes need to be done on the issue
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: c-dev-h...@axis.apache.org
