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 "Mark Whitlock (JIRA)" <ax...@ws.apache.org> on 2005/03/11 11:26:56 UTC
[jira] Created: (AXISCPP-529) Termination happens before Axis::terminate
Termination happens before Axis::terminate
------------------------------------------
Key: AXISCPP-529
URL: http://issues.apache.org/jira/browse/AXISCPP-529
Project: Axis-C++
Type: Bug
Reporter: Mark Whitlock
CalculatorDoc_TTest does an Axis::initialize, then runs some services, then does an Axis::terminate(). Because Axis::initialize was used to initialize Axis, Axis should not be terminated until the Axis::terminate is called. But trace is switched off before the Axis::terminate is called. This means that Axis' global variables are being deleted before the Axis::terminate. Assuming that the Stub that initialized Axis is also terminating it, this can lead to problems if that is not the last Stub to be deleted, since subsequent Stubs will fail.
--
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] Commented: (AXISCPP-529) Termination happens before Axis::terminate
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-529?page=comments#action_61106 ]
Samisa Abeysinghe commented on AXISCPP-529:
-------------------------------------------
According to my tests, there is nothing wrong here, even if we have threads.
I see AxisTrace::terminate only being called through Axis::terminate. Hence this looks to me as a non issue.
Could you please attach a trace here if possible.
> Termination happens before Axis::terminate
> ------------------------------------------
>
> Key: AXISCPP-529
> URL: http://issues.apache.org/jira/browse/AXISCPP-529
> Project: Axis-C++
> Type: Bug
> Components: Client - Engine
> Reporter: Mark Whitlock
> Assignee: Samisa Abeysinghe
>
> CalculatorDoc_TTest does an Axis::initialize, then runs some services, then does an Axis::terminate(). Because Axis::initialize was used to initialize Axis, Axis should not be terminated until the Axis::terminate is called. But trace is switched off before the Axis::terminate is called. This means that Axis' global variables are being deleted before the Axis::terminate. Assuming that the Stub that initialized Axis is also terminating it, this can lead to problems if that is not the last Stub to be deleted, since subsequent Stubs will fail.
--
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] Commented: (AXISCPP-529) Termination happens before
Axis::terminate
Posted by "Fred Preston (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-529?page=comments#action_12373376 ]
Fred Preston commented on AXISCPP-529:
--------------------------------------
The test appears to be running successfully now. The application is waiting for all threads to complete before deleting the threads. It might be worth expanding the test to stagger the launching of new threads to see if multiple calls to Axis::initialize also has any effect...
> Termination happens before Axis::terminate
> ------------------------------------------
>
> Key: AXISCPP-529
> URL: http://issues.apache.org/jira/browse/AXISCPP-529
> Project: Axis-C++
> Type: Bug
> Components: Client - Engine
> Reporter: Mark Whitlock
>
> CalculatorDoc_TTest does an Axis::initialize, then runs some services, then does an Axis::terminate(). Because Axis::initialize was used to initialize Axis, Axis should not be terminated until the Axis::terminate is called. But trace is switched off before the Axis::terminate is called. This means that Axis' global variables are being deleted before the Axis::terminate. Assuming that the Stub that initialized Axis is also terminating it, this can lead to problems if that is not the last Stub to be deleted, since subsequent Stubs will fail.
--
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
[jira] Assigned: (AXISCPP-529) Termination happens before Axis::terminate
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-529?page=history ]
Samisa Abeysinghe reassigned AXISCPP-529:
-----------------------------------------
Assign To: Samisa Abeysinghe
> Termination happens before Axis::terminate
> ------------------------------------------
>
> Key: AXISCPP-529
> URL: http://issues.apache.org/jira/browse/AXISCPP-529
> Project: Axis-C++
> Type: Bug
> Reporter: Mark Whitlock
> Assignee: Samisa Abeysinghe
>
> CalculatorDoc_TTest does an Axis::initialize, then runs some services, then does an Axis::terminate(). Because Axis::initialize was used to initialize Axis, Axis should not be terminated until the Axis::terminate is called. But trace is switched off before the Axis::terminate is called. This means that Axis' global variables are being deleted before the Axis::terminate. Assuming that the Stub that initialized Axis is also terminating it, this can lead to problems if that is not the last Stub to be deleted, since subsequent Stubs will fail.
--
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] Commented: (AXISCPP-529) Termination happens before Axis::terminate
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-529?page=comments#action_61104 ]
Samisa Abeysinghe commented on AXISCPP-529:
-------------------------------------------
CalculatorDoc_TTest is a threaded application. So I am wondering if this is happening due to some thread issues.
I tried the same with single threaded AxisBench and the scenario works as expected
> Termination happens before Axis::terminate
> ------------------------------------------
>
> Key: AXISCPP-529
> URL: http://issues.apache.org/jira/browse/AXISCPP-529
> Project: Axis-C++
> Type: Bug
> Reporter: Mark Whitlock
>
> CalculatorDoc_TTest does an Axis::initialize, then runs some services, then does an Axis::terminate(). Because Axis::initialize was used to initialize Axis, Axis should not be terminated until the Axis::terminate is called. But trace is switched off before the Axis::terminate is called. This means that Axis' global variables are being deleted before the Axis::terminate. Assuming that the Stub that initialized Axis is also terminating it, this can lead to problems if that is not the last Stub to be deleted, since subsequent Stubs will fail.
--
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-529) Termination happens before
Axis::terminate
Posted by "nadir amra (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-529?page=all ]
nadir amra closed AXISCPP-529.
------------------------------
Resolution: Fixed
I am assuming there is no problem here since things are working. Otherwise, reopen.
> Termination happens before Axis::terminate
> ------------------------------------------
>
> Key: AXISCPP-529
> URL: http://issues.apache.org/jira/browse/AXISCPP-529
> Project: Axis-C++
> Issue Type: Bug
> Components: Client - Engine
> Reporter: Mark Whitlock
>
> CalculatorDoc_TTest does an Axis::initialize, then runs some services, then does an Axis::terminate(). Because Axis::initialize was used to initialize Axis, Axis should not be terminated until the Axis::terminate is called. But trace is switched off before the Axis::terminate is called. This means that Axis' global variables are being deleted before the Axis::terminate. Assuming that the Stub that initialized Axis is also terminating it, this can lead to problems if that is not the last Stub to be deleted, since subsequent Stubs will fail.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Assigned: (AXISCPP-529) Termination happens before Axis::terminate
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-529?page=all ]
Samisa Abeysinghe reassigned AXISCPP-529:
-----------------------------------------
Assign To: (was: Samisa Abeysinghe)
I have looked into this problem but I lack insight on how to fix this
> Termination happens before Axis::terminate
> ------------------------------------------
>
> Key: AXISCPP-529
> URL: http://issues.apache.org/jira/browse/AXISCPP-529
> Project: Axis-C++
> Type: Bug
> Components: Client - Engine
> Reporter: Mark Whitlock
>
> CalculatorDoc_TTest does an Axis::initialize, then runs some services, then does an Axis::terminate(). Because Axis::initialize was used to initialize Axis, Axis should not be terminated until the Axis::terminate is called. But trace is switched off before the Axis::terminate is called. This means that Axis' global variables are being deleted before the Axis::terminate. Assuming that the Stub that initialized Axis is also terminating it, this can lead to problems if that is not the last Stub to be deleted, since subsequent Stubs will fail.
--
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
[jira] Updated: (AXISCPP-529) Termination happens before Axis::terminate
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-529?page=history ]
Samisa Abeysinghe updated AXISCPP-529:
--------------------------------------
Component: Client - Engine
> Termination happens before Axis::terminate
> ------------------------------------------
>
> Key: AXISCPP-529
> URL: http://issues.apache.org/jira/browse/AXISCPP-529
> Project: Axis-C++
> Type: Bug
> Components: Client - Engine
> Reporter: Mark Whitlock
> Assignee: Samisa Abeysinghe
>
> CalculatorDoc_TTest does an Axis::initialize, then runs some services, then does an Axis::terminate(). Because Axis::initialize was used to initialize Axis, Axis should not be terminated until the Axis::terminate is called. But trace is switched off before the Axis::terminate is called. This means that Axis' global variables are being deleted before the Axis::terminate. Assuming that the Stub that initialized Axis is also terminating it, this can lead to problems if that is not the last Stub to be deleted, since subsequent Stubs will fail.
--
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