[ROCKETMQ-35] Consumer client can’t persist consume offset table to Broker

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 4.0.0-incubating
• Fix Version/s: 4.0.0-incubating
• Component/s: rocketmq-client
• Assignee: Xiaorui Wang
• Reporter: qinliujie
• Created: 06/Jan/17 16:17
• Updated: 23/Jan/17 09:23
• Resolved: 23/Jan/17 08:43

Description

RocketMQ version:4.0.0-SNAPSHOT

When I use the consumer which in example/quickstart and used MessageListenerConcurrently MessageListener,I found that the consumer would reconsume message when I restarted it everytime.That is no sense,So I printed the log,found that when the consumer used RemoteBrokerOffsetStore to persist the consume offset table which always be zero.

I found that the inner class ConsumeRequest in ConsumeMessageConcurrentlyService class has a bug in it.

Let's have a see.

```java
consumeMessageContext.getProps().put(MixAll.CONSUME_CONTEXT_TYPE, returnType.name());
```

the consumeMessageContext not null only when ConsumeMessageConcurrentlyService.this.defaultMQPushConsumerImpl.hasHook() be TRUE.In the code,there is no IF clause,So,sometime will be cause NPE and can't update the consume offset table.

Solution:

Just remove the code above.

Issue Links

• links to: GitHub Pull Request #32