No records on consumer poll when upgraded to 2.11-1.1.0

["M. Manna" <ma...@gmail.com>]

Hello,

we have recently upgraded to 2.11-1.1.0, but for our publish-subscribe
design we are still using Producer and Consumer API from 0.10.2.1. We
understand there are more enhanced features in new 1.1 API but we aren't
using those specific items.

Upon upgrade, we confirmed that some test messages can be exchanged. But
with the same configuration as our 0.10.2.1 setup, we see that
consumer.poll(2000L) call never returns any data. As a result we have a
huge queue of messages pending even though a simple command line consumer
is able to get them all.

But as soon as we increased the value to 4000L, we received all data. Is
this tweaking expected for any such upgrade? Or do we need to move to new
Producer/Consumer API?

Any suggestion is appreciated. Attached is the broker and consumer files.

Regards,

Re: No records on consumer poll when upgraded to 2.11-1.1.0

["M. Manna" <ma...@gmail.com>]

I just noticed that my max.poll.interval.ms was higher than
request.timeout.ms for consumer.properties. So I removed them to be the
default OOB. But even then it's not working.

It looks like addition 2s on consumer.poll call is giving me data after the
upgrade. I am not sure why this is happening. Is this expected for
2.11-1.1-.0 ? This means addition 2s delay on my poll time, which is what I
would like to avoid if possible.

Regards,

On 10 May 2018 at 18:47, M. Manna <ma...@gmail.com> wrote:

> Hello,
>
> we have recently upgraded to 2.11-1.1.0, but for our publish-subscribe
> design we are still using Producer and Consumer API from 0.10.2.1. We
> understand there are more enhanced features in new 1.1 API but we aren't
> using those specific items.
>
> Upon upgrade, we confirmed that some test messages can be exchanged. But
> with the same configuration as our 0.10.2.1 setup, we see that
> consumer.poll(2000L) call never returns any data. As a result we have a
> huge queue of messages pending even though a simple command line consumer
> is able to get them all.
>
> But as soon as we increased the value to 4000L, we received all data. Is
> this tweaking expected for any such upgrade? Or do we need to move to new
> Producer/Consumer API?
>
> Any suggestion is appreciated. Attached is the broker and consumer files.
>
> Regards,
>