Jira had problems starting up

Question

we got error as all user can't log in to jira service (username or password not correct), we restart the server to fix the issue

after restart we get different error as below

we checked the log from jira in server we found this error

log4j:WARN No appenders could be found for logger (com.atlassian.analytics.client.properties.LoggingProperties).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Security framework of XStream not initialized, XStream is probably vulnerable.

Nic Brough -Adaptavist- · Answer

That's warnings from later on, when it's trying to shut down.

You need to be reading the errors from where it's trying to start up.

Abdullah Bahattab · Answer

Thank you for your reply

I didn't find any error log file, i only find other warning

07-Mar-2021 10:23:44.853 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [JonasBatch] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:502)
org.objectweb.jonas_timer.TimerManager.batch(TimerManager.java:193)
org.objectweb.jonas_timer.Batch.run(TimerManager.java:65)
07-Mar-2021 10:23:44.853 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [JonasClock] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
java.lang.Thread.sleep(Native Method)
org.objectweb.jonas_timer.TimerManager.clock(TimerManager.java:142)
org.objectweb.jonas_timer.Clock.run(TimerManager.java:46)
07-Mar-2021 10:23:44.885 INFO [Thread-35] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-80"]
07-Mar-2021 10:23:44.900 INFO [Thread-35] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-80"]

Nic Brough -Adaptavist- · Answer

You need to read the log again, looking for the actual error that halted it (not warnings about logging)