[CAMEL-10282] [Avro] Issue on OSGi due to static cache

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.17.3
• Fix Version/s: 2.16.4, 2.17.4, 2.18.0
• Component/s: camel-avro
• Patch Info: Patch Available
• Estimated Complexity: Unknown
• External issue URL: https://issues.jboss.org/browse/ENTESB-6017
• Assignee: Andrea Cosentino
• Reporter: Paolo Antinori
• Created: 01/Sep/16 08:23
• Updated: 01/Sep/16 09:34
• Resolved: 01/Sep/16 08:52

Description

Avro holds a cache of classloaders and other reflection related classes in a static map here:

https://github.com/apache/avro/blob/master/lang/java/avro/src/main/java/org/apache/avro/specific/SpecificData.java#L52-L57

Keys of that map are {{String}}s with classname.

The cache is never updated, and this breaks OSGi ability to update a new class definition, since avro will keep pointing to the old version.

This will lead to a situation where, on an OSGi platform, you are exposed to ClassCastException since the rest of the platform might see a different varsion than the old one cached by avro.

The attached fix is a simple way to entirely bypass this caching behavior with just public subclasses that turn off just the caching behavior.

Issue Links

• links to: GitHub Pull Request #1151