SupportConsoleDevelopersStart a trialContact

Chapter 3. Known Issues

3.1. List of Known Issues in JBoss A-MQ 6.2.1

The following list describes known issues in version 6.2.1:
[ENTMQ-1484] Implementation of AMQ-6077 in Fuse 6.2.1 is incomplete
The implementation of the new security features for JMS ObjectMessage serialization is incomplete in JBoss A-MQ 6.2.1. The use of the org.apache.activemq.SERIALIZABLE_PACKAGES JVM property has been implemented, but the setTrustedPackages() method, and so on, have not.
[ENTESB-4506] Unable to apply patch to JBoss AM-Q 6.2.0 SSH-containers
Applying the 6.2.1.redhat-084 JBoss A-MQ rollup patch to an existing JBoss A-MQ 6.2.0 Fabric instance using the new patching mechanism does not work out of the box, due to a missing fabric8-karaf distribution file. Please contact support for help, if you need to upgrade a JBoss A-MQ Fabric instance from version 6.2.0 to version 6.2.1.
[ENTESB-4497] Changes in org.ops4j.pax.logging.cfg do not propagate to newer version
After upgrading JBoss A-MQ 6.2.0 to version 6.2.1 using the new patching mechanism, it is likely that you will lose any custom configuration changes to the org.ops4j.pax.logging.cfg file. After upgrading the container, edit the etc/org.ops4j.pax.logging.cfg file to re-apply your custom logging configuration.
[ENTESB-4408] Patching functionality in Fuse Management Console (Hawtio) temporarily disabled
The patching functionality in the Fuse Management Console (Hawtio) has been temporarily disabled for this release. This is because the Hawtio UI has not been updated to use the new patching mechanism. To install Fabric patches, use the Karaf console instead. This issue will be fixed in a future release.
[ENTMQ-1323] Must not enable restartAllowed option on the Apache ActiveMQ broker
In the context of a master/slave configuration of an Apache ActiveMQ broker cluster, you must not enable the restartAllowed option (for example, by setting restartAllowed=true). When this option is enabled, it can cause a broker restart to fail.
[ENTESB-4105] Demos from the Apache ActiveMQ distribution in the extras subdirectory are not supported
The extras/ directory of your JBoss A-MQ installation contains the following distributions of Apache components:
  • apache-activemq-5.11.0.redhat-621084.zip
Included in this archives are numerous examples, which have been taken from the community distribution. These examples are not supported in JBoss A-MQ.
[ENTESB-4248] ./bin/amq script now creates two processes
There is a change in behaviour of the ./bin/amq script since version 6.2.1. This script now creates two processes (where previously there was just one process). There is now a parent process ./bin/karaf, which executes the Karaf console; and a child process, which executes the Karaf server in a JVM.
[ENTESB-3938] JBoss A-MQ 6.2.1 takes a long time to start up on OpenStack
When a JBoss A-MQ 6.2.1 container is deployed on RHEL Openstack Platform, it can take a long time (several minutes) for the container to start up. A workaround is to add the following option to the JVM that starts the container (for example, by setting the JAVA_OPTS environment variable): 
-Djava.security.egd=file:/dev/./urandom
The extra dot in the pathname, as in /./, is required.
Note
The effect of the workaround is to replace the default /dev/random by /dev/urandom. The alternative is faster, but less random than /dev/random. This has an impact on any security packages that depend on this device to generate entropy and random numbers.
[FABRIC-963] Cannot create a fabric on a Windows 7 operating system with Java 7
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
[ENTESB-3192] Client session is dropped after fabric:create
The Client session is dropped after fabric:create is run. The workaround is to reconnect to the karaf console after fabric is created.
[ENTESB-3039] [HTTP Gateway] apis mapping rules don't work right after deployment
If the zooKeeperPath property in the io.fabric8.gateway.http.mapping-apis.properties is changed, a gateway node restart will be required.
[ENTESB-2924] Insight - Elasticsearch: JsonPretty error: Unable to get property 'toLowerCase' of undefined or null reference (:7999:6)
Insight Elasticsearch page is not supported in IE. The error occurs when clicking rectangles with numbers at Insight - Elasticsearch page.
[ENTESB-2770] [OSE][6.2]AMQ6.2 and AMQ6.1 should allow to be installed together in OSE
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.
[ENTESB-2513] OSE Fuse JVM sometimes dies with SIGABRT
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.
[ENTMQ-1040] Stop script ignores arguments
When shutting down a broker using the stop script, the stop script fails to work remotely.
[ENTESB-2069] Container which is created from Hawtio can not start if restarting openshift node
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 until we get connected to ZooKeeper.
[ENTESB-3200] fuse startup warning on java 8 - PermSize and MaxPermSize support was removed
During JBoss A-MQ 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).
[FABRIC-963] Cannot create a fabric on a Windows 7 operating system with Java 7
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
[ENTESB-3192] Client session is dropped after fabric:create
The Client session is dropped after fabric:create is run. The workaround is to reconnect to the karaf console after fabric is created.
[ENTESB-3039] [HTTP Gateway] apis mapping rules don't work right after deployment
If the zooKeeperPath property in the io.fabric8.gateway.http.mapping-apis.properties is changed, a gateway node restart will be required.
[ENTESB-2924] Insight - Elasticsearch: JsonPretty error: Unable to get property 'toLowerCase' of undefined or null reference (:7999:6)
Insight Elasticsearch page is not supported in IE. The error occurs when clicking rectangles with numbers at Insight - Elasticsearch page.
[ENTESB-2773] [platform AIX HPUX] camel-leveldb missing native library
The camel-leveldb feature is not supported on IBM AIX, HP-UX, and Oracle Solaris operating systems.
[ENTESB-2770] [OSE][6.2]AMQ6.2 and AMQ6.1 should allow to be installed together in OSE
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.
[ENTESB-2513] OSE Fuse JVM sometimes dies with SIGABRT
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.
[ENTMQ-1040] Stop script ignores arguments
When shutting down a broker using the stop script, the stop script fails to work remotely.
[ENTESB-2069] Container which is created from Hawtio can not start if restarting openshift node
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.
[ENTMQ-1068] Exclude C# from Windows Qpid packages
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# example code. Please note that we do not support the Qpid C# client, and so these examples are not supported.
[ENTESB-3488] Fuse Fabric mq-create requires keytool to be installed
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).
[Bug 1275786] Missing nss-devel dependency on Client and ComputeNode variants
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.
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.