[I] [Enhancement] Fix lock leak risk in sendHeartbeatToBroker [rocketmq]

["yx9o (via GitHub)" <gi...@apache.org>]

yx9o opened a new issue, #10046:
URL: https://github.com/apache/rocketmq/issues/10046

   ### Before Creating the Enhancement Request
   
   - [x] I have confirmed that this should be classified as an enhancement rather than a bug/feature.
   
   
   ### Summary
   
   Ensuring all return paths after locking are inside a try-finally block so the lock is always released.
   
   ### Motivation
   
   Ensuring all return paths after locking are inside a try-finally block so the lock is always released.
   
   ### Describe the Solution You'd Like
   
   Ensuring all return paths after locking are inside a try-finally block so the lock is always released.
   
   ### Describe Alternatives You've Considered
   
   No
   
   ### 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: commits-unsubscribe@rocketmq.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] [Enhancement] Fix lock leak risk in sendHeartbeatToBroker [rocketmq]

["RongtongJin (via GitHub)" <gi...@apache.org>]

RongtongJin closed issue #10046: [Enhancement] Fix lock leak risk in sendHeartbeatToBroker
URL: https://github.com/apache/rocketmq/issues/10046


-- 
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: commits-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org