PK83416: UPDATE WEBSPHERE MQ JMS CLIENT TO FIX PACK 6.0.2.8

Fixes are available

APAR status

Closed as program error.

Error description

Update the WebSphere MQ JMS client shipped with WebSphere
Application Server V6.1 to fix pack 6.0.2.8.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the IBM WebSphere Application      *
*                  Server Version 6.1, using WebSphere MQ as   *
*                  a messaging provider                        *
****************************************************************
* PROBLEM DESCRIPTION: This APAR updates the WebSphere MQ      *
*                      JMS Client shipped with WebSphere       *
*                      Application Server Version 6.1 to       *
*                      WebSphere MQ Fix Pack 6.0.2.8           *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The following WebSphere MQ APARs in WebSphere MQ Fix Pack
6.0.2.5, 6.0.2.6, 6.0.2.7 and 6.0.2.8 may affect use of
WebSphere MQ as a messaging provider for WebSphere Application
Server Version 6.1:

IC54772 Publish subscribe application's WebSphere MQ channel
        and TCP/IP resources are not freed under some
        circumstances
IC56006 Incorrect put time and date is displayed when looking
        at messages on a queue
IC56133 MQRC_API_EXIT_NOT_FOUND reason code not found when
        compiling WebSphere MQ V6 Java applications
IC57782 WebSphere MQ jmsobjectmessage fails to deserialize when
        using WebSphere Application Server
IC57903 WebSphere MQ JMS messages are not backed to the backout
 queue, in case an error occurs during message header
        parsing
IC57918 Delay in delivering large messages to message-driven
 beans when using WebSphere MQ with WebSphere Application
        Server
IZ05857 WebSphere MQ responds with incorrect XA error code in a
        global XA transaction.
IZ19340 Deadlock condition may occur when an application thread
 attempts to close a session used by asynchronous
        message consumer
IZ28844 Memory leak due to build up of jmsqueueconnectionhandle
        or jmstopiconnectionhandle objects when using SSL
IZ30247 The words classname and methodname are hard coded in the
        waslogger class
IZ30565 WebSphere MQ JMS applications get a nullpointerexception
        thrown when calling queuereceiver.close
IZ31348 Jmssession.recover() method does not cause redelivery of
        non-persistent messages in a non-transacted session
IZ32305 WebSphere MQ JMS queuebrowser performance issue when
        using either a jmsmessageid or jmscorrelationid
        selector
IZ35745 WebSphere MQ jmsreplyto defaults to the RFH2 value of
        the reply to queue name instead of the value in the MQMD
IZ36978 Jmsreplyto always contains queue manager name after APAR
        IZ15279HAS been applied
PK64409 After a queue manager restart, MQ JMS connections in
 WebSphere Application Server receive multiple failures
        with MQRC_Q_MGR_NOT_AVAILABLE and J2CA0056I.
PK65622 MDB listeners running is WebSphere Application Server
 fail to process some messages after PTF UK41016 is
        applied.
IC58860 Localaddress parameter in connection factory, qcf and
tcf objects is set to null after copying the object in jndi

IC59701 WebSphere MQ JMS clients fail to parse rfh headers if
the jmstype field of the incoming message contains a namespace.

IC60304 WebSphere MQ V6 JMS publish/subscribe applications
intermittently experience fatal connection errors

IZ39034 Message-driven beans are not getting restarted if the
connection is broken or the queue manager is restarted.

IZ39036 Concurrentmodificationexceptions occur when using the
WebSphere MQ resource adapter.

IZ39041 WebSphere MQ base Java and JMS clients do not map
codepage 1386 to gbk.

IZ44532 Nullpointerexception occurs when WebSphere MQ JMS
applications receive messages containing extra attributes in
the RFH2 folder

IZ44556 WebSphere MQ V6 JMS applications get a 2195 error
followed by "MQJE043: insufficient data received from queue
manager"

PK65622 COMPOUNDCLASSLOADER STORAGE LEAK BY MQ JAVA/JMS IN
THE WEBSPHERE APPLICATION SERVER (WAS) SERVANT

IZ54623 MQ Java and JMS client message buffer not reduced if
messages are not received

IZ53024 WebSphere MQ JMS performance problems when browsing a
queue using selectors

IZ53228 WebSphere MQ V6 Java and JMS clients wait for longer
than expected when connecting to an unresponsive queue manager

IZ52710 Defining a clientid property on an activation
specification usedby the WebSphere MQ resource adapter results
in an error

IZ51728 WebSphere MQ V6 JMS resource adapter does not release
connections to pool when stopping messaging endpoint.

IZ50928 WebSphere MQ JMS applications can hang when
topicconnection objects are created and closed concurrently on
different threads

IZ50800 WebSphere MQ version 6 JMS client queuebrowser
reports get inhibited exceptions to JMS exception listener

IZ49783 WebSphere MQ applications using the classes for Java
or the classes for JMS truncate passwords longer than 12
characters

IZ49676 MQ JMS connections remain open when using connection
pooling

IZ49302 The WebSphere MQ Java message service client must
treat "" for a userid the same as null when creating connections

IZ47849 WebSphere MQ V6 JMS clients appear to hang when the
queue manager they are connecting to is unavailable

IZ46837 SAP pi adapter hangs if the connection to WebSphere
MQ is broken

IZ44963 Error when JMS message reply to queue set to empty
string or string with only spaces.

PK84835 MDB LISTENER STOPPED AFTER MQGET FAILS WITH CC=2,
RC=2080
(MQRC_TRUNCATED_MSG_FAILED)

PK84221 SCRIPT CSQ8JSH1.SH DOES NOT DELETE EXISTING OSGI JARS
BEFORE UNPACKING A TAR FILE THAT INCLUDES OSGI JARS

PK80807 MQJMS2013 RECEIVED FOR BINDINGS MODE JMS CONNECTION
WITH USERID AND PASSWORD


Further information on the APARs included in WebSphere MQ
Fix Packs is available here:
http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27007069

Users who have altered the MQ_INSTALL_ROOT WebSphere
environment variable to point at an external WebSphere MQ
client or server installation are not affected by this update.

Problem conclusion

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.29.  Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

```
ZE Fix Error, see PM10331   2010/03/25
```

Comments

APAR Information

APAR number
PK83416
Reported component name
PLAT MSG COM
Reported component ID
620600101
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-03-26
Closed date
2009-05-11
Last modified date
2010-03-25

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
PLAT MSG COM
Fixed component ID
620600101

Applicable component levels

R200 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK83416: UPDATE WEBSPHERE MQ JMS CLIENT TO FIX PACK 6.0.2.8

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R200 PSY

Document Information

Share your feedback

Need support?