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 "Damitha Kumarage (JIRA)" <ji...@apache.org> on 2008/10/22 09:52:44 UTC

[jira] Created: (AXIS2C-1279) A soap fault of "No Error" return

A soap fault of "No Error" return
---------------------------------

                 Key: AXIS2C-1279
                 URL: https://issues.apache.org/jira/browse/AXIS2C-1279
             Project: Axis2-C
          Issue Type: Bug
            Reporter: Damitha Kumarage


A soap fault with reason "No Error" return when a request without soap header is sent. In addition server seg faults.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


[jira] Updated: (AXIS2C-1279) A soap fault of "No Error" return

Posted by "S.Uthaiyashankar (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2C-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

S.Uthaiyashankar updated AXIS2C-1279:
-------------------------------------

    Component/s: core/engine

> A soap fault of "No Error" return
> ---------------------------------
>
>                 Key: AXIS2C-1279
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1279
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: core/engine
>            Reporter: Damitha Kumarage
>             Fix For: 1.6.0
>
>
> A soap fault with reason "No Error" return for certain errors at server side. The reason is that some times failures happen at server side but error code is not set for these. When at later times code see the status failure and call axutil_error_get_message() then it give the wrong message "No Error".
> To avoid this there are two solutions
> 1. Whenever there is an error make sure to call set_error_code(). Fix this in the current code.
> 2. Avoid using axutil_eror_get_message() function. 
> Ideally the solution should be the first one. Two is only a temporary hack.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (AXIS2C-1279) A soap fault of "No Error" return

Posted by "Damitha Kumarage (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2C-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761210#action_12761210 ] 

Damitha Kumarage commented on AXIS2C-1279:
------------------------------------------

When a service return NULL without setting error code(a common mistake that could happen by service writer) then this fault occur. I have fixed this perticuler problem by checking for "No Error" in the message receiver. This could be considered as the 3rd solution to the above problem

> A soap fault of "No Error" return
> ---------------------------------
>
>                 Key: AXIS2C-1279
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1279
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: core/engine
>            Reporter: Damitha Kumarage
>             Fix For: Next Version
>
>
> A soap fault with reason "No Error" return for certain errors at server side. The reason is that some times failures happen at server side but error code is not set for these. When at later times code see the status failure and call axutil_error_get_message() then it give the wrong message "No Error".
> To avoid this there are two solutions
> 1. Whenever there is an error make sure to call set_error_code(). Fix this in the current code.
> 2. Avoid using axutil_eror_get_message() function. 
> Ideally the solution should be the first one. Two is only a temporary hack.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (AXIS2C-1279) A soap fault of "No Error" return

Posted by "Manjula Peiris (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2C-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manjula Peiris updated AXIS2C-1279:
-----------------------------------

    Fix Version/s: 1.6.0

> A soap fault of "No Error" return
> ---------------------------------
>
>                 Key: AXIS2C-1279
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1279
>             Project: Axis2-C
>          Issue Type: Bug
>            Reporter: Damitha Kumarage
>             Fix For: 1.6.0
>
>
> A soap fault with reason "No Error" return for certain errors at server side. The reason is that some times failures happen at server side but error code is not set for these. When at later times code see the status failure and call axutil_error_get_message() then it give the wrong message "No Error".
> To avoid this there are two solutions
> 1. Whenever there is an error make sure to call set_error_code(). Fix this in the current code.
> 2. Avoid using axutil_eror_get_message() function. 
> Ideally the solution should be the first one. Two is only a temporary hack.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (AXIS2C-1279) A soap fault of "No Error" return

Posted by "Damitha Kumarage (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2C-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Damitha Kumarage updated AXIS2C-1279:
-------------------------------------

    Description: 
A soap fault with reason "No Error" return for certain errors at server side. The reason is that some times failures happen at server side but error code is not set for these. When at later times code see the status failure and call axutil_error_get_message() then it give the wrong message "No Error".
To avoid this there are two solutions
1. Whenever there is an error make sure to call set_error_code(). Fix this in the current code.
2. Avoid using axutil_eror_get_message() function. 

Ideally the solution should be the first one. Two is only a temporary hack.

  was:A soap fault with reason "No Error" return when a request without soap header is sent. In addition server seg faults.


> A soap fault of "No Error" return
> ---------------------------------
>
>                 Key: AXIS2C-1279
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1279
>             Project: Axis2-C
>          Issue Type: Bug
>            Reporter: Damitha Kumarage
>
> A soap fault with reason "No Error" return for certain errors at server side. The reason is that some times failures happen at server side but error code is not set for these. When at later times code see the status failure and call axutil_error_get_message() then it give the wrong message "No Error".
> To avoid this there are two solutions
> 1. Whenever there is an error make sure to call set_error_code(). Fix this in the current code.
> 2. Avoid using axutil_eror_get_message() function. 
> Ideally the solution should be the first one. Two is only a temporary hack.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org