axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe (JIRA)" <>
Subject [jira] Updated: (AXISCPP-189) Stub falls over after first stub has been deleted
Date Fri, 19 Nov 2004 11:08:25 GMT
     [ ]

Samisa Abeysinghe updated AXISCPP-189:

    Attachment: AXISCPP-189.cpp

This source file creates two stbs and delete one in the mid of the program.
It used Axis::initialize(false); and Axis::terminate(); to init and uninit platform level
If you do not use those, then the client segfaults. But I think this is a fair enough solution.

Can use this sample with the base.wsdl generated code and either the base sample service of
Axis C++ or the echo sample service of Axis Java

> 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
>  Attachments: AXISCPP-189.cpp
> 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