I am facing a similar issue where I can see some warnings and errors,which also caused Jenkins shutdown. Is there a way we can prevent it from happening in the future
23-Apr-2018 10:14:13.433 WARNING [splunkins-worker-1] com.splunk.splunkjenkins.utils.LogConsumer.handleRetry Server is busy, maybe caused by blocked queue, please check https://wiki.splunk.com/Community:TroubleshootingBlockedQueues, will wait 30 seconds and retry
23-Apr-2018 10:14:13.111 WARNING [splunkins-worker-2] com.splunk.splunkjenkins.utils.LogConsumer.handleRetry Server is busy, maybe caused by blocked queue, please check https://wiki.splunk.com/Community:TroubleshootingBlockedQueues, will wait 30 seconds and retry
23-Apr-2018 10:14:36.362 SEVERE [http-nio-8080-Acceptor-0] hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler.uncaughtException A thread (http-nio-8080-Acceptor-0/72) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code.
java.lang.OutOfMemoryError: Java heap space
at java.nio.HeapByteBuffer. (HeapByteBuffer.java:57)
at java.nio.ByteBuffer.allocate(ByteBuffer.java:335)
at org.apache.tomcat.util.net.SocketBufferHandler. (SocketBufferHandler.java:41)
at org.apache.tomcat.util.net.NioEndpoint.setSocketOptions(NioEndpoint.java:375)
at org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(NioEndpoint.java:473)
at java.lang.Thread.run(Thread.java:745)
... View more