Chapter 3. Known Issues

A file that is required for patching a Fabric from version 6.2.0 to 6.2.1 is missing from the JBoss A-MQ 6.2.0 distribution. The missing file will be provided in the first patch for JBoss A-MQ. For more details, see section "Patching a Fabric from 6.2.0 to 6.2.1" in "Migration Guide".

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

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.

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.

When you download the Red Hat JBoss A-MQ 6.2.0 QPID C++ Client for Windows 64bit Visual Studio 2012 v3.32.3.1 package from the JBoss A-MQ 6.2.0 downloads page, it includes a package called qpid-cpp-x64-VS2012-3.32.3.1.zip, which contains C# libraries (org.apache.qpid.messaging*.dll) and example code. Please note that we do not support the Qpid C# client, and so these libraries and examples are not supported.

The fabric:mq-create command requires that the Java keytool command-line utility is provided on your PATH. If necessary, you can work around this requirement by specifying the --no-ssl option (which disables support for the SSL/TLS protocol).

The Qpid C++ client cannot be compiled from sources through the Client or ComputeNode channels on Red Hat Enterprise Linux (RHEL) 6 (due to a missing dependency on the package, nss-devel). In order to compile from sources, it is recommended that you install the Qpid C++ client through the Server channel instead.

When you install and use the jmx.restart feature, you might encounter errors.

With repeated failover between master and slave, and a message-driven bean that consumes from A and sends to B in a transaction you can: