Strange Jackson exception being thrown when serializing Hibernate object

Question

Jackson is throwing a weird exception that I don't know how to fix. I'm using Spring, Hibernate and Jackson.

I have already considered that lazy-loading is causing the problem, but I have taken measures to tell Jackson to NOT process various properties as follows:

@JsonIgnoreProperties({ "sentMessages", "receivedMessages", "educationFacility" })
public class Director extends UserAccount implements EducationFacilityUser {
   ....
}

I have done the same thing for all the other UserAccount subclasses as well.

Here's the exception being thrown:

org.codehaus.jackson.map.JsonMappingException: No serializer found for class org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer and no properties discovered to create BeanSerializer (to avoid exception, disable SerializationConfig.Feature.FAIL_ON_EMPTY_BEANS) ) (through reference chain: java.util.ArrayList[46]->jobprep.domain.educationfacility.Director_$$_javassist_2["handler"])
    at org.codehaus.jackson.map.ser.StdSerializerProvider$1.serialize(StdSerializerProvider.java:62)
    at org.codehaus.jackson.map.ser.BeanPropertyWriter.serializeAsField(BeanPropertyWriter.java:268)
    at org.codehaus.jackson.map.ser.BeanSerializer.serializeFields(BeanSerializer.java:146)
    at org.codehaus.jackson.map.ser.BeanSerializer.serialize(BeanSerializer.java:118)
    at org.codehaus.jackson.map.ser.ContainerSerializers$IndexedListSerializer.serializeContents(ContainerSerializers.java:236)
    at org.codehaus.jackson.map.ser.ContainerSerializers$IndexedListSerializer.serializeContents(ContainerSerializers.java:189)
    at org.codehaus.jackson.map.ser.ContainerSerializers$AsArraySerializer.serialize(ContainerSerializers.java:111)
    at org.codehaus.jackson.map.ser.StdSerializerProvider._serializeValue(StdSerializerProvider.java:296)
    at org.codehaus.jackson.map.ser.StdSerializerProvider.serializeValue(StdSerializerProvider.java:224)
    at org.codehaus.jackson.map.ObjectMapper.writeValue(ObjectMapper.java:925)
    at org.springframework.http.converter.json.MappingJacksonHttpMessageConverter.writeInternal(MappingJacksonHttpMessageConverter.java:153)

Suggestions on how I can get more info to see what's causing this? Anyone know how to fix it?

EDIT: I discovered that getHander() and other get*() methods exist on the proxy object. GRR!! Is there any way I can tell Jackson to not process anything on the proxy, or am I sol? This is really weird because the method that spits out the JSON only crashes under certain circumstances, not all the time. Nonetheless, it's due to the get*() methods on the proxy object.

Aside: Proxies are evil. They disrupt Jackson, equals() and many other parts of regular Java programming. I am tempted to ditch Hibernate altogether :/

Arr you returning an object of type `Director` from your controller? — skaffman, Dec 06 '10 at 00:02
@btiernay: Looks like it, yeah. The good news is that Tatu is pretty good at addressing these things. — skaffman, Dec 06 '10 at 00:13
@skaffman: I am returning a list of all UserAccount types, one of which is a Director... so yeah. — egervari, Dec 06 '10 at 00:18
@btiernay: I don't know if it's Jira related. Is this a bug, or is this how it's supposed to work? If anything, I think this is Hibernate's fault. Or is it? I have no idea. I just want it fixed :( — egervari, Dec 06 '10 at 00:19
The solution for me was simply adding the appropriate getters and setters as mentioned by OhadR. — JStrahl, Mar 27 '12 at 17:25
Can't agree more. Proxies are evil. They give Java a bad name. As does Hibernate. — Alex Worden, Jan 07 '15 at 16:19

score 74 · Answer 1 · edited May 23 '17 at 10:31

74

I had a similar problem with lazy loading via the hibernate proxy object. Got around it by annotating the class having lazyloaded private properties with:

@JsonIgnoreProperties({"hibernateLazyInitializer", "handler"})

I assume you can add the properties on your proxy object that breaks the JSON serialization to that annotation.

Avoid Jackson serialization on non fetched lazy objects

edited May 23 '17 at 10:31

Community

1
1

answered Jan 04 '11 at 07:27

Claes Mogren

2,126
1
26
34

2

In my case, the exception was about a lazy proxy, but it was misleading. From the debugger I saw that the exception was thrown when it tried to serialize a property named `handler`. Adding this annotation, naturally, prevented jackson from attempting to serialize it. Right on the spot! Thanks a lot! – acdcjunior Feb 13 '14 at 00:25

skaffman · Accepted Answer · 2010-12-06T00:21:57.980

38

It's not ideal, but you could disable Jackson's auto-discovery of JSON properties, using @JsonAutoDetect at the class level. This would prevent it from trying to handle the Javassist stuff (and failing).

This means that you then have to annotate each getter manually (with @JsonProperty), but that's not necessarily a bad thing, since it keeps things explicit.

edited Dec 06 '10 at 00:21

answered Dec 06 '10 at 00:10

skaffman

398,947
96
818
769

Yep, that's pretty much what I did. It's not so bad I guess, but it makes some of my classes a little bloated with annotations all over the place. I guess it can't be helped. – egervari Dec 06 '10 at 01:42
2

@egervari: It's the way of the future, you know, like silver suits and robots. – skaffman Dec 06 '10 at 08:06
1

For what it's worth, you can also use mix-in annotations (http://wiki.fasterxml.com/JacksonMixInAnnotations) to keep annotations separate; not more light-weight but bit cleaner. – StaxMan Dec 07 '10 at 17:04
@egervari how did you disable auto-discovery of JSON properties using @JsonAutoDetect? – Kevin Bowersox Sep 26 '11 at 18:51
6

You can disable Jackson Auto Discovery by @JsonAutoDetect(fieldVisibility = JsonAutoDetect.Visibility.NONE, getterVisibility = JsonAudtoDetect.Visibility.NONE) – Kevin Bowersox Sep 26 '11 at 19:47
This helped me. I resolved this same issue by actually defining getters (I expected it to find attributes via reflection). As soon as there were getters, this error disappeared :) – KOGI Mar 08 '12 at 20:52
I also had to add `isGetterVisibility = JsonAutoDetect.Visibility.NONE` – Eli Ganem Apr 04 '13 at 10:15
If you use @ JsonAutoDetect(fieldVisibility = JsonAutoDetect.Visibility.NONE, getterVisibility = JsonAudtoDetect.Visibility.NONE), the result will be a JSON without properties. I don't think it's the ideal solution. – Alessandro C Jul 13 '16 at 13:18

score 23 · Answer 3 · answered Nov 21 '11 at 14:26

23

i got the same error, but with no relation to Hibernate. I got scared here from all frightening suggestions, which i guess relevant in case of Hibernate and lazy loading... However, in my case i got the error since in an inner class i had no getters/setters, so the BeanSerializer could not serialize the data...

Adding getters & setters resolved the problem.

answered Nov 21 '11 at 14:26

OhadR

8,276
3
47
53

1

This is really helped me ! – Badal Nov 06 '13 at 07:08
2

How might I do the opposite? ie. I don't want to add a getter/setter but I want Jackson to skip that property. – Daniel Patrick Jul 26 '16 at 23:38

score 9 · Answer 4 · answered Dec 07 '10 at 17:06

For what it's worth, there is Jackson Hibernate module project that just started, and which should solve this problem and hopefully others as well. Project is related to Jackson project, although not part of core source. This is mostly to allow simpler release process; it will require Jackson 1.7 as that's when Module API is being introduced.

score 6 · Answer 5 · answered Oct 17 '16 at 15:24

Similar to other answers, the problem for me was declaring a many-to-one column to do lazy fetching. Switching to eager fetching fixed the problem. Before:

@ManyToOne(targetEntity = StatusCode.class, fetch = FetchType.LAZY)

After:

@ManyToOne(targetEntity = StatusCode.class, fetch = FetchType.EAGER)

score 6 · Answer 6 · edited Oct 26 '12 at 11:58

6

I had the same problem. See if you are using hibernatesession.load(). If so, try converting to hibernatesession.get(). This solved my problem.

edited Oct 26 '12 at 11:58

Em1

1,077
18
38

answered Mar 29 '12 at 16:45

Jaishankararam

301
3
2

This is exactly what was wrong with my code. Thanks. – motiver Sep 03 '16 at 05:28

score 5 · Answer 7 · answered Apr 25 '14 at 06:27

5

I had the same error message from spring's @RestController. My rest controller class was using spring's JpaRepository class and by replacing repository.getOne(id) method call with repository.findOne(id) problem was gone.

answered Apr 25 '14 at 06:27

Remis B

365
3
11

@Sllouyssgortyou can check my answer for Spring Boot solution. http://stackoverflow.com/a/36704716/1577363 – erhun Apr 18 '16 at 21:37

score 4 · Answer 8 · answered Feb 10 '14 at 02:26

4

You can use jackson-datatype-hibernate module to solve this problem. It work for me. reference: https://github.com/FasterXML/jackson-datatype-hibernate

answered Feb 10 '14 at 02:26

Howard

41
3

score 3 · Answer 9 · answered Jul 20 '12 at 08:50

3

You could use @JsonIgnoreProperties(value = { "handler", "hibernateLazyInitializer" }) annotation on your class "Director"

answered Jul 20 '12 at 08:50

atovstonog

149
2
2
8

score 3 · Answer 10 · edited May 23 '17 at 12:03

3

I got the same issue, salutations are here

Avoid Jackson serialization on non fetched lazy objects

http://blog.pastelstudios.com/2012/03/12/spring-3-1-hibernate-4-jackson-module-hibernate/

https://github.com/nessonqk/jackson-datatype-hibernate

edited May 23 '17 at 12:03

Community

1
1

answered May 01 '14 at 14:15

Saorikido

2,173
2
26
37

score 2 · Answer 11 · answered May 24 '17 at 07:15

You can add a Jackson mixin on Object.class to always ignore hibernate-related properties. If you are using Spring Boot put this in your Application class:

@Bean
public Jackson2ObjectMapperBuilder jacksonBuilder() {
    Jackson2ObjectMapperBuilder b = new Jackson2ObjectMapperBuilder();
    b.mixIn(Object.class, IgnoreHibernatePropertiesInJackson.class);
    return b;
}


@JsonIgnoreProperties({"hibernateLazyInitializer", "handler"})
private abstract class IgnoreHibernatePropertiesInJackson{ }

score 0 · Answer 12 · answered Jun 08 '12 at 09:52

I am New to Jackson API, when i got the "org.codehaus.jackson.map.JsonMappingException: No serializer found for class com.company.project.yourclass" , I added the getter and setter to com.company.project.yourclass, that helped me to use the ObjectMapper's mapper object to write the java object into a flat file.

score 0 · Answer 13 · answered Nov 06 '13 at 07:14

0

I faced the same issue and It is really strange that the same code works in few case whereas it failed in some random cases.

I got it fixed by just making sure the proper setter/getter (Making sure the case sensitivity)

answered Nov 06 '13 at 07:14

Badal

4,078
4
28
28

score 0 · Answer 14 · answered Mar 12 '15 at 20:36

I tried @JsonDetect and

@JsonIgnoreProperties(value = { "handler", "hibernateLazyInitializer" })

Neither of them worked for me. Using a third-party module seemed like a lot of work to me. So I just tried making a get call on any property of the lazy object before passing to jackson for serlization. The working code snippet looked something like this :

@RequestMapping(value = "/authenticate", produces = "application/json; charset=utf-8")
    @ResponseBody
    @Transactional
    public Account authenticate(Principal principal) {
        UsernamePasswordAuthenticationToken usernamePasswordAuthenticationToken = (UsernamePasswordAuthenticationToken) principal;
        LoggedInUserDetails loggedInUserDetails = (LoggedInUserDetails) usernamePasswordAuthenticationToken.getPrincipal();
        User user = userRepository.findOne(loggedInUserDetails.getUserId());
        Account account = user.getAccount();
        account.getFullName();      //Since, account is lazy giving it directly to jackson for serlization didn't worked & hence, this quick-fix.
        return account;
    }

score 0 · Answer 15 · answered Sep 15 '16 at 21:16

0

Also you can make your domain object Director final. It is not perfect solution but it prevent creating proxy-subclass of you domain class.

answered Sep 15 '16 at 21:16

DzianisH

77
2

Strange Jackson exception being thrown when serializing Hibernate object

15 Answers15

Linked

Related