Red Hat Summitこのコンテンツは選択した言語では利用できません。
Chapter 2. Known Issues
This section lists known issues in version 6.1.1 of the JBoss A-MQ cartridge.
For general known issues in version 6.1.0 of JBoss A-MQ, see the Known Issues section of the Red Hat JBoss A-MQ 6.1 Release Notes.
- Restoring JBoss A-MQ applications from a snapshot is not supported
- If you create a snapshot of multiple JBoss A-MQ applications with the snapshot-save command, you cannot restore the snapshots with the snapshot-restore command.
- You must delete containers with the same tool that you used to create the containers
- For example, if you create a container from the Fuse Management Console and then delete the container from the OpenShift Enterprise command line utility, the utility might not completely remove the container from the fabric. The deleted container then might re-register to the fabric with incomplete information and generate run-time errors or failures.
- You cannot move the primary JBoss A-MQ application between nodes
- To move a JBoss A-MQ application from one OpenShift Enterprise node to another node, you can use the oo-admin-move command. However, you cannot move the first application that you created between nodes. You can use the command to move only subsequent applications that you create.
- The PortMapper tool does not translate TLS ports
- When you define connection URLs in CXF endpoints, you cannot specify SNI ports that use the TLS protocol, such as
APP_TLS_PORT_1. Instead, you must specify one of the non-TLS ports, such asAPP_PORT_1, when you configure the CXF endpoint. - When the the JBoss A-MQ application reconnects to the fabric server, the Karaf log throws an exception
- When the connection between the JBoss A-MQ application and the fabric server is suspended and then resumed, the following error message might appear in the Karaf log:
java.util.concurrent.RejectedExecutionException Task java.util.concurrent.FutureTask@27458911 rejected from java.util.concurrent.ThreadPoolExecutor@4629cf3b [Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 9] ...
java.util.concurrent.RejectedExecutionException Task java.util.concurrent.FutureTask@27458911 rejected from java.util.concurrent.ThreadPoolExecutor@4629cf3b [Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 9] ...Copy to Clipboard Copied! Toggle word wrap Toggle overflow This message reports a problem with an obsolete CuratofFramework listener.Workaround: Ignore the message. - The Fuse Builder cartridge does not support HTTPS connections
- To connect to the Maven repository of the Fuse Builder cartridge, you must use an HTTP connection.
- You cannot use the publicip resolver when you create a JBoss A-MQ application
- The
publicipresolver connects the application to the Git repository of the OpenShift Enterprise node. However, the resolver might not translate the public IP address of the node correctly and redirect the connection to an HTML page. - Some OpenShift Enterprise processes might stop before the JBoss A-MQ application is created
- In some environments, you cannot create the JBoss A-MQ application because some OpenShift Enterprise components, such as
mcollectiveandrhc, reach the maximum timeout limit and stop before the application is created.For general information about the default timeout values of OpenShift Enterprise components, see the Component Timeout Value Location section of the OpenShift Enterprise Administrator Guide.Workaround: Increase the timeout values of the OpenShift components. For a detailed description of this workaround, see the following knowledge base article: https://access.redhat.com/solutions/1238583 - The JBoss A-MQ cartridge creates a JBoss Fuse application by default
- When you install the JBoss A-MQ and create an application, the default type is JBoss Fuse. If you do not have the JBoss Fuse cartridge installed, the creation process fails.Workaround: In the fabric server, open the
openshift.profile/io.fabric8.openshift.propertiesfile and change the value of thedefault.cartridge.urlproperty in the following format:default.cartridge.url=id:amq-<version_number>
default.cartridge.url=id:amq-<version_number>Copy to Clipboard Copied! Toggle word wrap Toggle overflow For example, to set the default cartridge to JBoss A-MQ version 6.1.1, specify the following value:default.cartridge.url=id:amq-6.1.1
default.cartridge.url=id:amq-6.1.1Copy to Clipboard Copied! Toggle word wrap Toggle overflow
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}