Producer–Consumer Problem in Java Using BlockingQueue

-

The Producer–Consumer problem is one of the most important multi-threading patterns in Java. Traditionally, developers used wait and notify to coordinate threads, but this approach is complex and error-prone. Modern Java provides a cleaner solution: BlockingQueue.

1. What is the Producer–Consumer Problem?

Two types of threads share a common buffer:

  • Producer → Generates data and puts it into the buffer
  • Consumer → Retrieves data from the buffer and processes it

The challenge: prevent producers from writing when the buffer is full and consumers from reading when the buffer is empty.

2. Problems with wait()/notify()

The older approach required:

  • Manual locking
  • Complex condition handling
  • Risk of deadlocks
  • Hard to debug

BlockingQueue solves these issues with built-in thread management.

3. Why BlockingQueue?

BlockingQueue handles synchronization internally. Its key methods:

  • put() – waits if the queue is full
  • take() – waits if the queue is empty

No need for wait(), notify(), or synchronized blocks.

4. Example Implementation (Producer + Consumer)

import java.util.concurrent.*;

public class ProducerConsumerDemo {

    public static void main(String[] args) {
        BlockingQueue queue = new ArrayBlockingQueue<>(5);

        Runnable producer = () -> {
            int value = 1;
            try {
                while (true) {
                    queue.put(value);
                    System.out.println("Produced: " + value);
                    value++;
                    Thread.sleep(500);
                }
            } catch (Exception e) {
                e.printStackTrace();
            }
        };

        Runnable consumer = () -> {
            try {
                while (true) {
                    int val = queue.take();
                    System.out.println("Consumed: " + val);
                    Thread.sleep(800);
                }
            } catch (Exception e) {
                e.printStackTrace();
            }
        };

        new Thread(producer).start();
        new Thread(consumer).start();
    }
}

5. Multiple Producers & Consumers

ExecutorService service = Executors.newFixedThreadPool(4);

service.submit(producer);
service.submit(producer);
service.submit(consumer);
service.submit(consumer);

6. Graceful Shutdown Strategy

Use a poison pill:

queue.put(-1); // special value indicating stop

Consumers stop when they read -1.

7. Real-World Use Cases

  • Logging frameworks
  • Thread pool work queues
  • Messaging systems
  • Data streaming pipelines
  • Producer–Consumer microservices

Conclusion

BlockingQueue simplifies the producer–consumer problem by handling all synchronization internally. It is modern, cleaner, thread-safe, and widely used in enterprise applications.

Comments

Post a Comment

Popular posts from this blog

Spring Boot on AWS EC2: Upload to S3 Securely Using IAM Role

-
When running a Spring Boot application on AWS EC2 , the most common security mistake is hardcoding AWS access keys inside application.properties . This is unnecessary and risky. AWS already provides a secure mechanism: IAM Roles attached to EC2 . In this blog, you will learn how to upload and download files to Amazon S3 from Spring Boot running on EC2 without any access keys , using: Spring Profiles AWS SDK v2 Instance Metadata Service (IMDS) IAM Roles Why Access Keys Are a Bad Idea on EC2 Typical S3 setups use: Access key Secret key Region Bucket This works only for local development. It should NOT be used on EC2. Problems with access keys: Stored in config or code (high risk) Might leak through Git, logs, or screenshots Require manual rotation Not needed if app runs on EC2 AWS automatically manages temporary credentials using the EC2 Instance Profile (IAM Role) . Architecture: EC2 → IAM Role → S3 Spring Boot app r...
Read more

Java Streams Intermediate Operations Explained with Examples

-
Image
The Java Stream API lets you process collections in a fluent, declarative style. In this post, we’ll walk through the most useful intermediate operations with simple examples. Note: Examples below use Java 8 compatible collect(Collectors.toList()) . If you’re on Java 16+, you can replace it with toList() . 1) filter() — Select elements by a condition Keeps only elements that match the predicate. List<Integer> list = Arrays.asList(1,2,3,4,5,6,7,8,9,10); List<Integer> res = list.stream() .filter(num -> num % 2 != 0) // keep only odd numbers .collect(Collectors.toList()); System.out.println(res); // [1, 3, 5, 7, 9] 2) map() — Transform each element Applies a function to every element and returns a stream of results. List<String> strs = Arrays.asList("rama", "anjaneya", "krishna"); List<String> upper = strs.stream() .map(String::toUpperCase) .collect(Collectors.toList()); System.o...
Read more

ConcurrentHashMap vs Synchronized HashMap in Java

-
Image
Introduction In multi-threaded Java applications, managing shared data safely and efficiently is crucial. Two common approaches are using Synchronized HashMap (via Collections.synchronizedMap(...) ) and ConcurrentHashMap . While both aim to provide thread-safety, their implementations and performance characteristics differ significantly. This post explores these differences in detail. What is a Synchronized HashMap? Created by wrapping a regular HashMap using: Map<K, V> syncMap = Collections.synchronizedMap(new HashMap<>()); Enforces synchronization at the object level , meaning only one thread can access the map at any time (read or write). Supports null keys and values since it relies on HashMap behavior. Iterators are fail-fast , throwing ConcurrentModificationException if the map is modified while iterating. Simpler implementation, suitable when concurrency is low or performance is not cri...
Read more