Tatu Saloranta

@marcusvoltolim Looking forward to your solution (no snark intended)!

@JacksonJang Something you might be interested in trying to implement?

We can start with that, and see how PR forms. Easy enough to change name if necessary. Good thinking wrt backwards-compatibility!

UGGGH. This is my bad -- _I_ should have read this with more thought. I misunderstood what was being asked. Request was also for an annotation attribute, which would be...

Ok, please see my notes on #4442: I am not sure these are safe to remove. Problem I fear is that `JsonSerializer` instances are added to `Map` before dependency resolution...

@pjfanning But synchronization does have wider scope so it is NOT just guarding reads. That's what I realized reading through the code: `synchronized` locks the whole `SerializerCache` instance which then...

> _sharedMap is created in the constructor and is final. This coding approach makes it fully safe to read without locking. The JVM basically guarantees that the constructor must complete...

And one additional note: 2.15.2 is not the latest version, so you'd really want to try out with either latest release (2.17.2) or pre-release (2.18.0-rc1). There may be later fixes...

@fc76gsk Are you seriously not going to include any useful information here?!?! What the #%(%^ is "failed to serialize payload error"? Stack trace is absolutely needed, even if no reproduction...

While vague, it sounds more like something in JDK is having rare issues with Reflection-based `Field` accessors. If so, it'd unfortunately also be outside of anything Jackson has control over....