Troubleshooting
Problem
When an application, like Spring/Springboot, containing SLF4J (in particular, jul-to-slf4j.jar) starts, all logging from the WebSphere Application Server (WSAS) process ceases.
Symptom
When the application in question is started, at some point all logging to the server's standard output (SystemOut.log and SystemErr.log) ends. When the application auto-starts as part of server startup, the "open for e-business" message does not appear in the server log, since no logging occurs after the point of application start. The server is likely still functional and responsive to requests, but nothing additional is entered into its logs.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSAW57","label":"WebSphere Application Server Network Deployment"},"ARM Category":[{"code":"a8m50000000Cd9UAAS","label":"WebSphere Application Server traditional-All Platforms-\u003ELogging"}],"ARM Case Number":"TS016078265","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Historical Number
TS016078265
Was this topic helpful?
Document Information
Modified date:
15 November 2024
UID
ibm17150237