VariableLinkedBlockingQueue's capacity can be not volatile

[Inuyasha-Monster]

as title , the field capacity not volatile , is there some concurrency issue ?

[Inuyasha-Monster]

add another point， that because there is no lock scope in the method that partially accesses the field

[michaelklishin]

In the client, this data structure is used to ensure inbound deliveries on a single channel. Since channels must not be shared between threads (this has been documented for many years), I don’t see a reason to use any synchronization mechanism on this field.

In other words, why change it now, a decade into the current consumer dispatch design?

[Inuyasha-Monster]

i got it , thx your reply