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/05/25 15:49:53 UTC

[jira] Created: (AXISCPP-660) errno not output if library load fails

errno not output if library load fails
--------------------------------------

         Key: AXISCPP-660
         URL: http://issues.apache.org/jira/browse/AXISCPP-660
     Project: Axis-C++
        Type: Bug
  Components: Transport (axis3)  
    Reporter: Mark Whitlock


In ChannelFactory, if the channel library fails to load, the dlerror string is stored in the text of the exception that is thrown back to the client. But errno may also contain useful information. On AIX, for instance, the dlerror string is only set if the errno returned is ENOEXEC. So errno should be included in the exception, as well as the dlerror string. I believe this problem affects the code that loads other libraries. Errno should be passed back to the application in all exceptions that result from a system call failing that may set errno. This affects all platforms, not just AIX.

-- 
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] Commented: (AXISCPP-660) errno not output if library load fails

Posted by "Mark Whitlock (JIRA)" <ax...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/AXISCPP-660?page=comments#action_66268 ]
     
Mark Whitlock commented on AXISCPP-660:
---------------------------------------

This is related to AXISCPP-548

> errno not output if library load fails
> --------------------------------------
>
>          Key: AXISCPP-660
>          URL: http://issues.apache.org/jira/browse/AXISCPP-660
>      Project: Axis-C++
>         Type: Bug
>   Components: Transport (axis3)
>     Reporter: Mark Whitlock

>
> In ChannelFactory, if the channel library fails to load, the dlerror string is stored in the text of the exception that is thrown back to the client. But errno may also contain useful information. On AIX, for instance, the dlerror string is only set if the errno returned is ENOEXEC. So errno should be included in the exception, as well as the dlerror string. I believe this problem affects the code that loads other libraries. Errno should be passed back to the application in all exceptions that result from a system call failing that may set errno. This affects all platforms, not just AIX.

-- 
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] Closed: (AXISCPP-660) errno not output if library load fails

Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/AXISCPP-660?page=all ]
     
Samisa Abeysinghe closed AXISCPP-660:
-------------------------------------

    Resolution: Fixed

Added error noumber information to the exception

> errno not output if library load fails
> --------------------------------------
>
>          Key: AXISCPP-660
>          URL: http://issues.apache.org/jira/browse/AXISCPP-660
>      Project: Axis-C++
>         Type: Bug
>   Components: Transport (axis3)
>     Reporter: Mark Whitlock
>     Assignee: Samisa Abeysinghe

>
> In ChannelFactory, if the channel library fails to load, the dlerror string is stored in the text of the exception that is thrown back to the client. But errno may also contain useful information. On AIX, for instance, the dlerror string is only set if the errno returned is ENOEXEC. So errno should be included in the exception, as well as the dlerror string. I believe this problem affects the code that loads other libraries. Errno should be passed back to the application in all exceptions that result from a system call failing that may set errno. This affects all platforms, not just AIX.

-- 
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-660) errno not output if library load fails

Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/AXISCPP-660?page=all ]

Samisa Abeysinghe reassigned AXISCPP-660:
-----------------------------------------

    Assign To: Samisa Abeysinghe

> errno not output if library load fails
> --------------------------------------
>
>          Key: AXISCPP-660
>          URL: http://issues.apache.org/jira/browse/AXISCPP-660
>      Project: Axis-C++
>         Type: Bug
>   Components: Transport (axis3)
>     Reporter: Mark Whitlock
>     Assignee: Samisa Abeysinghe

>
> In ChannelFactory, if the channel library fails to load, the dlerror string is stored in the text of the exception that is thrown back to the client. But errno may also contain useful information. On AIX, for instance, the dlerror string is only set if the errno returned is ENOEXEC. So errno should be included in the exception, as well as the dlerror string. I believe this problem affects the code that loads other libraries. Errno should be passed back to the application in all exceptions that result from a system call failing that may set errno. This affects all platforms, not just AIX.

-- 
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