APAR status
Closed as program error.
Error description
When using the WTX 8.3.x Map Node, Message Broker abends occur along with high CPU usage after upgrading from WMB 7.0.0.2 to 7.0.0.3. The following stack trace is reported for the abend: ----------------------------- Stack dump for current thread ( 1) (0x0998f5e0+0x00000000) <no name available> [/opt/IBM/wsdtx/wmqi/dtxwmqi.lil] (0x0999a500+0x00000000) <no name available> [/opt/IBM/wsdtx/wmqi/dtxwmqi.lil] (0x09992820+0x00000000) <no name available> [/opt/IBM/wsdtx/wmqi/dtxwmqi.lil] (0x161ef180+0x00000178) initialize__10ImbCniNodeFP6cniVftPvPUs [/opt/IBM/mqsi/7.0/lib/libimbdfplg.a(libimbdfplg64.a.so)] (0x161eec80+0x00000100) createNode__17ImbCniNodeFactoryCFRC10ImbWstringT1P18ImbDataFlowM anager [/opt/IBM/mqsi/7.0/lib/libimbdfplg.a(libimbdfplg64.a.so)] (0x13adc100+0x00000368) createNode__18ImbDataFlowManagerFRC10ImbWstringT1 [/opt/IBM/mqsi/7.0/lib/libMessageServices.a(libMessageServices.a .so)] (0x13ad8580+0x000003ec) createResource__18ImbDataFlowManagerFRCQ2_10ImbMessage10ReadCurs orRQ2_10ImbMessage11WriteCursorb [/opt/IBM/mqsi/7.0/lib/libMessageServices.a(libMessageServices.a .so)] (0x135d4a80+0x00000d9c) loadAllDataFlowsFromDatabase__19ImbDataFlowDirectorFv [/opt/IBM/mqsi/7.0/lib/libMessageServices.a(libMessageServices.a .so)] (0x13ca2700+0x00000058) initialize__19ImbDataFlowDirectorFv [/opt/IBM/mqsi/7.0/lib/libMessageServices.a(libMessageServices.a .so)] (0x160e6880+0x00003bd8) start__7ImbMainFR18ImbStartParameters [/opt/IBM/mqsi/7.0/lib/libbipmain.a] (0x00000980+0x00000294) main [DataFlowEngine] (0x00000240+0x0000009c) __start [DataFlowEngine]
Local fix
WTXCQ - WTX00039184 PVB / PVB Circumvention: None
Problem summary
Users Affected: WebSphere Message Broker 7.0.0.3 users of the WTX Transformation Extender Plugin Node are affected when the Broker is using JRE1.6 SR9 FP1. When using JRE1.6 SR9 FP2, the problem does not occur. Problem Description: The Message Broker Plugin node causes a crash whenever the JVM is not initialized or reported as being initialized by the JNI layer. Platforms Affected: ALL
Problem conclusion
The WTX Node detects JVM/JNI initialization failures and avoids crashing as a result. Any JVM/JNI initialization failures are logged to the Service trace and an error code is propagated back to the Broker environment layer. JRE has to be updated to correct this error condition. Delivered in: 8.3.0.5, 8.4.0.1
Temporary fix
Comments
APAR Information
APAR number
PM55064
Reported component name
WEBSPHERE LAUNC
Reported component ID
5724M4011
Reported release
830
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2011-12-28
Closed date
2012-02-28
Last modified date
2012-08-02
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
WEBSPHERE LAUNC
Fixed component ID
5724M4011
Applicable component levels
R830 PSY
UP
R840 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSD8","label":"IBM Transformation Extender"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.3","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
02 August 2012