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 "Roger Nell (JIRA)" <ji...@apache.org> on 2006/03/16 22:32:58 UTC

[jira] Created: (AXIS2-498) The ultimate asynchrony!! - Lies, Lies, Damn Lies!

The ultimate asynchrony!! - Lies, Lies, Damn Lies!
--------------------------------------------------

         Key: AXIS2-498
         URL: http://issues.apache.org/jira/browse/AXIS2-498
     Project: Apache Axis 2.0 (Axis2)
        Type: Bug
  Components: client-api  
    Versions: 0.94    
    Reporter: Roger Nell


Sorry for the aggressive title, I had a moment of weakness.

Looking at your example: 
   EchoNonBlockingDualClient.java

The code after the:
   sender.sendReceiveNonblocking( payload, callback );
is not called until the callback completes!  I expect the send() to complete immediately and not wait for the callback.  This does not appear to run asynchronously.

I can test this by putting a long delay in the callback:
      Callback callback = new Callback() {
                public void onComplete( AsyncResult result ) {
                    try {
                        sleep( 60000 );
                        System.out.println( "In callback" )
                        ..etc..

and adding a 
   println( "sent" ) 

immediately after 
  sender.sendReceiveNonblocking( payload, callback );

and the output is:
   In callback
   sent



-- 
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-498) The ultimate asynchrony!! - Lies, Lies, Damn Lies!

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

    Fix Version: 0.95
     Resolution: Fixed

just adding following line I was able to fix that

 mc.setProperty(MessageContext.TRANSPORT_NON_BLOCKING, Boolean.TRUE);


thx for pointing this out

> The ultimate asynchrony!! - Lies, Lies, Damn Lies!
> --------------------------------------------------
>
>          Key: AXIS2-498
>          URL: http://issues.apache.org/jira/browse/AXIS2-498
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug
>   Components: client-api
>     Versions: 0.94
>     Reporter: rnell
>      Fix For: 0.95

>
> Sorry for the aggressive title, I had a moment of weakness.
> Looking at your example: 
>    EchoNonBlockingDualClient.java
> The code after the:
>    sender.sendReceiveNonblocking( payload, callback );
> is not called until the callback completes!  I expect the send() to complete immediately and not wait for the callback.  This does not appear to run asynchronously.
> I can test this by putting a long delay in the callback:
>       Callback callback = new Callback() {
>                 public void onComplete( AsyncResult result ) {
>                     try {
>                         sleep( 60000 );
>                         System.out.println( "In callback" )
>                         ..etc..
> and adding a 
>    println( "sent" ) 
> immediately after 
>   sender.sendReceiveNonblocking( payload, callback );
> and the output is:
>    In callback
>    sent

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