Fixes are available
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
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
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
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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.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
APAR status
Closed as program error.
Error description
In a mixed topology environment with Websphere Application Server deployment manager at v8.5 and nodes at v7.0 when an attempt is made to stop or reset the MQLink Sender channel, the following FFDCs are produced: FFDC Exception:com.ibm.ws.console.sib.sibresources. SIBMBeanNotFoundException SourceId:com.ibm.ws.console.sib.sibresources. SIBMQLinkCollectionAction.execute ProbeId:275 Reporter:com.ibm.ws.console.sib.sibresources. SIBMQLinkCollectionAction@ec336053 com.ibm.ws.console.sib.sibresources.SIBMBeanNotFoundException: SIBMQLink MBean not found: WebSphere:type=SIBMQLink, mbeanIdentifier=cells/Cell01/clusters/Cls01/sib-engines.xml #SIBMQLink_1430983025792,* at com.ibm.ws.console.sib.sibresources.SIBMBeanUtils. invokeMBean(SIBMBeanUtils.java:115) at com.ibm.ws.console.sib.sibresources.SIBMQLinkCollection Action.execute(SIBMQLinkCollectionAction.java:377) FFDC Exception:javax.management.MBeanException SourceId:com.ibm.ws.console.sib.sibresources.SIBMBeanUtils. invokeMBean ProbeId:54 javax.management.MBeanException: Operation isEnabled not in ModelMBeanInfo at com.ibm.ws.management.connector.soap.SOAPConnector Client.handleAdminFault(SOAPConnectorClient.java:959) at com.ibm.ws.management.connector.soap.SOAPConnector Client.invokeTemplateOnce(SOAPConnectorClient.java:924) at com.ibm.ws.management.connector.soap.SOAPConnector Client.invokeTemplate(SOAPConnectorClient.java:689) at com.ibm.ws.management.connector.soap.SOAPConnector Client.invokeTemplate(SOAPConnectorClient.java:679) at com.ibm.ws.management.connector.soap.SOAPConnector Client.invoke(SOAPConnectorClient.java:665) at com.ibm.ws.management.connector.soap.SOAPConnector Client.invoke(SOAPConnectorClient.java:487) at com.sun.proxy.$Proxy38.invoke(Unknown Source) at com.ibm.ws.management.AdminClientImpl.invoke(Admin ClientImpl.java:224) at com.ibm.ws.management.AdminServiceImpl$1.run(Admin ServiceImpl.java:1365) at com.ibm.ws.security.util.AccessController.do Privileged(AccessController.java:118) at com.ibm.ws.management.AdminServiceImpl.invoke (AdminServiceImpl.java:1228) at com.ibm.ws.console.sib.sibresources.SIBMBeanUtils. invokeMBean(SIBMBeanUtils.java:110) at com.ibm.ws.console.sib.sibresources.SIBMQLink CollectionAction.execute(SIBMQLinkCollectionAction.java:440)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider for * * IBM WebSphere Application Server * **************************************************************** * PROBLEM DESCRIPTION: In a mixed topology environment when * * any action is attempted on an MQ link * * using the console "MBeanException: * * Operation isEnabled not in * * ModelMBeanInfo" is thrown. * **************************************************************** * RECOMMENDATION: * **************************************************************** In a mixed topology environment with Websphere Application Server deployment manager at v8.0 or above and nodes at v7.0 when an attempt is made perform any action on MQ link using the administrative console the following exception is observed in the logs. FFDC Exception:javax.management.MBeanException SourceId:com.ibm.ws.console.sib.sibresources.SIBMBeanUtils. invokeMBean ProbeId:54 javax.management.MBeanException: Operation isEnabled not in ModelMBeanInfo The exception is due to a new method "isenabled" introduced post V8.0 which is called before any operation is performed. Since the method does not exist on the V7.0 MBean the exception is thrown. The new method was actually introduced to avoid making any calls to the MBean if the MBean is not active. But v7.0 MBeans do not have the method so the exception is reported.
Problem conclusion
To address the issue when invoking the MBean call we check if its a mixed cell environment. If so, if the node level is lower than v8.0 then we ignore the call to isenabled() and straight away invoke the requested operation. The fix for this APAR is currently targeted for inclusion in fix packs 8.0.0.13 and 8.5.5.9 . 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
PI45426
Reported component name
WAS SIB & SIBWS
Reported component ID
620800101
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-07-21
Closed date
2015-11-09
Last modified date
2016-10-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
WAS SIB & SIBWS
Fixed component ID
620800101
Applicable component levels
R300 PSY
UP
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
11 January 2022