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 ax...@ws.apache.org on 2004/10/11 05:30:51 UTC
[jira] Updated: (AXISCPP-180) Make the LibWWW based transport thread safe
The following issue has been updated:
Updater: Samisa Abeysinghe (mailto:samisa_abeysinghe@yahoo.com)
Date: Sun, 10 Oct 2004 8:29 PM
Changes:
Component changed to Transport (Client)
Component changed from Transport (Server)
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/AXISCPP-180?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXISCPP-180
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXISCPP-180
Summary: Make the LibWWW based transport thread safe
Type: Bug
Status: Open
Priority: Major
Project: Axis-C++
Components:
Transport (Client)
Versions:
current (nightly)
Assignee: Samisa Abeysinghe
Reporter: Samisa Abeysinghe
Created: Thu, 30 Sep 2004 3:54 AM
Updated: Sun, 10 Oct 2004 8:29 PM
Due: Fri, 8 Oct 2004 12:00 AM
Environment: Linux platfrom
Description:
The test program in tests/client/threadSafe fails randomly with LibWWW based transport.
It was expected that lib level init made possible by Axis::initialize would have made this transport thread safe, however, there are some undefined behaviours at times.
This problem could not be solved even with the pseudo locking model implemented to guard against event loop conflicts.
---------------------------------------------------------------------
JIRA INFORMATION:
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