Incorrect property resolver causes Fabric completely unusable
Environment
- JBoss Fuse 6.1
Issue
If I create a profile with a property that uses incorrect property resolver, for instance ${file:inputFile}, once I try to apply this profile to a newly created child container, it will cause the command line console completely unusable.
Before applying the faulty profile to the "child" container:
JBossFuse:karaf@root> container-list
[id] [version] [connected] [profiles] [provision status]
root* 1.0 true fabric, fabric-ensemble-0000-1, jboss-fuse-full success
child 1.0 true default success
After applying the profile to the "child" container:
JBossFuse:karaf@root> container-list
[id] [version] [connected] [profiles] [provision status]
root* 1.0 true fabric, fabric-ensemble-0000-1, jboss-fuse-full success
Error executing command: Missing Placeholder Resolvers: file
From hawtio, I can still browse the root container, but any operation on the "child" container will just hang.
It is not only limited to unsupported property resolver. If I use a supported property resolver but the property placeholder does not exist, for instance, ${container:test}, it will have the same effect as the unsupported property resolver ${file:xxx}. But I will get a slightly different error:
JBossFuse:karaf@root> container-list
[id] [version] [connected] [profiles] [provision status]
root* 1.0 true fabric, fabric-ensemble-0000-1, jboss-fuse-full success
Error executing command: java.lang.NullPointerException
Resolution
Upgrade to JBoss Fuse 6.2 when it becomes available.
Root Cause
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.