nats.java

nats.java copied to clipboard

ConsumerContext - fail fast with push consumers to prevent API calls "hanging" in consume() callbacks and interators

roeschter

Add nullability annotations

4

### Proposed change Please annotate the API, including return types and parameters, with `@javax.annotations.NonNull` or `@javax.annotations.Nullable` as appropriate so that users of the API know what can and can't be...

matthewadams

scottf

- Increasing `reconnectWait` to wait a bit longer. A message put into the `reconnectOutgoing` queue will get immediately, regardless of this wait time. Only if we are stopped will we...

MauriceVanVeen

Slow memory leak

6

### Observed behavior My pods that are running the NATS Java client are consuming more and more memory. I'm not using JetStream. There are slow consumers 1-2 times a week...

tinder-marissanovak

When `maxBatch`, `maxBytes`, `maxExpires` are exceeded there is only a timeout but no status message

1

### Observed behavior When setting `maxBatch`, `maxBytes` or `maxExpires` on the `ConsumerConfiguration`, and we exceed this value while pulling for messages, we don't get informed about this and only wait...

MauriceVanVeen

Resolves https://github.com/nats-io/nats.java/issues/1194 Simple potential fix is enabling `raiseStatusWarnings` in the `_pull(..)`. Would keep the behaviour the same, just informing the user of the status message being hit: ``` Aug 09,...

MauriceVanVeen

* Reduces thread usage when many pull consumers * Scheduler uses nano time making it better immune to time shifts

scottf

MessageConsumer.isFinished() after .stop() will never report true on empty stream or after seeing messages with no future messages in stream

1

### Observed behavior When testing some of the graceful closure of MessageConsumer I came across MessageConsumerExample. This tells me to call consumerContext.consume( handler ), and then when finished I can...

wjnicholson

MessageManager.lastMsgReceived uses wall clock

2

### Observed behavior `lastMsgReceived` is set using `System.currentTimeMillis()`, as a result, it is susceptible to changes in the system clock. For example, if the system clock jumps into the future...

powturns