You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am currently using the jasync client in Vert.x. Is there a potential thread-safety issue with MySQLFrameDecoder? When we call sendQuery, it is executed on vert.x-eventloop-thread-0, where queryProcessStarted is invoked, setting this.isInQuery = true. However, during decoding, it might switch to a different thread, such as vert.x-eventloop-thread-1. Could this cause this.isInQuery to become invisible? Should we add the volatile keyword to the relevant variable? Thanks
The text was updated successfully, but these errors were encountered:
Hi, I am currently using the jasync client in Vert.x. Is there a potential thread-safety issue with MySQLFrameDecoder? When we call sendQuery, it is executed on vert.x-eventloop-thread-0, where queryProcessStarted is invoked, setting this.isInQuery = true. However, during decoding, it might switch to a different thread, such as vert.x-eventloop-thread-1. Could this cause this.isInQuery to become invisible? Should we add the volatile keyword to the relevant variable? Thanks


The text was updated successfully, but these errors were encountered: