TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ 8.5.1 Hotfix 08 is now available
book
Article ID: KB0101727
calendar_today
Updated On:
Products
Versions
TIBCO ActiveMatrix BusinessWorks Plug-in for IBM MQ
8.5.1
Description
TIBCO ActiveMatrix BusinessWorks™ Plug-in for WebSphere MQ 8.5.1 Hotfix 8 is released for all platforms. Please refer to the product readme file for details regarding the supported platforms. Listed below is a summary of updates included in this Hotfix. Please refer to the Hotfix Readme for additional details and installation instructions.
====================================================================== Closed Issues in 8.5.1_HF-008
BWMQ-891 Support passwords with more than 12 chars. As of this hotfix if the password is longer than 12 chars it will be sent via an MQCSP header. This is only supported on servers and clients above 8.0
BWMQ-889 Listener hangs if there is significant delay between the commit and end of process. A synchronization defect in the listener causes it to run a second process before the previous one has been committed causeing a deadlock at the commit point.
Closed Issues in 8.5.1_HF-007
BWMQ-865 Activities leak memory while checking for a zOS server because the PCFAgent for client version 9.x does not cleanup on disconnect. This results in a consumption of memory proportional to the number of activities executed and the number of listener polling calls made.
Closed Issues in 8.5.1_hotfix06
BWMQ-839 Put/Get version of request reply pattern fails if the dynamic reply queue is not sharable. This was introduced in hotfix 5 when optimizing the RequestReply activity and has been reverted in hotfix 6.
BWMQ-836 Repackaged hotfix 5 as a full installer with attendant BWCE runtime archive. The only functional difference from HF5 is that the test button for MQ server version 9.1 will work.
Closed Issues in 8.5.1_hotfix05
BWMQ-827 Use of PCFAgents sometimes leave dynamic temporary queues allocated on the server.
BWMQ-826 RequestReply activity with dynamic reply queue getting an NPE on the response queue.
BWMQ-824 RequestReply activity fails when used in a loop.
BWMQ-818 Sometimes the get or listen activities will get an error when running on zOS after changing the get options due to non-indexed queues.
BWMQ-816 Delay the startup of listeners so that queue managers can allocate multiple conversations per physical connection. To effect the behavior add this java property to the tra: com.tibco.bw.palette.mq.runtime.MqReceiver=5 which will delay connections 2-n by 5 seconds so that all connections can participate in the shared conversation.
BWMQ-815 Test button and runtime not working on server version 9.1. The queue manager inquire method crashes the server connection channel on MQ server version 9.1. This results in the test button and the runtime not being able to connect to the queue manager. Note that this hotfix addresses only the runtime issue. The test button will not work on server 9.1 but queue choosers and the runtime will work.
BWMQ-811 If Listener/Subscriber server connection is terminated forcibly the listener will report errors too fast for the engine to handle, resulting in excessive resource consumption and eventually out of memory conditions.
BWMQ-807 Topic Subscriber does not work on zOS queue manager versions 9.x
BWMQ-793 Disable Listener/Subscriber error events when the server or server connection channel is unavailable or while switching to fault tolerant partner. To effect this behavior set the following parameter in the application.tra: com.tibco.bw.palette.mq.runtime.DisableEventsourceFaultEvents=true
Closed Issues in 8.5.1_hotfix04
BWMQ-798 Connections are not released after app is stopped. Connections are now closed correctly if the application is stopped while the listener was blocked on an MQ get call.
Closed Issues in 8.5.1_hotfix03
BWMQ-789 Customer has messages with embedded nulls that they want "sanitized" via the same mechanism used in BWMQ-711 Modified the plugin to replace embedded nulls with '.' chars when the special jvm parms from BWMQ-711 are set to true. Also ensured that embedded nulls dot truncate messages regardless of the sanitization parms.
Closed Issues in 8.5.1_hotfix01
BWMQ-696 Listener Fails to reconnect with exceptions when connection lost.
BWMQ-711 Incoming corrupt message cannot be mapped by engine Important usage notes: Two system environment parameters are now observed by the plugin: com.tibco.bw.palette.mq.runtime.sanitizeMqmdHeaderFields=true com.tibco.bw.palette.mq.runtime.sanitizeMessageText=true Set them to have invalid XML characters in either the MQMD header fields or the message body replaced with the '.' character.
This hotfix can be downloaded from TIBCO Support Customer Portal Web UI(https://support.tibco.com). You will need to provide your TIBCO Support Portal credentials. Once logged in you can download the hotfix by selecting the “Downloads” -> “Hotfixes” option under: