[ http://issues.apache.org/jira/browse/AXIS2-1061?page=all ]

Eran Chinthaka resolved AXIS2-1061.
-----------------------------------

    Resolution: Fixed

Depends on the situation. I haven't tried using the same callback for thousands 
of requests, you better try it.
If you really wanna have the same callback object, make sure the method is 
sync'ed and it just acts as a proxy.
Anyway, since your concern is addressed by cloning the OMElement, 'm resolving 
this issue.


> sendReceiveNonBlocking fails to send multiple (identical) requests
> ------------------------------------------------------------------
>
>                 Key: AXIS2-1061
>                 URL: http://issues.apache.org/jira/browse/AXIS2-1061
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: client-api
>         Environment: Windows XP sp2, jdk 1.5.03, mac os X 10.4.7, jdk 1.5_06, 
> axis2 17/08/06
>            Reporter: Michele Mazzucco
>            Priority: Critical
>
> The call sendReceiveNonBlocking call fails when multiple, identical messages 
> are sent. More in detail, the first send succeeds, but the second fails 
> because the message is sent with an empty SOAP body. A workaround is to 
> interleave two consecutive send operations by (at least) 600 ms (on my 
> system).
> In other words:
> for (int i = 0; i < execution.requestNum; i++) {
>       OMElement payload = getTestOMElement();
>       sender.sendReceiveNonBlocking(payload, callback);
> }
> succeeds, while:
> OMElement payload payload = getTestOMElement();
> for (int i = 0; i < execution.requestNum; i++) {
>       sender.sendReceiveNonBlocking(payload, callback);
> }
> fails, because (from the second send) the SOAP message is empty

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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to