axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "santosh kumar das (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AXIS2-5312) Application level blocking and transport level non blocking fails with connection timeout in case of WS-Addressing enabled.
Date Thu, 03 May 2012 11:18:48 GMT
santosh kumar das created AXIS2-5312:
----------------------------------------

             Summary: Application level blocking and transport level non blocking fails with
connection timeout in case of WS-Addressing enabled.
                 Key: AXIS2-5312
                 URL: https://issues.apache.org/jira/browse/AXIS2-5312
             Project: Axis2
          Issue Type: Bug
    Affects Versions: 1.5.4
            Reporter: santosh kumar das


If we execute a service using execute api (block = true )and engage addressing module with
a reply to header as a non anonymous uri ,the client fails with connection timeout.Analysed
the code OutInAxisOperation.sendAsync()
creates a synccallback in case the client doesnt register any callback,and the thread which
gets spinned off for transpot level asynchronous behaviour ,I believe its is TransportNonBlockingInvocationWorker
in AxisEngine
doesnt notify the main thread (and does complete to true)when WaitForcompletion is called
on the synccallback,so even if the response is recieved ,it times out.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


Mime
View raw message