Chapter 2. Known Issues
The following list describes known issues in version 6.1:
- LDAP JAAS login module causes authentication problems for Fabric [FABRIC-1154]
- Configuration of LDAP authentication in the context of Fabric does not work as described in section "Enable LDAP Authentication in the OSGi Container" in "Security Guide". When you configure the LDAP login module as described, authentication fails always. To work around this problem, configure JAAS as follows:
<?xml version="1.0" encoding="UTF-8"?> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0" xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0" xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0"> <jaas:config name="karaf" rank="2"> <jaas:module className="io.fabric8.jaas.ZookeeperLoginModule" flags="sufficient"> </jaas:module> <jaas:module className="org.apache.karaf.jaas.modules.ldap.LDAPLoginModule" flags="sufficient"> initialContextFactory=com.sun.jndi.ldap.LdapCtxFactory connection.username=uid=admin,ou=system connection.password=secret connection.protocol= connection.url=ldap://localhost:10389 user.base.dn=ou=users,ou=system user.filter=(uid=%u) user.search.subtree=true role.base.dn=ou=roles,ou=system role.name.attribute=cn role.filter=(member=uid=%u) role.search.subtree=true authentication=simple </jaas:module> </jaas:config> </blueprint>Where theZookeeperLoginModuleis added to the chain of login modules and both theZookeeperLoginModuleand theLDAPLoginModuleare configured withflags=sufficient. TheZookeeperLoginModulemust be present, in order to parse the credentials token. It is not necessary to populate the Zookeeper authentication system with user data. - To secure JBoss A-MQ against the POODLE SSLv3 vulnerability, you must disable SSLv3 in some JBoss A-MQ components
- The POODLE SSLv3 vulnerability can cause JBoss A-MQ components that use SSL authentication, such as the embedded ActiveMQ broker and the LDAP authentication module, to be exposed to man-in-the-middle attacks.Workaround: Manually disable SSLv3 in any deployed components that use SSL authentication. For details on how to disable SSLv3, see the Disabling SSLv3 in JBoss Fuse 6.x and JBoss A-MQ 6.x knowledge base article on the Red Hat Customer Portal. For general information about the POODLE SSLv3 vulnerability, see the POODLE: SSLv3 vulnerability (CVE-2014-3566) knowledge base article on the Red Hat Customer Portal.
- The help command in the generic Apache Karaf shell causes an exception
- By default, you launch the Red Hat JBoss A-MQ console with the fusemq command. However, Red Hat JBoss A-MQ also includes a generic Apache Karaf shell that you can launch with the shell command. In the generic shell, the help command throws an exception. It is not recommend to use the generic Apache Karaf shell.
- The ls command might cause an exception
- The ls console command that you can use to inspect OSGi bundles throws an exception when you run it on some bundles.
- Microsoft Visual C++ Runtime is required on Windows 7 64-bit operating systems
- On some 64-bit Windows operating systems you must install Microsoft Visual C++ 2008 Redistributable Package (x64) before you can start Red Hat JBoss A-MQ.
- The jmx.restart feature might behave unexpectedly [ENTMQ-570]
- When you install and use the jmx.restart feature, you might encounter errors.
- Some jClouds feature dependencies must be installed manually [ENTESB-1223]
- When you install the jclouds-rackspace-cloudblockstorage-us feature, you must manually install some bundle dependencies.To install the bundles:
- In the Karaf console, run the command to show the list of feature dependencies in the following format:
features:info -d <feature_name>
- Run the command to show the Maven repository that contains the feature bundles on each of the dependencies in the following format:
features:info -b <feature_name>
- Run the command to install each bundle directly from the Maven repository in the following format:
osgi:install <Mave_repository_URL>
After you install all of the bundle dependencies, you can install the feature with the features:install command in the same way you normally install features. - Cannot connect to SSH containers on Windows operating systems with JDK 7 [ENTESB-1211]
- The following error message might appear:
c:\proj\jboss-fuse-6.1.0.redhat-<build_number>>bin\client.bat org.apache.sshd.common.RuntimeSshException: Failed to get the session. at org.apache.sshd.client.future.DefaultConnectFuture.getSession(DefaultConnectFuture.java:43) at org.apache.karaf.client.Main.main(Main.java:134) Caused by: java.io.IOException: The format of the specified network name is invalid. at sun.nio.ch.Iocp.translateErrorToIOException(Iocp.java:309) at sun.nio.ch.Iocp.access$700(Iocp.java:46) at sun.nio.ch.Iocp$EventHandlerTask.run(Io
Workaround: Run the command to manually specify the host name in the following format:bin\client.bat -h <IP_address>
- Cannot run jClouds 1.6.3 and 1.7.0 on Oracle databases with OpenJDK 1.7.0 build 51 [JCLOUDS-427]
- Workaround: To continue to use jClouds 1.6.3 or 1.7.0, you can use OpenJDK 1.7.0 build 45 or earlier. To use OpenJDK 1.7.0 build 51, tou can use a jClouds snapshot of version 1.7.1 or 1.8.0.To check whether your jClouds version is compatible with your OpenJDK version, run the command to search for the TypeToken2 class in the jclourse-core-<version>.jar file in the following format:
$ jar -tvf jclouds-core-<version>.jar org/jclouds/util/TypeToken2.class
- Cannot create a fabric on a Windows 7 operating system with Java 7 [FABRIC-963]
- 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
- Cannot apply patches with alphabetic characters [ENTESB-1352]
- You can specify only numeric characters and periods (
.) in profile patch versions. For example, you cannot apply a patch with the version1.2-amq. - You cannot access the management console when you run Red Hat JBoss A-MQ
- When you start the Karaf console in JBoss A-MQ and log in to the management console from the browser, the logging console shows the following error message:
java.lang.NoSuchMethodError: org.apache.commons.codec.binary.Base64.decodeBase64(Ljava/lang/String;)[B
Workaround: Delete thepax-url-aether-1.5.2.jarfile from the lib/ folder. - KAR files not supported in a Fabric environment
- Apache Karaf archive (KAR) files are not supported in a Fabric environment and cannot be deployed to a Fabric container. It is possible, however, to deploy KAR files to a non-Fabric container.
- [ENTESB-3488] Fuse Fabric mq-create requires keytool to be installed
- The
fabric:mq-createcommand requires that the Javakeytoolcommand-line utility is provided on your PATH. If necessary, you can work around this requirement by specifying the--no-ssloption (which disables support for the SSL/TLS protocol). - [ENTMQ-686] Fabric Discovery protocol is not backward compatible for mq clients
- JBoss A-MQ 6.0 clients that use a Fabric discovery broker URL—for example, a URL of the form
discovery:fabric:clusterID—cannot connect to JBoss A-MQ 6.1 brokers deployed in a Fabric. There are two alternative workarounds for this issue:- Upgrade the 6.0 clients to user version 6.1, or
- Interpose an MQ Gateway (from JBoss A-MQ 6.1) between the clients and the brokers, and configure the clients to connect to the brokers through the MQ Gateway.
