Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- docker run -d --name sonarqube
- -p 9000:9000 -p 9092:9092
- -e SONARQUBE_JDBC_USERNAME=sonar
- -e SONARQUBE_JDBC_PASSWORD=sonar
- -e SONARQUBE_JDBC_URL="jdbc:mysql://111.222.33.444:3306/sonar?characterEncoding=utf8&useUnicode=true&rewriteBatchedStatements=true"
- sonarqube
- 2017.04.21 06:39:37 WARN web[][o.a.c.l.WebappClassLoaderBase] The web application [ROOT] appears to have started a thread named [elasticsearch[Pip the Troll][[timer]]] 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.elasticsearch.threadpool.ThreadPool$EstimatedTimeThread.run(ThreadPool.java:747)
- 2017.04.21 06:39:37 WARN web[][o.a.c.l.WebappClassLoaderBase] The web application [ROOT] appears to have started a thread named [elasticsearch[Pip the Troll][scheduler][T#1]] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
- sun.misc.Unsafe.park(Native Method)
- java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
- java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
- java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)
- java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
- java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067)
- java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127)
- java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
- java.lang.Thread.run(Thread.java:745)
- 2017.04.21 06:39:37 WARN web[][o.a.c.l.WebappClassLoaderBase] The web application [ROOT] appears to have started a thread named [elasticsearch[Pip the Troll][transport_client_worker][T#1]{New I/O worker #1}] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
- sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
- sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269)
- sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93)
- sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
- sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
- org.jboss.netty.channel.socket.nio.SelectorUtil.select(SelectorUtil.java:68)
- org.jboss.netty.channel.socket.nio.AbstractNioSelector.select(AbstractNioSelector.java:434)
- org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:212)
- org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)
- org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
- org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
- org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
- java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
- java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
- java.lang.Thread.run(Thread.java:745)
- 2017.04.21 06:39:37 WARN web[][o.a.c.l.WebappClassLoaderBase] The web application [ROOT] appears to have started a thread named [elasticsearch[Pip the Troll][transport_client_worker][T#2]{New I/O worker #2}] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
- sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
- sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269)
- sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93)
- sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
- sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
- org.jboss.netty.channel.socket.nio.SelectorUtil.select(SelectorUtil.java:68)
- org.jboss.netty.channel.socket.nio.AbstractNioSelector.select(AbstractNioSelector.java:434)
- org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:212)
- org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)
- org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
- org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
- org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
- java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
- java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
- java.lang.Thread.run(Thread.java:745)
- 2017.04.21 06:39:37 WARN web[][o.a.c.l.WebappClassLoaderBase] The web application [ROOT] appears to have started a thread named [elasticsearch[Pip the Troll][transport_client_worker][T#3]{New I/O worker #3}] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
- sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
- sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269)
- sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93)
- sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
- sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
- org.jboss.netty.channel.socket.nio.SelectorUtil.select(SelectorUtil.java:68)
- org.jboss.netty.channel.socket.nio.AbstractNioSelector.select(AbstractNioSelector.java:434)
- org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:212)
- org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)
- org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
- org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
- org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
- java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
- java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
- java.lang.Thread.run(Thread.java:745)
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement