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 "Adrian Dick (JIRA)" <ax...@ws.apache.org> on 2004/11/17 17:59:23 UTC
[jira] Created: (AXISCPP-270) FaultMappingDoc testcase failing on windows
FaultMappingDoc testcase failing on windows
-------------------------------------------
Key: AXISCPP-270
URL: http://nagoya.apache.org/jira/browse/AXISCPP-270
Project: Axis-C++
Type: Bug
Versions: current (nightly)
Environment: Windows
Reporter: Adrian Dick
Priority: Critical
When running the FaultMappingDoc test on Windows it fails with the following pop-up message:
Unhandled exception in FaultMappingDoc.exe: 0x0000005: Access Violation.
Following some investigation I've found the problem appears to be a sequencing issue.
By modifying the test to create a new instance of the web service for each call, allows the test to pass.
I feel this is probably a fair fix for this particular test - but the real problem here is a sequencing/re-use issue, and a test (or set of tests) should be created to capture this.
There is obviously some kind of unwanted caching going on between repeated calls causing problems here - though this currently only appears to be a problem on Windows.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.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-270) FaultMappingDoc testcase failing on windows
Posted by "Adrian Dick (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-270?page=history ]
Adrian Dick closed AXISCPP-270:
-------------------------------
> FaultMappingDoc testcase failing on windows
> -------------------------------------------
>
> Key: AXISCPP-270
> URL: http://issues.apache.org/jira/browse/AXISCPP-270
> Project: Axis-C++
> Type: Bug
> Components: Test
> Versions: current (nightly)
> Environment: Windows
> Reporter: Adrian Dick
> Assignee: John Hawkins
> Priority: Critical
> Fix For: 1.5 Alpha
>
> When running the FaultMappingDoc test on Windows it fails with the following pop-up message:
> Unhandled exception in FaultMappingDoc.exe: 0x0000005: Access Violation.
> Following some investigation I've found the problem appears to be a sequencing issue.
> By modifying the test to create a new instance of the web service for each call, allows the test to pass.
> I feel this is probably a fair fix for this particular test - but the real problem here is a sequencing/re-use issue, and a test (or set of tests) should be created to capture this.
> There is obviously some kind of unwanted caching going on between repeated calls causing problems here - though this currently only appears to be a problem on Windows.
--
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-270) FaultMappingDoc testcase failing on windows
Posted by "John Hawkins (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-270?page=comments#action_58384 ]
John Hawkins commented on AXISCPP-270:
--------------------------------------
Andrew is going to return the fault test back to the way it was so we can fix it
> FaultMappingDoc testcase failing on windows
> -------------------------------------------
>
> Key: AXISCPP-270
> URL: http://issues.apache.org/jira/browse/AXISCPP-270
> Project: Axis-C++
> Type: Bug
> Versions: current (nightly)
> Environment: Windows
> Reporter: Adrian Dick
> Priority: Critical
>
> When running the FaultMappingDoc test on Windows it fails with the following pop-up message:
> Unhandled exception in FaultMappingDoc.exe: 0x0000005: Access Violation.
> Following some investigation I've found the problem appears to be a sequencing issue.
> By modifying the test to create a new instance of the web service for each call, allows the test to pass.
> I feel this is probably a fair fix for this particular test - but the real problem here is a sequencing/re-use issue, and a test (or set of tests) should be created to capture this.
> There is obviously some kind of unwanted caching going on between repeated calls causing problems here - though this currently only appears to be a problem on Windows.
--
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-270) FaultMappingDoc testcase failing on windows
Posted by "John Hawkins (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-270?page=history ]
John Hawkins resolved AXISCPP-270:
----------------------------------
Resolution: Fixed
Fix Version: 1.5 Alpha
I've created new test ->FaultMappingRepeatedDoc that only uses one instance of the stub. This test worked first time so I'm assuming that other memory management issues have resolved this problem since it was first opened.
> FaultMappingDoc testcase failing on windows
> -------------------------------------------
>
> Key: AXISCPP-270
> URL: http://issues.apache.org/jira/browse/AXISCPP-270
> Project: Axis-C++
> Type: Bug
> Components: Test
> Versions: current (nightly)
> Environment: Windows
> Reporter: Adrian Dick
> Priority: Critical
> Fix For: 1.5 Alpha
>
> When running the FaultMappingDoc test on Windows it fails with the following pop-up message:
> Unhandled exception in FaultMappingDoc.exe: 0x0000005: Access Violation.
> Following some investigation I've found the problem appears to be a sequencing issue.
> By modifying the test to create a new instance of the web service for each call, allows the test to pass.
> I feel this is probably a fair fix for this particular test - but the real problem here is a sequencing/re-use issue, and a test (or set of tests) should be created to capture this.
> There is obviously some kind of unwanted caching going on between repeated calls causing problems here - though this currently only appears to be a problem on Windows.
--
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-270) FaultMappingDoc testcase failing on windows
Posted by "John Hawkins (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-270?page=history ]
John Hawkins reassigned AXISCPP-270:
------------------------------------
Assign To: John Hawkins
> FaultMappingDoc testcase failing on windows
> -------------------------------------------
>
> Key: AXISCPP-270
> URL: http://issues.apache.org/jira/browse/AXISCPP-270
> Project: Axis-C++
> Type: Bug
> Components: Test
> Versions: current (nightly)
> Environment: Windows
> Reporter: Adrian Dick
> Assignee: John Hawkins
> Priority: Critical
> Fix For: 1.5 Alpha
>
> When running the FaultMappingDoc test on Windows it fails with the following pop-up message:
> Unhandled exception in FaultMappingDoc.exe: 0x0000005: Access Violation.
> Following some investigation I've found the problem appears to be a sequencing issue.
> By modifying the test to create a new instance of the web service for each call, allows the test to pass.
> I feel this is probably a fair fix for this particular test - but the real problem here is a sequencing/re-use issue, and a test (or set of tests) should be created to capture this.
> There is obviously some kind of unwanted caching going on between repeated calls causing problems here - though this currently only appears to be a problem on Windows.
--
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-270) FaultMappingDoc testcase failing on windows
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-270?page=history ]
Samisa Abeysinghe updated AXISCPP-270:
--------------------------------------
Component: Test
> FaultMappingDoc testcase failing on windows
> -------------------------------------------
>
> Key: AXISCPP-270
> URL: http://issues.apache.org/jira/browse/AXISCPP-270
> Project: Axis-C++
> Type: Bug
> Components: Test
> Versions: current (nightly)
> Environment: Windows
> Reporter: Adrian Dick
> Priority: Critical
>
> When running the FaultMappingDoc test on Windows it fails with the following pop-up message:
> Unhandled exception in FaultMappingDoc.exe: 0x0000005: Access Violation.
> Following some investigation I've found the problem appears to be a sequencing issue.
> By modifying the test to create a new instance of the web service for each call, allows the test to pass.
> I feel this is probably a fair fix for this particular test - but the real problem here is a sequencing/re-use issue, and a test (or set of tests) should be created to capture this.
> There is obviously some kind of unwanted caching going on between repeated calls causing problems here - though this currently only appears to be a problem on Windows.
--
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