Fixes are available
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 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
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
A Websphere Application Server Service Integration Buslink is configured between two Buses. When messages are sent over the buslink,JMFSchemaViolationException occurs and the buslink stops. The following error is written to Systemut.log: CWSIC2009E: There was a failure to send a message: exception com.ibm.websphere.sib.exception.SIResourceException: com. ibm.ws.sib.mfp.MessageDecodeFailedException: com.ibm.ws. sib.mfp.jmf.JMFSchemaViolationException: schemaId=null. FFDCs are produced with the following stack: FFDC Exception:com.ibm.ws.sib.mfp.jmf.JMFSchemaViolation Exception SourceId:com.ibm.ws.sib.mfp.impl.JsMsgObject. initializePart ProbeId:jmo450 Reporter:com.ibm.ws.sib. mfp.impl.JsMsgObject@145c145c com.ibm.ws.sib.mfp.jmf.JMFSchemaViolationException: schemaId=null at com.ibm.ws.sib.mfp.jmf.impl.JSRegistry.decode (JSRegistry.java:310) at com.ibm.ws.sib.mfp.impl.JsMsgObject.initializePart (JsMsgObject.java:747) at com.ibm.ws.sib.mfp.impl.JsMsgObject.initialize(JsMsg Object.java:603) at com.ibm.ws.sib.mfp.impl.JsMsgObject.<init>(JsMsg Object.java:304) at com.ibm.ws.sib.mfp.impl.JsMessageFactoryImpl.create InboundJsMessage(JsMessageFactoryImpl.java:201) at com.ibm.ws.sib.comms.common.CommsByteBuffer.getMessage (CommsByteBuffer.java:994) at com.ibm.ws.sib.comms.server.clientsupport.StaticCAT Producer.sendSessMsg(StaticCATProducer.java:511) at com.ibm.ws.sib.comms.server.clientsupport.StaticCAT Producer.rcvSendSessMsgNoReply(StaticCATProducer.java:434) at com.ibm.ws.sib.comms.server.clientsupport.Server TransportReceiveListener.dataReceived(ServerTransport ReceiveListener.java:479) at com.ibm.ws.sib.jfapchannel.impl.rldispatcher. ConversationReceiveListenerDataReceivedInvocation.invoke (ConversationReceiveListenerDataReceivedInvocation.java:195) at com.ibm.ws.sib.jfapchannel.impl.rldispatcher.Receive ListenerDispatchQueue.run(ReceiveListenerDispatchQueue. java:542) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1646) FFDC Exception:com.ibm.ws.sib.mfp.MessageDecodeFailedException SourceId:com.ibm.ws.sib.comms.common.CommsByteBuffer. getMessage ProbeId:5-006-0002 Reporter:com.ibm.ws. sib.comms.server.CommsServerByteBuffer@144c144c com.ibm.ws.sib.mfp.MessageDecodeFailedException: c om.ibm.ws.sib.mfp.jmf.JMFSchemaViolationException: schemaId=null at com.ibm.ws.sib.mfp.impl.JsMsgObject.initializePart (JsMsgObject.java:754) at com.ibm.ws.sib.mfp.impl.JsMsgObject.initialize (JsMsgObject.java:603) at com.ibm.ws.sib.mfp.impl.JsMsgObject.<init>(JsMsg Object.java:304) .............. Caused by: com.ibm.ws.sib.mfp.jmf.JMFSchemaViolation Exception: schemaId=null at com.ibm.ws.sib.mfp.jmf.impl.JSRegistry.decode (JSRegistry.java:310) at com.ibm.ws.sib.mfp.impl.JsMsgObject.initialize Part(JsMsgObject.java:747)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider * * for * * IBM WebSphere Application Server * **************************************************************** * PROBLEM DESCRIPTION: When messages are sent over a * * buslink, a JMFSchemaViolationException * * occurs and the buslink stops. * **************************************************************** * RECOMMENDATION: * **************************************************************** In the SIBus environments where SIBus links are used to transfer the messages from one SIBus to another SIBus, in order to successfully transfer the messages from the source messaging engine to the target messaging engine, the MFP schemas required to de-serialize the messages at the target side have to be first exchanged between source messaging engine and the target messaging engine. However, there are situations observed in certain SIB topologies with SIB links involved where the message transfer is triggered even before the MFP schemas are exchanged between the source and target messaging engines. The required MFP schemas are not exchanged successfully because the MEConnection on the ConversationState object is not set. Due to absence of the MEConnection during the transfer of schemas, the required schemas were not exchanged successfully.
Problem conclusion
The code has been fixed so that MEConnection is available during the transfer of the MFP Schemas leading to successful exchange of required MFP Schemas. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.35, 8.0.0.9 and 8.5.5.3. 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
PI07806
Reported component name
WAS SIB & SIBWS
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-12-12
Closed date
2014-03-26
Last modified date
2014-05-20
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
WAS SIB & SIBWS
Fixed component ID
620800101
Applicable component levels
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 April 2022