You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Tim Bartley (JIRA)" <ax...@ws.apache.org> on 2005/03/18 07:20:21 UTC
[jira] Created: (AXISCPP-557) Reference count initialize/terminate calls
Reference count initialize/terminate calls
------------------------------------------
Key: AXISCPP-557
URL: http://issues.apache.org/jira/browse/AXISCPP-557
Project: Axis-C++
Type: Bug
Components: Basic Architecture
Versions: current (nightly)
Reporter: Tim Bartley
Priority: Minor
Attachments: Axis.cpp.patch
To support multiple clients being loaded/unloaded as shared libraries it would be good to reference count calls to initialize/terminate. Otherwise it is unsafe for such libraries to call initiaize or terminate at all.
I've attached a patch to Axis.cpp but I haven't tested it (trying to finish a few things off) - it requires the creation of a new AxisException.h status code so that if an app calls initialize different values for bServer then an exception is thrown.
Also modified the code so that it doesn't just exit on wsdd failure which is a little nasty for apps that are just dynamically loading the shared library.
I haven't tested this change heavily (alright, not at all - I'm running out of time before my vacation ;-) but I think you get the idea.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXISCPP-557) Reference count initialize/terminate calls
Posted by "Tim Bartley (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-557?page=history ]
Tim Bartley updated AXISCPP-557:
--------------------------------
Attachment: Axis.cpp.patch
> Reference count initialize/terminate calls
> ------------------------------------------
>
> Key: AXISCPP-557
> URL: http://issues.apache.org/jira/browse/AXISCPP-557
> Project: Axis-C++
> Type: Bug
> Components: Basic Architecture
> Versions: current (nightly)
> Reporter: Tim Bartley
> Priority: Minor
> Attachments: Axis.cpp.patch
>
> To support multiple clients being loaded/unloaded as shared libraries it would be good to reference count calls to initialize/terminate. Otherwise it is unsafe for such libraries to call initiaize or terminate at all.
> I've attached a patch to Axis.cpp but I haven't tested it (trying to finish a few things off) - it requires the creation of a new AxisException.h status code so that if an app calls initialize different values for bServer then an exception is thrown.
> Also modified the code so that it doesn't just exit on wsdd failure which is a little nasty for apps that are just dynamically loading the shared library.
> I haven't tested this change heavily (alright, not at all - I'm running out of time before my vacation ;-) but I think you get the idea.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Assigned: (AXISCPP-557) Reference count initialize/terminate calls
Posted by "Adrian Dick (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-557?page=history ]
Adrian Dick reassigned AXISCPP-557:
-----------------------------------
Assign To: Adrian Dick
> Reference count initialize/terminate calls
> ------------------------------------------
>
> Key: AXISCPP-557
> URL: http://issues.apache.org/jira/browse/AXISCPP-557
> Project: Axis-C++
> Type: Bug
> Components: Basic Architecture
> Versions: current (nightly)
> Reporter: Tim Bartley
> Assignee: Adrian Dick
> Priority: Minor
> Attachments: Axis.cpp.patch
>
> To support multiple clients being loaded/unloaded as shared libraries it would be good to reference count calls to initialize/terminate. Otherwise it is unsafe for such libraries to call initiaize or terminate at all.
> I've attached a patch to Axis.cpp but I haven't tested it (trying to finish a few things off) - it requires the creation of a new AxisException.h status code so that if an app calls initialize different values for bServer then an exception is thrown.
> Also modified the code so that it doesn't just exit on wsdd failure which is a little nasty for apps that are just dynamically loading the shared library.
> I haven't tested this change heavily (alright, not at all - I'm running out of time before my vacation ;-) but I think you get the idea.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Resolved: (AXISCPP-557) Reference count initialize/terminate calls
Posted by "Adrian Dick (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-557?page=history ]
Adrian Dick resolved AXISCPP-557:
---------------------------------
Resolution: Fixed
I have applied the provided fix to Axis.cpp. It required a small modification to compile on Windows, and a few small changes to Call, as well as the addition to AxisEngineException described in the original comments.
I have successfully tested on Windows, Linux (RH AS 3.0) and AIX.
> Reference count initialize/terminate calls
> ------------------------------------------
>
> Key: AXISCPP-557
> URL: http://issues.apache.org/jira/browse/AXISCPP-557
> Project: Axis-C++
> Type: Bug
> Components: Basic Architecture
> Versions: current (nightly)
> Reporter: Tim Bartley
> Assignee: Adrian Dick
> Priority: Minor
> Attachments: Axis.cpp.patch
>
> To support multiple clients being loaded/unloaded as shared libraries it would be good to reference count calls to initialize/terminate. Otherwise it is unsafe for such libraries to call initiaize or terminate at all.
> I've attached a patch to Axis.cpp but I haven't tested it (trying to finish a few things off) - it requires the creation of a new AxisException.h status code so that if an app calls initialize different values for bServer then an exception is thrown.
> Also modified the code so that it doesn't just exit on wsdd failure which is a little nasty for apps that are just dynamically loading the shared library.
> I haven't tested this change heavily (alright, not at all - I'm running out of time before my vacation ;-) but I think you get the idea.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (AXISCPP-557) Reference count initialize/terminate
calls
Posted by "Fred Preston (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-557?page=all ]
Fred Preston closed AXISCPP-557:
--------------------------------
> Reference count initialize/terminate calls
> ------------------------------------------
>
> Key: AXISCPP-557
> URL: http://issues.apache.org/jira/browse/AXISCPP-557
> Project: Axis-C++
> Type: Bug
> Components: Basic Architecture
> Versions: current (nightly)
> Reporter: Tim Bartley
> Assignee: Adrian Dick
> Priority: Minor
> Attachments: Axis.cpp.patch
>
> To support multiple clients being loaded/unloaded as shared libraries it would be good to reference count calls to initialize/terminate. Otherwise it is unsafe for such libraries to call initiaize or terminate at all.
> I've attached a patch to Axis.cpp but I haven't tested it (trying to finish a few things off) - it requires the creation of a new AxisException.h status code so that if an app calls initialize different values for bServer then an exception is thrown.
> Also modified the code so that it doesn't just exit on wsdd failure which is a little nasty for apps that are just dynamically loading the shared library.
> I haven't tested this change heavily (alright, not at all - I'm running out of time before my vacation ;-) but I think you get the idea.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira