tianping526 opened a new issue, #509:
URL: https://github.com/apache/rocketmq-clients/issues/509

   ### Before Creating the Bug Report
   
   - [X] I found a bug, not just asking a question, which should be created in 
[GitHub Discussions](https://github.com/apache/rocketmq-clients/discussions).
   
   - [X] I have searched the [GitHub 
Issues](https://github.com/apache/rocketmq-clients/issues) and [GitHub 
Discussions](https://github.com/apache/rocketmq-clients/discussions)  of this 
repository and believe that this is not a duplicate.
   
   - [X] I have confirmed that this bug belongs to the current repository, not 
other repositories of RocketMQ.
   
   
   ### Programming Language of the Client
   
   Go
   
   ### Runtime Platform Environment
   
   5.8.0-43-generic #49~20.04.1-Ubuntu SMP Fri Feb 5 09:57:56 UTC 2021 x86_64 
x86_64 x86_64 GNU/Linux
   
   ### RocketMQ Version of the Client/Server
   
   github.com/apache/rocketmq-clients/golang/v5 v5.0.1-rc.3
   
   ### Run or Compiler Version
   
   _No response_
   
   ### Describe the Bug
   
   rocketmq-clients/golang/[email protected]/rpc_client.go
   ```golang
   func (rc *rpcClient) GracefulStop() error {
        rc.mux.Lock()
        sugarBaseLogger.Warnf("close rpc client, target=%s", rc.target)
        closeResult := rc.conn.Close()
        rc.mux.Lock()
        return closeResult
   }
   ```
   the GracefulStop method did not release the lock correctly
   
   ### Steps to Reproduce
   
   calling GracefulStop method in parallel, the second concurrent process will 
block permanently
   
   ### What Did You Expect to See?
   
   Lock is released correctly
   
   ### What Did You See Instead?
   
   Lock not released correctly
   
   ### Additional Context
   
   _No response_


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

Reply via email to