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-189) Stub falls over after first stub has been deleted
Date Tue, 26 Oct 2004 08:59:43 GMT
     [ ]
Samisa Abeysinghe commented on AXISCPP-189:

Are we happy with the platform level Axis::initialize(false); {false to indicate client; true
to say its server} and Axis::terminate(); as a solution for this issues? Or are we looking
for another solution. (Thread safety concerns leave out refcount)

> Stub falls over after first stub has been deleted
> -------------------------------------------------
>          Key: AXISCPP-189
>          URL:
>      Project: Axis-C++
>         Type: Bug
>   Components: Basic Architecture
>     Versions: 1.3 Final
>     Reporter: Mark Whitlock
>     Priority: Minor

> The first Call to be created remembers that it issued initialize_module and issues uninitialize_module
in its destructor. Other Call objects don't issue initialize_module. If other Call objects
are used after the first Call has been deleted, uninitialize_module will have been called
and they will fall over. There should be a reference count of the number of Call objects and
the *last* one should issue uninitialize_module, not the one that issued initialize_module.
This problem will happen for Stubs and generated stubs, since a generated stub has a Stub
and a Stub has a Call.

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