Problem with JBoss Fuse patching procedure

Solution In Progress - Updated -

Issue

We still experience a problem with JBoss Fuse patching procedure.

We analyzed the internal state of OSGI bundles after the official patching procedure. Unfortunately, the problem is more than just a minor issue with a wrong "osgi:list -l" output. This command works properly; it is more a corrupted internal state of OSGI-Bundles that a minor display issue.

Let me illustrate the severity of this inconsistency on one example. Having patch R1 applied as described in ENTESB-2387, let’s refresh one bundle:

JBossFuse:karaf@root> osgi:list | grep camel-core
[ 142] [Active     ] [            ] [       ] [   50] camel-core (2.12.0.redhat-610394)

JBossFuse:karaf@root> osgi:update 142

JBossFuse:karaf@root> osgi:list | grep camel-core
[ 142] [Active     ] [            ] [       ] [   50] camel-core (2.12.0.redhat-610379)

What just happened is the bundle became “unpatched” again. This is 100% reproducible.

The question is, how to workaround the patching problem?

Environment

  • JBoss Fuse 6.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.