The JRE is updated to 8.0.6.25 in this release. LIMITATIONS AND KNOWN PROBLEMS FOR IBM MQ 9.2.2 Changes to default values for some ciphers You can add this information by using the IBM MQ Operator and an ini configmap. To configure TLS 1.2 for replication traffic, add the following setting to the NativeHALocalInstance stanza of qm.ini in each queue manager instance: CipherSpec=ANY_TLS12 Until a fix is available, use a plain text or TLS 1.2 connection for replication. [CommentInsert1(), CommentInsert2(),ĬommentInsert3(rrcE_SSL_BAD_RETURN_FROM_GSKIT (14) (?) (gsk_secure_soc_read) When you run with TLS 1.3, after a failover you might get pairs of messages similar to the following pair: T12:06:14.148Z AMQ3214I: Native HA inbound secure connection accepted fromĬommentInsert3(TLS_CHACHA20_POLY1305_SHA256)] T12:06:14.613Z AMQ3222E: Native HA network connection from '' ended Native HA with replication over TLS 1.3: After a failover, replicas might repeatedly connect and disconnect from the active instance Unresolved requirement: Import-Package: .ajax version="[9.4.40,10.0.0)" Unresolved requirement: Import-Package: version="[9.4.40,10.0.0)" resolution:="optional" > Export-Package: bundle-symbolic-name="" bundle-version="9.4.40.v20210413" version="9.4.40" uses:="rvlet.pathmap.handler.handler.gzip.session.annotation.component.resource" The following error is being addressed by APAR IT37166: !ENTRY .jetty 4 0 17:18:34.417 Unresolved requirement: Import-Package: .ajax version="[9.4.35,10.0.0)"Īt .Module.start(Module.java:462)Īt .ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1844)Īt .framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)Īt .ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1837)Īt .ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1778)Īt .ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1742)Īt .ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1664)Īt .ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)Īt .(EventManager.java:234)Īt .eventmgr.EventManager$n(EventManager.java:345) Unresolved requirement: Import-Package: version="[9.4.35,10.0.0)" resolution:="optional" > Export-Package: bundle-symbolic-name="" bundle-version="9.4.35.v20201120" version="9.4.35" uses:="rvlet.pathmap.handler.handler.gzip.session.annotation.component.resource" Unresolved requirement: Import-Package: version="[9.4.0,10.0.0)"
The following error is being addressed by APAR IT36319: !ENTRY .jetty 4 0 15:01:50.304 The log file is here: \IBM\WebSphereMQ\workspace-\.metadata\.log In both cases, the error message can be ignored. Error messages in the IBM MQ Explorer log after IBM MQ 9.2.3 is installed on WindowsĪfter IBM MQ 9.2.3 is installed on Windows, you might see one of the following error messages in the IBM MQ Explorer log file the first time the IBM MQ Explorer is started. You must apply the fix before you start a migrated queue manager for the first time. This issue is fixed by APAR IT34332, which is included in IBM MQ 9.2.3. LIMITATIONS AND KNOWN PROBLEMS FOR IBM MQ 9.2.3 Channel names are blank in MQSC and IBM MQ Explorer after direct migration from IBM MQ 8.0.0.1, 8.0.0.2, or 8.0.0.3įor more information, see LIMITATIONS AND KNOWN PROBLEMS FOR THE INITIAL IBM MQ 9.2.0 RELEASE. In a future release, the QPST_MSGP020_PUTTIME parameter will move to an internal control block.
However QPST_MSGP020_PUTTIME is an internal parameter, and QPST is an externalized control block. LIMITATIONS AND KNOWN PROBLEMS FOR IBM MQ 9.2.4 On z/OS, QPST_MSGP020_PUTTIME is added to the QPST control blockĪs part of the z/OS System Management Facility (SMF) enhancements for IBM MQ 9.2.4, the QPST_MSGP020_PUTTIME parameter is added to the QPST control block. Installation instructions are available as part of the IBM MQ 9.2 product information published in IBM Documentation: Limitations and known problems for Continuous Delivery releases IBM MQ for Multiplatforms, on Cloud, and Appliance, 9.2 IBM MQ for Multiplatforms, on Cloud, and Appliance, 9.2.1 IBM MQ for z/OS Statement of Direction, 9.2.2 IBM MQ for Multiplatforms, on Cloud, and Appliance, 9.2.2 IBM MQ for Multiplatforms, MQ on Cloud, and Appliance firmware, 9.2.3 IBM MQ for Multiplatforms, MQ on Cloud, and Appliance firmware, 9.2.4