axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe (JIRA)" <>
Subject [jira] Commented: (AXISCPP-130) Client memory problems with globals
Date Mon, 31 Jan 2005 12:26:17 GMT
     [ ]
Samisa Abeysinghe commented on AXISCPP-130:

We still do have globles; but are not facing problems with them as far as we know.
Hence can I say that we are happy about the use of globles in current codebase and close this

> Client memory problems with globals
> -----------------------------------
>          Key: AXISCPP-130
>          URL:
>      Project: Axis-C++
>         Type: Bug
>   Components: Basic Architecture
>     Versions: 1.3 Beta
>     Reporter: Mark Whitlock

> 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