Cannot deserialize / JSON parse error (Jackson)

Q: Add a default constructor

When to use: Use this when you have a parameterized constructor but no default constructor.. Jackson needs a default (no-arguments) constructor to instantiate the object before setting fields via setters or reflection.

Q: Fix JSON field name mismatch

When to use: Use this when your JSON keys don't match your Java field names.. Jackson expects JSON keys to match Java variable names exactly. If they differ, use @JsonProperty to map them.

Q: Fix data type mismatch

When to use: Use this when your JSON sends a String but your Java field expects an Integer.. Ensure the JSON data type matches the Java field type. Jackson cannot convert "abc" to an Integer.

🔴 The Error You're Seeing

Confirm this matches your console output. If it does, you're in the right place.

ERROR LOG

2023-10-25 10:15:30.812  WARN 12345 --- [nio-8080-exec-1] .w.s.m.s.DefaultHandlerExceptionResolver : Resolved [org.springframework.http.converter.HttpMessageNotReadableException: JSON parse error: Cannot construct instance of `com.devinhyderabad.dto.UserRequest` (although at least one Creator exists): cannot deserialize from Object value (no delegate- or property-based Creator)]

2023-10-25 10:15:30.812 ERROR 12345 --- [nio-8080-exec-1] o.a.c.c.C.[.[.[/].[dispatcherServlet]    : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed: org.springframework.http.converter.HttpMessageNotReadableException: JSON parse error: Cannot construct instance of `com.devinhyderabad.dto.UserRequest`] with root cause

com.fasterxml.jackson.databind.exc.InvalidDefinitionException: Cannot construct instance of `com.devinhyderabad.dto.UserRequest`

⚡ Quick Fix Works 80% of the time

Add a default (no-args) constructor to your DTO class.

public class UserRequest {
    public UserRequest() {} // Default constructor
    // ...
}

🧠 Why this Happens

Tap to expand the deep technical explanation

When a client sends a POST request with JSON, Spring Boot uses the Jackson library to convert that JSON into your Java object. If the JSON is malformed, missing required fields, or the Java class doesn't have a default constructor, Jackson throws this exception.

The HITEC City Parking Spot Analogy:

It's like trying to translate a sentence from English to French, but the dictionary is missing a word. The translator (Jackson) can't finish the job.

🔁 How to Reproduce Confirm this is your error

Send a JSON body whose value type does not match your DTO (for example a number where the field is a String) using curl or Postman. Jackson throws HttpMessageNotReadableException / Cannot deserialize.

🛠️ Solutions (3 Ways to Fix)

Solution 1✓ Most common cause

Add a default constructor

👉 Use this when you have a parameterized constructor but no default constructor.

Jackson needs a default (no-arguments) constructor to instantiate the object before setting fields via setters or reflection.

public class UserRequest {
    public UserRequest() {} // Add this

    public UserRequest(String name) { ... }
}

Solution 2

Fix JSON field name mismatch

👉 Use this when your JSON keys don't match your Java field names.

Jackson expects JSON keys to match Java variable names exactly. If they differ, use @JsonProperty to map them.

public class UserRequest {
    @JsonProperty("user_name")
    private String userName;
}

Solution 3

Fix data type mismatch

👉 Use this when your JSON sends a String but your Java field expects an Integer.

Ensure the JSON data type matches the Java field type. Jackson cannot convert "abc" to an Integer.

// JSON: { "age": "abc" } -> FAILS
// JSON: { "age": 25 } -> WORKS

public class UserRequest {
    private Integer age;
}

📋 Version Notes

Spring Boot 2.x

Uses Jackson 2.x. Standard deserialization behavior.

Spring Boot 3.x

Uses Jackson 2.15+. Stricter date/time handling.

🛡️ How to Prevent This Next Time

Always use DTOs (Data Transfer Objects) for request bodies, and add validation annotations like @Valid to catch bad data early.