axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (AXISCPP-130) Client memory problems with globals
Date Thu, 09 Sep 2004 10:02:37 GMT
The following comment has been added to this issue:

     Author: Samisa Abeysinghe
    Created: Thu, 9 Sep 2004 3:02 AM
I updated the code to call ModuleUnInitialize() on client side to prevent memory leaks by
making sure the globals get deleted.

Threading issues due to the use of the globle g_pSerializerPool is yet to be fixed.
However the thSafeTest in the tests folder does work without problems with the axis transport.
View this comment:

View the issue:

Here is an overview of the issue:
        Key: AXISCPP-130
    Summary: Client memory problems with globals
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis-C++
             Basic Architecture
             1.3 Beta

   Reporter: Mark Whitlock

    Created: Wed, 18 Aug 2004 6:55 AM
    Updated: Thu, 9 Sep 2004 3:02 AM

The SerializerPool is a global referenced from g_pSerializerPool and is new'ed during the
Call constructor. A client application that creates stubs up front and then uses them later
would fail because the 2nd time the Call constructor is invoked it would overwrite the globals
the 1st Call constructor set up. An application that 
invokes web services from multiple threads at the same time would fail for the same reason.

g_pSerializerPool gets deleted in ModuleUnInitialize() which is only called from the SimpleAxisServer.
So a client application that creates, uses and deletes Stubs leaks memory since these globals
never get deleted.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message