Fixes are available
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for AIX
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for IBM i
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Windows
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for HP-UX
7.0.0.5: Java SDK 1.6 SR5 Cumulative Fix for WebSphere Application Server
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Solaris
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Linux
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for IBM i
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for AIX
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Windows
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for HP-UX
7.0.0.7: Java SDK 1.6 SR6 Cumulative Fix for WebSphere Application Server
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Solaris
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Linux
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for IBM i
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Windows
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for AIX
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for HP-UX
7.0.0.9: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Solaris
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Linux
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
Fixes for the default messaging provider for WebSphere Application Server Version 7, including use of this messaging provider the the WS-Notification protocol
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider for * * IBM WebSphere Application Server Version 7 * **************************************************************** * PROBLEM DESCRIPTION: Problems performing JMS messaging via * * a Service Integration Bus, including * * when using WS-Notification * **************************************************************** * RECOMMENDATION: * **************************************************************** The following issues are addressed in this APAR that might be seen when using the default messaging provider for WebSphere Application Server Version 7: - An application connecting to a messaging engine over a network an consuming messages with read-ahead enabled might stop receiving messages because of a deadlock. A thread dump of the JVM where the application is running will show two deadlocked threads, one in ConsumerSessionProxy.unlockAll and another in ProxyReceiveListener.processMessage. - A NullPointerException might be thrown when the dump method on the SIBMessagingEngine MBean is called meaning that no dump is produced. - In a mixed version cell (6.0 or 6.1 on one server and 7.0 on another) where the 6.1 server was hosting an WebSphere MQ Link but the application producing messages to be sent over that link was running on the 7.0 server, a failure and restart of the 6.1 server meant that messages were no longer sent over the link. The link transmitter for the connection to the 6.1 server from the 7.0 server was seen to be in the warning state with the warning message "CWSIP0911W: No response from receiver, acknowledgment of sent messages are overdue" in the administration console. - Tn a mixed version cell (6.0 or 6.1 on one server and 7.0 on another) an application connecting to the bus might receive the following exception: ERROR: com.ibm.websphere.sib.exception.SIErrorException: java.security.PrivilegedActionException: java.lang.ClassNotFoundException: com.ibm.ws.sib.jfapchannel.impl.octracker. JFapOutboundChannelDefinitionImpl - If the auditing service for a bus is enabled, an exception might occur that prevents any auditing records being created for that connection attempt. - The command assistance output generated when modifying a service integration bus link in the administration console is incorrect. It includes a preferLocal parameter to the AdminConfig.modify command that does not exist. - A NullPointerException might be thrown by LocalAccessControl.localCheckDestinationAccess if a user attempts an unsupported operation on a destination. Instead a declared exception containing a meaningful exception should have been thrown. - When an ondemand publisher is registered with the WS-Notification Broker, the Broker subscribes to each of the topics registered by the producer, but the subscription loses an XML namespace and prefix element that was specified with the publisher. - When a messaging engine is stopped, message-driven beans that are connected to that messaging engine might not attempt to reconnect to the bus. - The AdminTask.removeDestinationRoles command might fail with a NullPointerException. - The message detail panel in the administration console might incorrectly show a message in UNKNOWN state. - The message detail panel in the administration console shows transaction identifiers in a form that cannot be correlated with other resources, and does not match the form outputted by the transaction manager. - The AdminTask.modifySIBDestination command might fail with the following error: CWSJA0150E: The "queuePoints" parameter can only be used when the target destination is a queue destination with one or more queue points. - When multiple queue points exist for a partitioned queue, and the "Message Visibility" on the JMS Queue used by consumers has been set to "Messages on all queue points are visible", some messages might remain on a queue point without being delivered to an active consumer. - In an environment with multiple messaging engines in a single cluster bus member, messaging might be onto a remote queue point for delivery to a messaging engine that is not running. - The following exception might be seen after changing the value of the "Receive Exclusive" checkbox for a bus destination: CWSIP0001E: An internal messaging error occurred in com.ibm.ws.sib.processor.impl.LocalQPConsumerKeyGroup, 1:688:1.6.1.14 - If the auditing service for a bus is enabled and an unauthorized user attempts to delete a subscription from topic space on that bus, no audit record is produced. - When multiple messaging engines are added to a cluster, the "Create tables" attribute may be unset on the second and subsequent messaging engines meaning that those messaging engines are not able to start. - When operating with Bus Security enabled, users of the SdoRepository MBean are unable to use the listResources method even if the user has an appropriate bus role. Any attempt to use this method results in the user being notified thatthey are not authorized. - In an environment with multiple messaging engines in a bus, an FFDC containing a StateException from method AOStream.consumeNonPersistentMessages might be seen - A ConcurrentModificationException might be issued when subscribing large numbers of consumers to a WS-Notification broker, due to a lack of synchronization between methods. - WS-Notifcation and WS-ReliableMessaging initialization never completes following a failover from one server to another. The problem is caused by a state change method for the BrokerServiceHandler was not being called during failover. - A NullPointerException might be thrown by JFAPCommunicator.defaultChecker during a web service invocation if an incorrect WS-Notification security configuration has been configured. Instead a declared exception containing a meaningful exception should have been thrown. - The WS-Notification service fails to start when the WS-Notification service name contains underscores. - The following exception might be thrown after a bus destination is deleted and recreated: java.lang.NullPointerException at com.ibm.ws.sib.processor.impl.indexes. AbstractDestinationIndex.cleanup( AbstractDestinationIndex.java:218)
Problem conclusion
The fix for this APAR addresses the problems described above in the default messaging provider, and WS-Notification. The APAR is targeted for delivery in WebSphere Application Server fix pack 7.0.0.5.
Temporary fix
Comments
APAR Information
APAR number
PK81434
Reported component name
PLAT MSG COM
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-02-26
Closed date
2009-06-26
Last modified date
2009-06-26
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
620800101
Applicable component levels
R300 PSY
UP
Document Information
Modified date:
24 October 2021