APAR status
Closed as program error.
Error description
[2/8/23 0:57:01:963 CET] 00000001 ManagerAdmin I TRAS0018I: The trace state has changed. The new trace state is *=info:com. lombardisoftware.userorg.UserOrgModule=off:ArtifactLoader=warni ng:ClassLoadingService=all:SharedLibrary=all. ... [2/8/23 0:57:02:222 CET] 00000001 WsServerImpl W WSVR0661W: Some bundles failed to resolve during the BAW1.AppServer server startup. The server logged OSGi bundle diagnostics to the /opt/ IBM/BAW/dir1/profiles/AppSrv01/servers/BAW1.AppServer/configur ation/diag-1675814204129.logfile. ... Source file trace.log At least one bundle failed to resolve. Writing resolution diagnostics to file /opt/IBM/BAW/dir1/profiles/AppSrv01/server s/BAW1.AppServer/configuration/diag-1676246192430.log BEGIN resolution diagnostics System Bundle [0] .... initial@reference:file:plugins/org.eclipse.core.runtime_.jar/ [5] Direct constraints which are unresolved: Missing optionally required bundle org.eclipse.core.runtime.compatibility.auth_[3.2.0,4.0.0). Missing dynamically imported package org.eclipse.core.internal.runtime.auth_0.0.0. ... Source file: diag-1676246192430.log . ------------------------------ . After those unresolved constraints I can see lots of other listed as unresolved, could you please take a look at the above file and let us know what should be the next steps?
Local fix
Jarid update:The diagnostic log does not indicate any non-optiona/dynamic unresolved bundles, and I believe this constitutes a bug in the logic. Please open an APAR and we'll update the logic to avoid logging the message in those cases.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: Bundle resolution diagnostics do not * * filter out optional and dynamic * * resolution * **************************************************************** * RECOMMENDATION: * **************************************************************** When the server is started, OSGi bundles are scanned to ensure that all bundles have resolved and that there are no package import failures. This process, however, treats optional and dynamic imports with the same level of import as mandatory imports, despite the fact that the dynamic and optional imports do not as actively cause issues at runtime. The resulting output is much greater in size than it would be if only the mandatory failures were logged, and that makes the output much more difficult to interpret.
Problem conclusion
Optional and dynamic import resolution failures are now only logged when bootstrap tracing is enabled via the ws.ext.debug flag (set to "true" as a JVM custom property or by adding - Dws.ext.debug=true as a generic JVM option on the server). The fix for this APAR is targeted for inclusion in fix packs 8.5.5.27 and 9.0.5.21. For more information, see 'Recommended Updates for WebSphere Application Server': https://www.ibm.com/support/pages/node/715553
Temporary fix
Comments
APAR Information
APAR number
PH52585
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2023-02-14
Closed date
2024-06-05
Last modified date
2024-06-05
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 APP S
Fixed component ID
5724J0800
Applicable component levels
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]
Document Information
Modified date:
06 June 2024