Chapter 4. Known Issues

To connect to the ZooKeeper server, you must change the connectivity type from IPv6 to IPv4. For the detailed solution, see the following Customer Portal article: Cannot create fabric in JBoss Fuse 6.1 Beta on Windows 7

When you send a message or draft, the response contains a Message object with an ID. It may not be possible to immediately get this message via another call to the API. You may have to wait and retry the call.

Importing a message may throw a java.net.SocketTimeoutException if the send operation was called before. Workaround: After a send call wait for few moments before calling import.

Response of permission insert operation sometimes does not return emailAddress property even if the value of request property type was set to user. Nevertheless the permission is successfully inserted.

Google Drive API JSON reponse for changes returns bad count of items for the first page. Setting maxResults for a list operation may not return all the results in the first page. You may have to go through several pages to get the complete list (that is by setting pageToken on new requests).

Configuring for a specific version of TLS is possible from Red Hat JBoss Fuse 6.1 rollup 2 onwards. Earlier versions of JBoss Fuse do not allow to explicitly configure a specific TLS/SSL version to be used by the CXF server. For the detailed solution, see the following Customer Portal article: https://access.redhat.com/solutions/1314403

The Client session is dropped after fabric:create is run. The workaround is to reconnect to the karaf console after fabric is created.

If the zooKeeperPath property in the io.fabric8.gateway.http.mapping-apis.properties is changed, a gateway node restart will be required.

camel-avro, camel-hbase, camel-hdfs2 are not supported on Solaris / AIX. The camel-hdfs2 feature can only run if you have libsnappyjava.dylib in java.library.path. You must manually setup libsnappyjava.dylib in Red Hat JBoss Fuse before installing these features.

JBossFuse:karaf@root> features:info camel-hdfs2
		Description of camel-hdfs2 2.15.0.redhat-620133 feature

Insight Elasticsearch page is not supported in IE. The error occurs when clicking rectangles with numbers at Insight - Elasticsearch page.

The camel-leveldb feature is not supported on IBM AIX, HP-UX, and Oracle Solaris operating systems.

It is not possible to update both Red Hat JBoss Fuse 6.1 on OSE and Red Hat JBoss Fuse 6.2 on OSE on the same node. Once you update to Red Hat JBoss Fuse 6.2 using rpm -U or yum you will no longer be able to receive updates (patches) for Red Hat JBoss Fuse 6.1 on OSE.

RHEL customers need to upgrade openjdk to java-1.7.0-openjdk-1.7.0.79-2.5.5.3.el6_6 or later which will fix the SIGABRT.

A failed to register plugin exception is thrown after running the command patch:install

When shutting down a broker using the stop script, the stop script fails to work remotely.

After restarting OpenShift, containers created from Hawtio cannot be started. This happens because the containers started before the ZooKeeper starts running will fail to start. The workaround is to wait for the start and keep restarting untill we get connected to ZooKeeper.

The default installation of Red Hat JBoss Fuse 6.2 contains fabric-rest feature which is active by default. This allows to invoke REST-like operations on Fabric (like deleting containers or versions) without any authentication. For 6.2.0, the recommended action is to uninstall this feature after installing Red Hat JBoss Fuse 6.2.

Karaf commands that are not explicitly listed in RBAC access control lists can be invoked in non-interactive shells. To work around the issue, create explicit rules that prevent execution of unwanted commands.

The ssh container provisioning fails to create or publish the artifacts to the fabric maven instance. The workaround is to remove (temporarely) remote Maven servers so that the resolution completes successfully with just the local maven instance.

During JBoss Fuse 6.2 startup on Java 8, the following warnings are printed to the Karaf console:

$FUSE_HOME/bin/fuse
OpenJDK 64-Bit Server VM warning: ignoring option PermSize=128M; support was removed in 8.0
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0
Please wait while JBoss Fuse is loading...
100% [========================================================================]

You can safely ignore these warnings (the PermSize and MaxPermSize JVM options are needed for Java 7, but are ignored in Java 8).

The fabric:join command ignores the --non-managed option when joining a standalone container into an existing fabric. This issue will be fixed in the next release of JBoss Fuse.