Fixes are available
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
When try to create a New transport chain, in a dynamic cluster via the server template Navigation: Dynamic Clusters > GENERIC > Server template > Web container transport chains: When tried via wsadmin command, the wsadmin.traceout has the following error: 1:00:35 PM: Tony: [10/14/14 18:06:53:818 EDT] 00000001 AbstractShell E WASX7120E: Diagnostic information from exception with text "com.ibm.websphere.management.exception.MetadataNotAvailableExce ption com.ibm.websphere.management.exception.DocumentNotFoundException : cells/SBCell/nodes/ere:_Websphere_Config_Data_Id=cells/SBCell/dy namicclu sters/GENERIC/node-metadata.properties " follows: com.ibm.websphere.management.exception.MetadataNotAvailableExce ption: Could not obtain managed object metadata from Config Repository. at com.ibm.ws.management.metadata.ManagedObjectMetadataAccessorImpl .extract Metadata(ManagedObjectMetadataAccessorImpl.java:299) at com.ibm.ws.management.metadata.ManagedObjectMetadataAccessorImpl .getMeta dataProperties(ManagedObjectMetadataAccessorImpl.java:188) at com.ibm.websphere.management.metadata.ManagedObjectMetadataHelpe r.getNod ePlatformOS(ManagedObjectMetadataHelper.java:778) ................. Caused by: com.ibm.websphere.management.exception.DocumentNotFoundException : cells/SBCell/nodes/ere:_Websphere_Config_Data_Id=cells/SBCell/dy namicclu sters/GENERIC/node-metadata.properties at com.ibm.ws.management.repository.FileRepository.extractInternal( FileRepo sitory.java:1134) at com.ibm.ws.management.repository.FileRepository.extract(FileRepo sitory.j ava:1115) ... 36 more
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server Full * * Profile Version 8.5.5 users * **************************************************************** * PROBLEM DESCRIPTION: When creating a transport chain via a * * dynamic cluster server template the * * process fails * **************************************************************** * RECOMMENDATION: * **************************************************************** When creating a transport chain via a dynamic cluster server template the process fails throwing the following exceptions: WASX7015E: Exception running command: ... exception information: com.ibm.websphere.management.exception.MetadataNotAvailableExcep tion com.ibm.websphere.management.exception.DocumentNotFoundException : ...
Problem conclusion
The Channel Framework code was modified to correctly handle the request to create chains via the dynamic cluster server template for WebSphere Application Server V8.5.5. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.6. 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
PI30464
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-11-26
Closed date
2014-12-29
Last modified date
2014-12-29
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
28 April 2022