camel-avro in Fabric8 containers does not re-initialize correctly after profile-refresh

An application uses camel-avro to deserialize objects in Apache Avro format. The application is an OSGi bundle, specified along with all its dependencies in a Fabric8 profile.

When the application is modified by the developers, it is pushed to a repository, followed by profile-update to bring the changes into the fabric container. Although all the necessary bundles appear to refresh, in fact Avro is left in a peculiar state. and API calls that ought to return data return nulls. To recover, it is necessary explicitly to refresh the avro and avro-ipc bundles, along with the application bundle.

It seems that a profile-update leaves the Avro runtime in a peculiar state.