Spring-Kafka-Test已经封装了Kafka-test提供了注解式的一键开启Kafka Server的功能.
1.搭建工程
参考：0000.Eclipse+Maven+SpringBoot+MongoDB搭建工程 - 简书 (jianshu.com)
2.目录结构
image.png
3.Hello World
3.1.pom.xml中引入spring-kafka-test
<dependency>
<groupId>org.springframework.kafka</groupId>
<artifactId>spring-kafka-test</artifactId>
<scope>test</scope>
</dependency>
3.2.LaunchKafkaServer.java
@EmbeddedKafka启动Kafka Server
因为测试进程结束后Kafka Server就会被关闭
所以这里做了一个不会结束的进程来让Kafka Server保持生存。
右键->run as->junit test 启动
package study.kafka2;
import org.junit.Test;
import org.junit.runner.RunWith;
import org.springframework.boot.test.context.SpringBootTest;
import org.springframework.kafka.test.context.EmbeddedKafka;
import org.springframework.test.context.junit4.SpringRunner;
@SpringBootTest
@RunWith(SpringRunner.class)
@EmbeddedKafka(
count = 1,
ports = {9092},
brokerPropertiesLocation = "classpath:study/kafka2/kafka-server.properties")
public class LaunchKafkaServer {
@Test
public void testHelloWorld() throws InterruptedException {
while (true) {
Thread.sleep(5000);
}
}
}
3.3.kafka-server.properties
############################# Server Basics #############################
# The id of the broker. This must be set to a unique integer for each broker.
broker.id=0
############################# Socket Server Settings #############################
# The number of threads that the server uses for receiving requests from the network and sending responses to the network
num.network.threads=3
# The number of threads that the server uses for processing requests, which may include disk I/O
num.io.threads=8
# The send buffer (SO_SNDBUF) used by the socket server
socket.send.buffer.bytes=102400
# The receive buffer (SO_RCVBUF) used by the socket server
socket.receive.buffer.bytes=102400
# The maximum size of a request that the socket server will accept (protection against OOM)
socket.request.max.bytes=104857600
############################# Log Basics #############################
# A comma separated list of directories under which to store log files
#log.dirs=C:\\kafka_2.13-3.1.0\\kafka-logs
# The default number of log partitions per topic. More partitions allow greater
# parallelism for consumption, but this will also result in more files across
# the brokers.
num.partitions=1
# The number of threads per data directory to be used for log recovery at startup and flushing at shutdown.
# This value is recommended to be increased for installations with data dirs located in RAID array.
num.recovery.threads.per.data.dir=1
############################# Internal Topic Settings #############################
# The replication factor for the group metadata internal topics "__consumer_offsets" and "__transaction_state"
# For anything other than development testing, a value greater than 1 is recommended to ensure availability such as 3.
offsets.topic.replication.factor=1
transaction.state.log.replication.factor=1
transaction.state.log.min.isr=1
############################# Log Retention Policy #############################
# The minimum age of a log file to be eligible for deletion due to age
log.retention.hours=168
# A size-based retention policy for logs. Segments are pruned from the log unless the remaining
# segments drop below log.retention.bytes. Functions independently of log.retention.hours.
#log.retention.bytes=1073741824
# The maximum size of a log segment file. When this size is reached a new log segment will be created.
log.segment.bytes=1073741824
# The interval at which log segments are checked to see if they can be deleted according
# to the retention policies
log.retention.check.interval.ms=300000
############################# Zookeeper #############################
# Zookeeper connection string (see zookeeper docs for details).
# This is a comma separated host:port pairs, each corresponding to a zk
# server. e.g. "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002".
# You can also append an optional chroot string to the urls to specify the
# root directory for all kafka znodes.
#zookeeper.connect=localhost:2181
# Timeout in ms for connecting to zookeeper
#zookeeper.connection.timeout.ms=18000
############################# Group Coordinator Settings #############################
# The following configuration specifies the time, in milliseconds, that the GroupCoordinator will delay the initial consumer rebalance.
# The rebalance will be further delayed by the value of group.initial.rebalance.delay.ms as new members join the group, up to a maximum of max.poll.interval.ms.
# The default value for this is 3 seconds.
# We override this to 0 here as it makes for a better out-of-the-box experience for development and testing.
# However, in production environments the default value of 3 seconds is more suitable as this will help to avoid unnecessary, and potentially expensive, rebalances during application startup.
group.initial.rebalance.delay.ms=0
其他部分参考：0002.Kafka Server的安装与Spring-Kafka Helloworld - 简书 (jianshu.com)
3.4.右键App.java->run as->Java Application启动Listener
3.5.HelloWorldTest.java
右键->run as->junit test 启动
@SpringBootTest
@RunWith(SpringRunner.class)
public class HelloWorldTest {
@Autowired
private KafkaTemplate<Integer,String> kafkaTemplate;
@Test
public void testHelloWorld() throws InterruptedException {
System.out.println("====testHelloWorld run");
kafkaTemplate.send("topic.quick.helloWorld", "this is my first demo, Hello World!!!");
// 如果在数据送达kafka服务器之前进程就结束了的话，就会造成数据丢失
// 所以休眠5秒，让进程活着，为了使监听器有足够的时间监听到topic的数据
Thread.sleep(5000);
}
}
成功的话，控制台打出以下信息image.png
网友评论