Hey there! Since you’ve already got ZooKeeper, Kafka broker, producers, and consumers up and running smoothly, the issue with launching the WordCountDemo is almost certainly tied to Windows-specific quirks or Kafka Streams-specific setup details. Let’s walk through the most common fixes step by step:

1. Verify Your Java Environment Setup #

First, double-check that your Java 8 environment is properly configured for Windows:

• Ensure JAVA_HOME is set to your Java 8 JDK directory (no spaces in the path—Windows hates spaces in classpaths). For example, C:\Java\jdk1.8.0_291 works better than C:\Program Files\Java\jdk1.8.0_291.
• Confirm %JAVA_HOME%\bin is added to your system PATH variable. Test this by opening a new command prompt and running:

  echo %JAVA_HOME%
  java -version
  

  Both commands should return valid, Java 8-specific output.

2. Manually Create Required Demo Topics #

The WordCountDemo relies on two topics by default: streams-plaintext-input (for input data) and streams-wordcount-output (for results). While newer Kafka versions auto-create topics, Kafka 1.0.0 might not handle this reliably on Windows. Create them manually first:

bin\windows\kafka-topics.bat --create --zookeeper localhost:2181 --replication-factor 1 --partitions 1 --topic streams-plaintext-input
bin\windows\kafka-topics.bat --create --zookeeper localhost:2181 --replication-factor 1 --partitions 1 --topic streams-wordcount-output

You can verify they exist with:

bin\windows\kafka-topics.bat --list --zookeeper localhost:2181

3. Fix Path & Command Line Quirks #

Windows has strict rules about paths and working directories:

• Make sure you’re running the command from the root directory of your Kafka installation. For example, if Kafka is installed at C:\kafka_2.11-1.0.0, first run:

  cd C:\kafka_2.11-1.0.0
  

  Then execute the kafka-run-class.bat command.
• If your Kafka path includes spaces (e.g., C:\Program Files\kafka...), wrap the entire path to kafka-run-class.bat in double quotes:

  "C:\Program Files\kafka_2.11-1.0.0\bin\windows\kafka-run-class.bat" org.apache.kafka.streams.examples.wordcount.WordCountDemo
  

4. Diagnose the Specific Exception #

The most critical step is to look at the exact error message in your command prompt. Here are common issues and fixes:

• ClassNotFoundException: This means the Kafka Streams JARs are missing or not in the classpath. Re-download and re-extract the Kafka 1.0.0 binary package to ensure no files are corrupted.
• Connection/Timeout Errors: Confirm ZooKeeper (port 2181) and Kafka broker (port 9092) are running locally. Test connectivity with:

  telnet localhost 9092
  

  If it fails, restart your Kafka services and check server.properties for correct port configurations.
• Topic Authorization Errors: Ensure your server.properties doesn’t have security settings enabled (Kafka 1.0.0 defaults to no authentication/authorization, so this is only an issue if you modified the config).

5. Validate Streams Configuration #

Check the default streams config file (config\streams.properties) to ensure:

• bootstrap.servers=localhost:9092
• zookeeper.connect=localhost:2181
  These values should match the ports your Kafka and ZooKeeper services are using.

Once you’ve worked through these steps, try launching the WordCountDemo again. If you still hit issues, share the exact error message and we can dive deeper!

内容的提问来源于stack exchange，提问作者Satyakam kaul