eBook – Guide Spring Cloud – NPI EA (cat=Spring Cloud)
announcement - icon

Let's get started with a Microservice Architecture with Spring Cloud:

>> Join Pro and download the eBook

eBook – Mockito – NPI EA (tag = Mockito)
announcement - icon

Mocking is an essential part of unit testing, and the Mockito library makes it easy to write clean and intuitive unit tests for your Java code.

Get started with mocking and improve your application tests using our Mockito guide:

Download the eBook

eBook – Java Concurrency – NPI EA (cat=Java Concurrency)
announcement - icon

Handling concurrency in an application can be a tricky process with many potential pitfalls. A solid grasp of the fundamentals will go a long way to help minimize these issues.

Get started with understanding multi-threaded applications with our Java Concurrency guide:

>> Download the eBook

eBook – Reactive – NPI EA (cat=Reactive)
announcement - icon

Spring 5 added support for reactive programming with the Spring WebFlux module, which has been improved upon ever since. Get started with the Reactor project basics and reactive programming in Spring Boot:

>> Join Pro and download the eBook

eBook – Java Streams – NPI EA (cat=Java Streams)
announcement - icon

Since its introduction in Java 8, the Stream API has become a staple of Java development. The basic operations like iterating, filtering, mapping sequences of elements are deceptively simple to use.

But these can also be overused and fall into some common pitfalls.

To get a better understanding on how Streams work and how to combine them with other language features, check out our guide to Java Streams:

>> Join Pro and download the eBook

eBook – Jackson – NPI EA (cat=Jackson)
announcement - icon

Do JSON right with Jackson

Download the E-book

eBook – HTTP Client – NPI EA (cat=Http Client-Side)
announcement - icon

Get the most out of the Apache HTTP Client

Download the E-book

eBook – Maven – NPI EA (cat = Maven)
announcement - icon

Get Started with Apache Maven:

Download the E-book

eBook – Persistence – NPI EA (cat=Persistence)
announcement - icon

Working on getting your persistence layer right with Spring?

Explore the eBook

eBook – RwS – NPI EA (cat=Spring MVC)
announcement - icon

Building a REST API with Spring?

Download the E-book

Course – LS – NPI EA (cat=Jackson)
announcement - icon

Get started with Spring and Spring Boot, through the Learn Spring course:

>> LEARN SPRING
Course – RWSB – NPI EA (cat=REST)
announcement - icon

Explore Spring Boot 3 and Spring 6 in-depth through building a full REST API with the framework:

>> The New “REST With Spring Boot”

Course – LSS – NPI EA (cat=Spring Security)
announcement - icon

Yes, Spring Security can be complex, from the more advanced functionality within the Core to the deep OAuth support in the framework.

I built the security material as two full courses - Core and OAuth, to get practical with these more complex scenarios. We explore when and how to use each feature and code through it on the backing project.

You can explore the course here:

>> Learn Spring Security

Course – LSD – NPI EA (tag=Spring Data JPA)
announcement - icon

Spring Data JPA is a great way to handle the complexity of JPA with the powerful simplicity of Spring Boot.

Get started with Spring Data JPA through the guided reference course:

>> CHECK OUT THE COURSE

Partner – Moderne – NPI EA (cat=Spring Boot)
announcement - icon

Refactor Java code safely — and automatically — with OpenRewrite.

Refactoring big codebases by hand is slow, risky, and easy to put off. That’s where OpenRewrite comes in. The open-source framework for large-scale, automated code transformations helps teams modernize safely and consistently.

Each month, the creators and maintainers of OpenRewrite at Moderne run live, hands-on training sessions — one for newcomers and one for experienced users. You’ll see how recipes work, how to apply them across projects, and how to modernize code with confidence.

Join the next session, bring your questions, and learn how to automate the kind of work that usually eats your sprint time.

Course – LJB – NPI EA (cat = Core Java)
announcement - icon

Code your way through and build up a solid, practical foundation of Java:

>> Learn Java Basics

Partner – LambdaTest – NPI EA (cat= Testing)
announcement - icon

Distributed systems often come with complex challenges such as service-to-service communication, state management, asynchronous messaging, security, and more.

Dapr (Distributed Application Runtime) provides a set of APIs and building blocks to address these challenges, abstracting away infrastructure so we can focus on business logic.

In this tutorial, we'll focus on Dapr's pub/sub API for message brokering. Using its Spring Boot integration, we'll simplify the creation of a loosely coupled, portable, and easily testable pub/sub messaging system:

>> Flexible Pub/Sub Messaging With Spring Boot and Dapr

1. Introduction

When working with Java programs that read input from the console, we use the Scanner class. It’s simple, powerful, and flexible enough to handle various types of input, including integers, doubles, and strings. However, one of the most common challenges developers face when working with a Scanner object is figuring out how to stop reading input once the task is complete.

Let’s consider a situation where we want to read multiple lines of input, process them, and then terminate the program gracefully. At first glance, it might seem that pressing the Return key a few times should signal to the program that input has ended. Unfortunately, the program continues to wait for more input, as it doesn’t inherently know when we’ve finished typing.

In this tutorial, we’ll explore how to terminate a Java Scanner after input is complete. First, we’ll discuss different strategies for terminating a scanner, and look at code examples that demonstrate correct approaches. Further, we’ll examine why certain basic attempts might fail. Lastly, we’ll conclude with best practices for writing clean, input-handling code in Java.

2. Terminating the Scanner Class

A Scanner connected to System.in continuously waits for input. From the coding perspective, as long as the user hasn’t explicitly told it to stop, it assumes more input may follow. Pressing the Return key simply indicates the end of one line, not the end of the entire input stream.

For instance, let’s consider a simple case of Scanner termination:

import java.util.Scanner;
public class SampleScanner {
    public static void main(String[] args) {
        Scanner scan = new Scanner(System.in);
        try {
            while (scan.hasNextLine()) {
                String line = scan.nextLine().toLowerCase();
                System.out.println(line);
            }
        } finally {
           scan.close();
        }
    }
}

At first glance, the logic seems simple. The loop keeps reading lines and prints them until no more lines are available. However, unless the program receives an explicit end-of-input signal, hasNextLine() keeps returning true. That’s why the loop doesn’t terminate automatically when the user simply presses Return several times.

3. Scanner Termination Considerations

Notably, care should be taken when using Scanner in terms of its termination.

3.1. Closing the Scanner Class

When working with Scanner, it’s important to close the resource to avoid memory leaks. However, if the Scanner is reading from System.in, closing it also closes the underlying input stream, which cannot be reopened.

This may result in further errors.

3.2. Graceful Termination vs. Forced Exit

Some examples show the use of System.exit(0) to terminate immediately. While this works, it’s a blunt tool. A cleaner approach is to break out of the loop, enabling the program to finish naturally.

This is especially important when multithreading.

4. Wrongly Using the == Operator to Check the Input

If we try to compare input directly using == or by checking whether the input equals an empty string to terminate the Scanner input, it mostly won’t work. One exception is targeting empty strings specifically.

For example, let’s consider the scan.nextLine comparison in SampleScannerScan.java:

import java.util.Scanner;
public class SampleScannerScan {
    public static void main(String[] args) {
        Scanner scan = new Scanner(System.in);
        try {
            while (scan.hasNextLine()) {
                String line = scan.nextLine();
                if (line == null) {
                    System.out.println("Exiting program (null check)...");
                    System.exit(0);
                }
                System.out.println("Input was: " + line);
            }
        } finally {
            scan.close();
        }
    }
}

The == operator checks whether two references point to the same object, not whether the contents of two strings are equal. Therefore, even if two strings contain the same characters, == may return false. To properly compare strings, we need to use .equals() or .isEmpty().

5. Using End-of-File (EOF) Marker

The most direct approach for actually closing Scanner is to let the user indicate end-of-input using the operating system EOF marker. On Unix-like systems, this is a control character indicated via CTRL+D, while Windows uses CTRL+Z. When the EOF marker is sent, hasNextLine() returns false, and the loop ends naturally.

Let’s look at the sample code in EOFExample.java that demonstrates the use of EOF:

import java.util.Scanner;
public class EOFExample {
    public static void main(String[] args) {
        Scanner scan = new Scanner(System.in);
        try {
            System.out.println("Enter text (press CTRL+D on Unix/Mac or CTRL+Z on Windows to end):");
            while (scan.hasNextLine()) {
                String line = scan.nextLine();
                System.out.println("You entered: " + line);
            }
            System.out.println("End of input detected. Program terminated.");
        } finally {
            scan.close();
        }
    }
}

This approach works without modifying the code, but it relies on the user knowing how to send the EOF signal. However, it may not always be the most user-friendly option.

5. Using a Sentinel Value

Another common method for terminating Scanner gracefully is to define a special keyword that indicates the user is finished. This sentinel value could be something simple like exit, quit, or even a symbol such as ##. The program can check each line, and when it matches the sentinel, it terminates gracefully.

Let’s modify the SampleScannerSentinel.java to check the Scanner termination:

import java.util.Scanner;
public class SampleScannerSentinel {
    public static void main(String[] args) {
        Scanner scan = new Scanner(System.in);
        try {
            while (scan.hasNextLine()) {
                String line = scan.nextLine().toLowerCase();
                if (line.equals("exit")) {
                    System.out.println("Exiting program...");
                    break;
                }
                System.out.println(line);
            }
        } finally {
            scan.close();
        }
    }
}

In this version, typing exit immediately ends the loop. This approach is easier, as the user knows exactly how to signal completion.

6. Using a do-while Loop

Another choice for completing Scanner is to use a do-while loop. This structure ensures that at least one line is read before the termination condition is checked. Let’s look at the code from the SampleScanner.java file, but with a do-while loop (DoWhileScanner.java):

import java.util.Scanner;
public class DoWhileScanner {
    public static void main(String[] args) {
        Scanner sc = new Scanner(System.in);
        String input;
        do {
            input = sc.nextLine();
            System.out.println(input);
        } while (!input.equals("exit"));
        sc.close();
    }
}

In this example, the program keeps looping until the sentinel word exit is typed. It’s clean, straightforward, and ensures the immediate processing of user input.

7. Conclusion

In this article, we covered how to terminate Scanner when input is complete in Java. The two most effective approaches either employ the system EOF marker or define a sentinel value like exit. While the EOF marker is efficient, the sentinel method often provides a clearer experience for users. Furthermore, we also learned why naive solutions like checking for null or using == fail.

The source code is available over on GitHub.

Baeldung Pro – NPI EA (cat = Baeldung)
announcement - icon

Baeldung Pro comes with both absolutely No-Ads as well as finally with Dark Mode, for a clean learning experience:

>> Explore a clean Baeldung

Once the early-adopter seats are all used, the price will go up and stay at $33/year.

eBook – HTTP Client – NPI EA (cat=HTTP Client-Side)
announcement - icon

The Apache HTTP Client is a very robust library, suitable for both simple and advanced use cases when testing HTTP endpoints. Check out our guide covering basic request and response handling, as well as security, cookies, timeouts, and more:

>> Download the eBook

eBook – Java Concurrency – NPI EA (cat=Java Concurrency)
announcement - icon

Handling concurrency in an application can be a tricky process with many potential pitfalls. A solid grasp of the fundamentals will go a long way to help minimize these issues.

Get started with understanding multi-threaded applications with our Java Concurrency guide:

>> Download the eBook

eBook – Java Streams – NPI EA (cat=Java Streams)
announcement - icon

Since its introduction in Java 8, the Stream API has become a staple of Java development. The basic operations like iterating, filtering, mapping sequences of elements are deceptively simple to use.

But these can also be overused and fall into some common pitfalls.

To get a better understanding on how Streams work and how to combine them with other language features, check out our guide to Java Streams:

>> Join Pro and download the eBook

eBook – Persistence – NPI EA (cat=Persistence)
announcement - icon

Working on getting your persistence layer right with Spring?

Explore the eBook

Course – LS – NPI EA (cat=REST)

announcement - icon

Get started with Spring Boot and with core Spring, through the Learn Spring course:

>> CHECK OUT THE COURSE

Partner – Moderne – NPI EA (tag=Refactoring)
announcement - icon

Modern Java teams move fast — but codebases don’t always keep up. Frameworks change, dependencies drift, and tech debt builds until it starts to drag on delivery. OpenRewrite was built to fix that: an open-source refactoring engine that automates repetitive code changes while keeping developer intent intact.

The monthly training series, led by the creators and maintainers of OpenRewrite at Moderne, walks through real-world migrations and modernization patterns. Whether you’re new to recipes or ready to write your own, you’ll learn practical ways to refactor safely and at scale.

If you’ve ever wished refactoring felt as natural — and as fast — as writing code, this is a good place to start.

eBook Jackson – NPI EA – 3 (cat = Jackson)