You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Thilina Gunarathne (JIRA)" <ji...@apache.org> on 2005/08/29 06:10:05 UTC

[jira] Created: (AXIS2-186) Faults are not handled correctly in NonBlocking two channel scenerio

Faults are not handled correctly in NonBlocking two channel scenerio
--------------------------------------------------------------------

         Key: AXIS2-186
         URL: http://issues.apache.org/jira/browse/AXIS2-186
     Project: Apache Axis 2.0 (Axis2)
        Type: Bug
 Reporter: Thilina Gunarathne
    Priority: Critical


I tried using the nonBlocking two channel in client API to call a service. The listener kept on listening without terminating.  I tried this through the tcpmon and  I saw  a service not found Axis fualt as the reply. 
and it is not handled by the client. 
The reason behind may be that the fault is coming in the same channel where we send the reply. But the listener is up on a seperate channel....


-- 
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] Resolved: (AXIS2-186) Faults are not handled correctly in NonBlocking two channel scenerio

Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS2-186?page=all ]
     
Deepal Jayasinghe resolved AXIS2-186:
-------------------------------------

    Resolution: Fixed

Fixed by introduction of ServiceClient and OperationClie

> Faults are not handled correctly in NonBlocking two channel scenerio
> --------------------------------------------------------------------
>
>          Key: AXIS2-186
>          URL: http://issues.apache.org/jira/browse/AXIS2-186
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug
>     Reporter: Thilina Gunarathne
>     Assignee: Deepal Jayasinghe
>     Priority: Critical

>
> I tried using the nonBlocking two channel in client API to call a service. The listener kept on listening without terminating.  I tried this through the tcpmon and  I saw  a service not found Axis fualt as the reply. 
> and it is not handled by the client. 
> The reason behind may be that the fault is coming in the same channel where we send the reply. But the listener is up on a seperate channel....

-- 
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: (AXIS2-186) Faults are not handled correctly in NonBlocking two channel scenerio

Posted by "Eran Chinthaka (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS2-186?page=all ]

Eran Chinthaka reassigned AXIS2-186:
------------------------------------

    Assign To: Deepal Jayasinghe

I think user should call the service in a try block and should call serviceClient.finalizeInvoke() within finally. That will fix this.
Deepal, you may add some more here and resolve this issue.

> Faults are not handled correctly in NonBlocking two channel scenerio
> --------------------------------------------------------------------
>
>          Key: AXIS2-186
>          URL: http://issues.apache.org/jira/browse/AXIS2-186
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug
>     Reporter: Thilina Gunarathne
>     Assignee: Deepal Jayasinghe
>     Priority: Critical

>
> I tried using the nonBlocking two channel in client API to call a service. The listener kept on listening without terminating.  I tried this through the tcpmon and  I saw  a service not found Axis fualt as the reply. 
> and it is not handled by the client. 
> The reason behind may be that the fault is coming in the same channel where we send the reply. But the listener is up on a seperate channel....

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