Skip to content
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

"JVM is terminating. Shutting down Winstone" #34

Closed
adriaanm opened this issue Feb 17, 2015 · 5 comments
Closed

"JVM is terminating. Shutting down Winstone" #34

adriaanm opened this issue Feb 17, 2015 · 5 comments

Comments

@adriaanm
Copy link
Contributor

This job just stopped with no apparent reason.

The log on jenkins-master says:

Feb 16 18:05:07 ip-172-31-2-59 [jenkins]: INFO: JVM is terminating. Shutting down Winstone
@adriaanm
Copy link
Contributor Author

@adriaanm
Copy link
Contributor Author

We already run under

cd /var/lib/jenkins
touch jenkins.start
exec chpst -u jenkins -U jenkins \
  env HOME=/var/lib/jenkins \
  JENKINS_HOME=/var/lib/jenkins \
  java -server -Xmx4G -XX:MaxPermSize=512M -XX:+HeapDumpOnOutOfMemoryError -jar jenkins.war \
  --httpPort=8080 \
  --httpListenAddress=127.0.0.1 \

and no hprof memory dumps were found. CPU usage was much higher than usual according to EC2 monitoring, but that's all I have...

@som-snytt
Copy link

Maybe it's terminated from a browser console due to a javascript bug. Or a Jenkins virus!

@retronym
Copy link
Member

That message is logged in a JVM shutdown hook

If we keep seeing this, we could start that JVM with a custom java agent that logs a stack trace when System.exit is called. I can't think of a more straight forward way to diagnose this.

@adriaanm
Copy link
Contributor Author

adriaanm commented Jul 1, 2015

Closing because we haven't seen this since.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants