-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failing to start - #25
Comments
@johndoran this doesn't look like full log, so could you please provide full log, including command, which was used to start container? Also - do you experience the same problem with other versions? |
Hi, full stack attached. I'm using ecs to deploy the container - here is my task definition.
|
I ran the 4.5.7 docker container and here is the stacktrace |
@johndoran I have strong feeling that attempt with 4.5.7 is not a cold start - it seems that during startup something requesting non-existing in this version component. Possible causes:
Please try cold start. Log for 5.4 looks strange and unhelpful, but I will also recommend to do cold start. This way we can determine - whether problem comes from state of data, or due to SQ+Docker. |
running with raw docker run -d --name sonarqube -p 9000:9000 -p 9092:9092 sonarqube |
I'm having this issue as well. Ever figure out what the problem was @johndoran ? |
Im having trouble starting my container. Im using the standard setup. Has anyone else seen this issue?
Appreciate any tips.
Using sonarqube/5.4 container
2016.04.13 16:59:41 WARN web[o.a.c.l.WebappClassLoaderBase] The web application [ROOT] appears to have started a thread named [Abandoned connection cleanup thread] 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.ref.ReferenceQueue.remove(ReferenceQueue.java:143)
com.mysql.jdbc.AbandonedConnectionCleanupThread.run(AbandonedConnectionCleanupThread.java:43)
2016.04.13 16:59:41 INFO web[o.a.c.h.Http11NioProtocol] Stopping ProtocolHandler ["http-nio-0.0.0.0-9000"]
2016.04.13 16:59:42 INFO web[o.a.c.h.Http11NioProtocol] Destroying ProtocolHandler ["http-nio-0.0.0.0-9000"]
2016.04.13 16:59:42 INFO web[o.s.s.a.TomcatAccessLog] Web server is stopped
2016.04.13 16:59:42 INFO app[o.s.p.m.Monitor] Process[web] is stopped
2016.04.13 16:59:42 INFO app[o.s.p.m.Monitor] Process[search] is stopping
The text was updated successfully, but these errors were encountered: