nats-io / nats.java / #1683

95%

Build Type

push

github

Committed by web-flow

Commit Message

Removing writerLock in favor of setting a flag to call flushBuffer (#1208)

* Removing writerLock in favor of setting a flag to call flushBuffer
* Instead of using writerLock around flushBuffer (socket flush), set a flag to tell the sendMessageBatch to flushBuffer after a write, instead of locking around send.

* better place to flush

* fixed api doc

* don't catch flush exception as it's likely a legit issue

Run Details

38 of 41 new or added lines in 1 file covered. (92.68%)

1 existing line in 1 file now uncovered.

11299 of 11852 relevant lines covered (95.33%)

0.95 hits per line