Skip to main content

Redis Cache Issue – Why @Cacheable Didn’t Work (and Fix)

 Hi 👋, I’m Anandharaj.


Today’s learning is about Redis Cache in Spring Boot.  

We faced an interesting issue at work (Project) where @Cacheable didn’t behave as expected.


👉 The key takeaway: Avoid self-invocation when using @Cacheable methods.

Let me explain with code examples below.



❌ Non‑Working Code (Self‑Invocation Issue)

In the below snippet, the processData() method calls another @Cacheable method internalGetData() inside the same class. 
Because it’s an internal call, Spring’s proxy is bypassed, so caching never happens.







✅ Working Code (Fixed with separate bean)


To fix it, we separated the cached method into another Spring-managed bean (another class).
Now the call goes through the proxy and caching works as expected.



💡 Key Takeaways:
✔️ Avoid calling @Cacheable methods from within the same class.
✔️ Move the cached method to another Spring bean.
✔️ This ensures the proxy logic and caching work correctly.



Labels:

Comments

Post a Comment

Popular posts from this blog

🐱 Tomcat vs ⚡ Netty – Which One Should You Use?

🐱 Tomcat vs ⚡ Netty – Which One Should You Use? So recently I got curious about this too 🤔. Everywhere in Spring Boot tutorials we see Tomcat . Then suddenly while exploring Spring WebFlux , the name Netty pops up. And I was like – “Wait, who’s this Netty guy trying to replace Tomcat?” 😅 Let’s break it down with real-time examples , icons , and fun comparisons . 🐱 Tomcat – The Traditional Web Server Type: Servlet Container (blocking I/O) World: Used with Spring MVC Style: Thread-per-request model 👩‍💻 Pros: Stable, widely used, battle-tested Cons: Struggles with huge concurrent connections 👉 Example in real life: Tomcat is like a restaurant with fixed waiters 🍴. - Each customer = one thread/waiter - If too many customers come in at once → waiters run out → customers wait outside 🚪 ⚡ Netty – The Reactive Rockstar Type: Asynchronous Event-Driven Network Framework World: Default for Spring WebFlux Style: Event-lo...
Post a Comment
Read more

🎭 Spring’s Secret: Why @Transactional & Friends Betray You Silently

💡 Lesson Learned — Not a Prod Bug, But a Real Pain No, this wasn’t a production outage. Nobody screamed at me. But I sat for 3 hours wondering: “Why the heck is my @Transactional not rolling back!?” 😵‍💫 “Why is Redis cache not working?” 🤯 Turned out, the issue was one silent villain: 🧱 Self-invocation 🤷 What Is @Transactional ? If you're new: @Transactional = Tells Spring to start a DB transaction when a method is called. It’ll commit if everything’s okay. It’ll rollback if something fails. 🧠 Think of it like wrapping your code in: try { beginTransaction(); // your logic commit(); } catch(Exception e) { rollback(); } 🕵️ Real-Life Analogy — The Gateway Community 🏘️ Let me tell you about my society — it has a strict watchman at the gate. Here’s how it works: 🛂 Watchman = Spring Proxy 🏠 Your apartment = Your service class 🚪 Your room = A method inside that class 🏃 Scenario 1: Outsider Visits Your friend from outside...
Post a Comment
Read more

🧵 Virtual Threads in Java — The Ultimate Guide with Diagrams, Code & Interview Qs!

🚀 “How are Virtual Threads different from Thread Pools?” 😵 “Are they OS threads or JVM threads?” 🙃 “Should I still use CompletableFuture?” 🤯 “How do I even use them in real-time microservices?” 🧠 What are Virtual Threads? Virtual Threads (introduced in Java 21 as stable 🎉) are lightweight threads managed by the JVM instead of the OS kernel. 👉 They look like normal threads, but don’t hog OS resources like traditional threads. 🧠 What is the OS Kernel? 🏛️ OS Kernel = The Brain of the Operating System It’s the core part of your OS (Windows, Linux, Mac) that: Manages memory 🧠 Schedules threads 🕒 Talks to hardware 💻 Handles I/O operations 📨 When you create a traditional thread in Java, the JVM asks the OS Kernel to create a real OS-level thread. 🖼️ Imagine This... ┌───────────────────────────┐ │ Your Java Application │ └────────────┬──────────────┘ │ ...
Post a Comment
Read more