Skip to content
This repository has been archived by the owner on Nov 5, 2019. It is now read-only.

Log-warning "Disabling Afterburner deserialization for type" using wrong logger-name #46

Closed
mbknor opened this issue Nov 12, 2014 · 1 comment
Milestone

Comments

@mbknor
Copy link
Member

mbknor commented Nov 12, 2014

When the afterburner-module is disabled with the error-message below, it logs it as WARN, with a dynamic logger-name.

This dynamic logger-name makes it impossible to configure logback/log4j to not log it.

If the logger-name was prefixed with "com.fasterxml.jackson.module.afterburner", we could configure to ignore it.

I do not know why this specific class results in this error in the first place, but I think it has something to do with IpInfoExtended extending IpInfo.

Logged WARN message:
"Disabling Afterburner deserialization for type class com.company.IpInfo, field #0, due to access error (type java.lang.IllegalAccessError, message=tried to access field com.company.IpInfo.ipAddress from class com.company.IpInfoExtended$Access4JacksonDeserializer)"

Used logging-Logger=com.company.IpInfoExtended$Access4JacksonDeserializer

@cowtowncoder
Copy link
Member

Agreed, sounds like we should prefix logger name to allow changing of logging details.

As to failure itself, it would be good to get a reproducible use case: Afterburner should be able to detect cases where it can not use accessors and thereby avoid exception.
Also make sure to test with latest version (2.4.3) if not doing that already.

@cowtowncoder cowtowncoder added this to the 2.6.0-rc4 milestone Jul 11, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants