Make use compareAndSet instead lock

[laststem]

Changes

1. Use compareAndSwap operation: CAS operation is more efficient than lock + unlock operation.
2. Set the parameters((superStreamRouting, producerCustomizer, ...) required to create a producer in advance : The parameters used to create a producer have no effect after the producer has been created, so i changed them to only have an effect when the producer is not initialized.
3. Rename streamConverter to streamMessageConverter.

New found

• If send() and close() are executed at the same time, there is a race condition where producer becomes null but trying to call a method on producer

[artembilan]

This is exactly the problem we are trying to cover with a Lock.
Imaging the situation when several threads concurrently call this method.
So, the first one calls compareAndSet() and enters into a block to create a producer.
The second one got false for the compareAndSet() and goes to the end of the method.
Since the first one has not finished its work for producer initialization, the second one ends up with a null.

Do I miss anything?

[laststem]

You're right. my mistake.

[artembilan]

I think we need to revert all your changes, and just add extra if (this.producer == null) { before calling lock().
This way only first calls to the createOrGetProducer() would suffer from Lock delay.

[ngocnhan-tran1996]

@laststem

As @artembilan said
I have a PR #2874 for adding condition this.producer. You can check out and continue to contributing your idea

[artembilan]

Well, I even would say that this is a duplicate of that #2874. So, closed respectively .
@laststem , feel free to come back to us with any other contribution. Thank you for your effort!