kafka报文一直打印的问题

一、问题描述

今天开发了一个kafka消费者数据接收的功能，基本过程为分别启动本地的kafka服务和代码程序，在服务端手动发送消息，代码来进行接收消费。经测试，代码功能正常，但是再接收到一条kafka消息之后，便开始在后台疯狂打印日志，如图：

...
.2020-08-26 17:00:37.651 com.hikvision.js.facecompare.dao.CaptureFaceInfoDAO.insert DEBUG - <==    Updates: 1
.2020-08-26 17:00:37.651 org.mybatis.spring.SqlSessionUtils DEBUG - Closing non transactional SqlSession [org.apache.ibatis.session.defaults.DefaultSqlSession@76f8de1f]
.2020-08-26 17:00:37.652 com.hikvision.js.facecompare.service.impl.KafkaConsumerListener INFO - 一条kafka消息已经入库：1598432437652
.2020-08-26 17:00:37.658 org.apache.kafka.clients.consumer.internals.ConsumerCoordinator DEBUG - Committed offset 3 for partition SNAP_IMAGE_INFO_TOPIC-0
.2020-08-26 17:00:37.912 org.apache.kafka.clients.consumer.internals.AbstractCoordinator DEBUG - Received successful heartbeat response.
.2020-08-26 17:00:38.654 org.apache.kafka.clients.consumer.internals.ConsumerCoordinator DEBUG - Committed offset 3 for partition SNAP_IMAGE_INFO_TOPIC-0
.2020-08-26 17:00:39.654 org.apache.kafka.clients.consumer.internals.ConsumerCoordinator DEBUG - Committed offset 3 for partition SNAP_IMAGE_INFO_TOPIC-0
.2020-08-26 17:00:40.654 org.apache.kafka.clients.consumer.internals.ConsumerCoordinator DEBUG - Committed offset 3 for partition SNAP_IMAGE_INFO_TOPIC-0
.2020-08-26 17:00:40.910 org.apache.kafka.clients.consumer.internals.AbstractCoordinator DEBUG - Received successful heartbeat response.
.2020-08-26 17:00:41.657 org.apache.kafka.clients.consumer.internals.ConsumerCoordinator DEBUG - Committed offset 3 for partition SNAP_IMAGE_INFO_TOPIC-0
.2020-08-26 17:00:42.656 org.apache.kafka.clients.consumer.internals.ConsumerCoordinator DEBUG - Committed offset 3 for partition SNAP_IMAGE_INFO_TOPIC-0
.2020-08-26 17:00:43.656 org.apache.kafka.clients.consumer.internals.ConsumerCoordinator DEBUG - Committed offset 3 for partition SNAP_IMAGE_INFO_TOPIC-0
...

网上查询得知，需要设置对应类的日志打印级别，设置之后还是不行。

二、解决方法

在idea全局搜索ConsumerCoordinator 类发现，不止一个jar包中包含这个类，仔细分析发现其中一个包是我在代码调试过程中手动添加的外部jar包，这个jar包已经没什么用了，于是手动将该包移除，重新启动消费端程序，再次接受kafka消息，恢复正常，因此日志频繁打印的原因应该是两个jar包冲突。