Can't access Jjira after some time of inactivity

Question

We installed Jira server and came across some hickup that i can describe like some sort of hybernation of Jira aplication.

Firstly Jira service and Confluence service seem like they are up and running but no browser can connect to them. This happens after few days of innactivity in Jira. After i restart services all work perfectly.

what could be the issue.

I can provide Jira and confluence logs for you if you need them(just point me to them).

Regards, Tomaž

Primož Tomšič · Answer

What does "the browser cannot connect" mean here?
Let say i come to work in the morning and try to connect to jira via my Chrome.. the browser just scrolls and trys to connect (the url is correct but the page is blank and scrolling)

You get an error?
No error on browser.

It sits there with a blank page for ages and then gives a timeout? 
i have never waited for that long..

It just churns until you close it?
Correct.

jirasoftware.stderr.log since up and running today:

03-Apr-2019 10:36:28.380 SEVERE [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run Unexpected death of background thread [ContainerBackgroundProcessor[StandardEngine[Catalina]]]
 java.lang.OutOfMemoryError: Java heap space

80-exec-3"  at java.util.Arrays.copyOf(Arrays.java:3332)
 at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:124)
 at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:448)
 at java.lang.StringBuffer.append(StringBuffer.java:270)
 at com.atlassian.logging.log4j.StackTraceCompressor.outputMinimumLines(StackTraceCompressor.java:229)
 at com.atlassian.logging.log4j.StackTraceCompressor.filterStackTrace(StackTraceCompressor.java:171)
 at com.atlassian.logging.log4j.FilteredPatternLayout.formatStackTrace(FilteredPatternLayout.java:345)
 at com.atlassian.logging.log4j.FilteredPatternLayout.format(FilteredPatternLayout.java:330)
 at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:310)
 at org.apache.log4j.RollingFileAppender.subAppend(RollingFileAppender.java:276)
 at org.apache.log4j.WriterAppender.append(WriterAppender.java:162)
 at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251)
 at com.atlassian.jira.logging.JiraHomeAppender.doAppend(JiraHomeAppender.java:206)
 at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66)
 at org.apache.log4j.Category.callAppenders(Category.java:206)
 at org.apache.log4j.Category.forcedLog(Category.java:391)
 at org.apache.log4j.Category.log(Category.java:856)
 at org.slf4j.impl.Log4jLoggerAdapter.log(Log4jLoggerAdapter.java:601)
 at org.apache.commons.logging.impl.SLF4JLocationAwareLog.warn(SLF4JLocationAwareLog.java:199)
 at org.apache.commons.dbcp2.SwallowedExceptionLogger.onSwallowException(SwallowedExceptionLogger.java:57)
 at org.apache.commons.pool2.impl.BaseGenericObjectPool.swallowException(BaseGenericObjectPool.java:858)
 at org.apache.commons.pool2.impl.BaseGenericObjectPool$Evictor.run(BaseGenericObjectPool.java:1038)
 at java.util.TimerThread.mainLoop(Timer.java:555)
 at java.util.TimerThread.run(Timer.java:505)
java.lang.OutOfMemoryError: Java heap space
 at java.nio.HeapByteBuffer.<init>(HeapByteBuffer.java:57)
 at java.nio.ByteBuffer.allocate(ByteBuffer.java:335)
 at org.apache.coyote.http11.Http11InputBuffer.init(Http11InputBuffer.java:695)
 at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:669)
 at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
 at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:800)
 at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1471)
 at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
 at java.lang.Thread.run(Thread.java:748)
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
Exception in thread "I/O dispatcher 2" Exception in thread "NavLink RestCapabilitiesClient:thread-1" java.lang.OutOfMemoryError: Java heap space
Exception in thread "I/O dispatcher 4" java.lang.OutOfMemoryError: Java heap space
Exception in thread "http-nio-8080-ClientPoller-0" Exception in thread "I/O dispatcher 7" Exception in thread "Caesium-1-2" Exception in thread "http-nio-8080-ClientPoller-1" Exception in thread "pool-11-thread-1" java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
Exception in thread "http-nio-8080-exec-6" java.lang.OutOfMemoryError: Java heap space
Exception in thread "http-nio-8080-exec-18" java.lang.OutOfMemoryError: Java heap space
Exception in thread "httpclient-io:thread-1" java.lang.OutOfMemoryError: Java heap space
Exception in thread "pool-1-thread-1-Logging Task Scheduler" java.lang.OutOfMemoryError: Java heap space
Exception in thread "ContainerBackgroundProcessor[StandardEngine[Catalina]]" java.lang.OutOfMemoryError: Java heap space
Exception in thread "Thread-55" java.lang.OutOfMemoryError: GC overhead limit exceeded
Exception in thread "Thread-57" java.lang.OutOfMemoryError: GC overhead limit exceeded
Exception in thread "Thread-78" java.lang.OutOfMemoryError: Java heap space
Exception in thread "Thread-99" java.lang.OutOfMemoryError: GC overhead limit exceeded

Nic Brough -Adaptavist- · Answer

This suggests the applications are failing somewhere (although not the Tomcat running them). What does "the browser cannot connect" mean here? You get an error? It sits there with a blank page for ages and then gives a timeout? It just churns until you close it? Logs to check are /logs/atlassian-.log first - that should have most errors thrown into it. Sometimes though, if it's an issue with the Tomcat service, you will want to read /log/catalina.out