Ashutosh-Panda2004 commented on issue #16533:
URL: https://github.com/apache/dubbo/issues/16533#issuecomment-6348759242

   Reproduced this on `843b98b`, the commit in the report. I compiled the 
unmodified `DefaultFuture` and ran it with a `MockedChannel`, a `Request` and a 
`ThreadlessExecutor`, Maven Central is blocked in my sandbox so this was a 
`javac` harness rather than the full test suite.
   
   Calling `cancel(false)` twice, cancelling after `DefaultFuture.received()` 
with an OK response, and cancelling after a timeout response all threw the same 
error:
   
   ​```text
   repeated cancel => THREW java.lang.NullPointerException: Cannot invoke 
"org.apache.dubbo.remoting.exchange.support.DefaultFuture.getExecutor()" 
because "<parameter1>" is null
   cancel after response => THREW java.lang.NullPointerException: Cannot invoke 
"org.apache.dubbo.remoting.exchange.support.DefaultFuture.getExecutor()" 
because "<parameter1>" is null
   cancel after timeout => THREW java.lang.NullPointerException: Cannot invoke 
"org.apache.dubbo.remoting.exchange.support.DefaultFuture.getExecutor()" 
because "<parameter1>" is null
   ​```
   
   Looks like the cause in the report is right, `FUTURES.remove(id)` is already 
null on the second call.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to