Fixes are available
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
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
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
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
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
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
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.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
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
WebSphere Application Server JVM hosting the Service Integration Bus Messaging Engine throws JMFUninitializedAccessException . The following FFDC is produced: Exception = com.ibm.ws.sib.mfp.jmf.JMFUninitializedAccess Exception Source = com.ibm.ws.sib.mfp.impl.JsMsgObject.encodeFast probeid = jmo570 Stack Dump = com.ibm.ws.sib.mfp.jmf.JMFUninitializedAccess Exception: guaranteedValue/set/startTick Schema: com.ibm.ws. sib.mfp.schema.JsHdr2Schema at com.ibm.ws.sib.mfp.jmf.impl.JSMessageImpl.getLength (JSMessageImpl.java:930) at com.ibm.ws.sib.mfp.jmf.impl.JSMessageImpl.getEncodedLength (JSMessageImpl.java:843) at com.ibm.ws.sib.mfp.jmf.impl.JSDynamic.getEncodedLength (JSDynamic.java:143) at com.ibm.ws.sib.mfp.jmf.impl.JSField.getEncodedValue Length(JSField.java:185) at com.ibm.ws.sib.mfp.jmf.impl.JSMessageImpl.getLength (JSMessageImpl.java:939) at com.ibm.ws.sib.mfp.jmf.impl.JSMessageImpl.getEncoded Length(JSMessageImpl.java:843) at com.ibm.ws.sib.mfp.impl.JsMsgObject.encodeFast(JsMsg Object.java:718) at com.ibm.ws.sib.mfp.impl.JsMessageImpl.encodeFast(Js MessageImpl.java:648) at com.ibm.ws.sib.comms.common.CommsUtils.encodeMessage (CommsUtils.java:739) at com.ibm.ws.sib.comms.server.clientsupport.CATProxy Consumer.sendMessage(CATProxyConsumer.java:737) The following error is written to the SystemOut.log during startup of the JVM hosting the application: CWSIV0770W: A consumer for remote destination {0} on bus {1} for endpoint activation {2} failed with exception com.ibm.websphere.sib.exception.SIErrorException: CWSIC8002E: An internal error occurred. An unknown or unexpected exception was thrown by the core API: com.ibm.ws.sib.mfp.MessageEncodeFailedException: com.ibm.ws.sib.mfp.jmf.JMFUninitializedAccessException: guaranteedValue/set/startTick Schema:com.ibm.ws.sib.mfp. schema.JsHdr2Schema .
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider for * * IBM WebSphere Application Server Version 7.0* **************************************************************** * PROBLEM DESCRIPTION: JMFUninitializedAccessException using * * best-effort nonpersistent * * pub/sub messages in a bus * * with multiple messaging engines * **************************************************************** * RECOMMENDATION: * **************************************************************** The JMFUninitializedAccessException exception occurs when there is a subscriber to a topic connected to a messaging engine as a local subscriber (but running on a remote server connected over a network), and there are multiple messaging engines in the bus with subscribers attached for that topic. For best-effort nonpersistent messages the code preparing the message for delivery to remote proxy subscriptions on other messaging engines in the bus might run simultaneously to serializing the message for delivery to a locally-attached subscriber (connected over a network). Whereas for other reliability levels, the message is prepared for delivery to remote messaging engines synchronously, before the message is delivered to locally attached subscribers The two pieces of code preparing the message for delivery, and delivering it over a network, cannot run simultaneously against the same copy of the message, so the JMFUninitializedAccessException exception occurs indicating that the local-delivery thread has seen a corrupt copy of the message (because it was being modified by the other thread).
Problem conclusion
The fix for this APAR updates the special case code used for best-effort nonpersistent messages to take a copy of the message before it prepares it for delivery to remote messaging engines. This allows the code running in parallel to deliver the message to the locally attached subscriber to run successfully, without seeing a corrupt message. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.13. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM15466
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
2010-05-28
Closed date
2010-08-31
Last modified date
2010-08-31
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
Document Information
Modified date:
24 October 2021