From 7b5225e8db05bd236cafa955223212c2db435bc2 Mon Sep 17 00:00:00 2001
From: Ulisses Lima <ulisseslima@users.noreply.github.com>
Date: Tue, 28 Nov 2023 12:14:50 -0300
Subject: [PATCH] BAEL-7022 Why wait must be called in a synchronized block -
 Changing Boolean to primitive

Based on a comment.
---
 .../com/baeldung/wait_synchronization/ConditionChecker.java   | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/core-java-modules/core-java-concurrency-advanced-5/src/main/java/com/baeldung/wait_synchronization/ConditionChecker.java b/core-java-modules/core-java-concurrency-advanced-5/src/main/java/com/baeldung/wait_synchronization/ConditionChecker.java
index dca36fe7cb..34e0a7522b 100644
--- a/core-java-modules/core-java-concurrency-advanced-5/src/main/java/com/baeldung/wait_synchronization/ConditionChecker.java
+++ b/core-java-modules/core-java-concurrency-advanced-5/src/main/java/com/baeldung/wait_synchronization/ConditionChecker.java
@@ -2,7 +2,7 @@ package com.baeldung.wait_synchronization;
 
 public class ConditionChecker {
 
-    private volatile Boolean jobIsDone;
+    private volatile boolean jobIsDone;
     private final Object lock = new Object();
 
     public void ensureCondition() {
@@ -21,4 +21,4 @@ public class ConditionChecker {
             lock.notify();
         }
     }
-}
\ No newline at end of file
+}