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 ji...@apache.org on 2004/04/27 15:08:53 UTC
[jira] Created: (AXISCPP-65) Bootstrapping bug with logging initialization
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXISCPP-65
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXISCPP-65
Summary: Bootstrapping bug with logging initialization
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis-C++
Components:
Basic Architecture
Versions:
1.1 Final
Assignee:
Reporter: Benson Margulies
Created: Tue, 27 Apr 2004 6:08 AM
Updated: Tue, 27 Apr 2004 6:08 AM
Environment: Windows
Description:
If the code cannot open the log, for example, because AXIS_HOME isn't set, the attempt to log an error dereferences a bad pointer and crashes. Failures that early should just yell on stderr.
---------------------------------------------------------------------
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
[jira] Closed: (AXISCPP-65) Bootstrapping bug with logging initialization
Posted by ax...@ws.apache.org.
Message:
The following issue has been closed.
Resolver: Samisa Abeysinghe
Date: Fri, 8 Oct 2004 5:41 AM
This problem is handled with exception managemnt logic in AxisCongig class.
Works on Linux. The same logic should work on Windows.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXISCPP-65
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXISCPP-65
Summary: Bootstrapping bug with logging initialization
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Axis-C++
Components:
Basic Architecture
Fix Fors:
1.3 Final
Versions:
1.1 Final
Assignee:
Reporter: Benson Margulies
Created: Tue, 27 Apr 2004 6:08 AM
Updated: Fri, 8 Oct 2004 5:41 AM
Environment: Windows
Description:
If the code cannot open the log, for example, because AXIS_HOME isn't set, the attempt to log an error dereferences a bad pointer and crashes. Failures that early should just yell on stderr.
---------------------------------------------------------------------
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
[jira] Commented: (AXISCPP-65) Bootstrapping bug with logging initialization
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: Aleksander Slominski
Created: Tue, 4 May 2004 4:27 PM
Body:
this is VERY serious and confusing back ...
should be TOP priority to fix it ...
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXISCPP-65?page=comments#action_35401
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXISCPP-65
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXISCPP-65
Summary: Bootstrapping bug with logging initialization
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis-C++
Components:
Basic Architecture
Versions:
1.1 Final
Assignee:
Reporter: Benson Margulies
Created: Tue, 27 Apr 2004 6:08 AM
Updated: Tue, 4 May 2004 4:27 PM
Environment: Windows
Description:
If the code cannot open the log, for example, because AXIS_HOME isn't set, the attempt to log an error dereferences a bad pointer and crashes. Failures that early should just yell on stderr.
---------------------------------------------------------------------
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