[TK-281] scheduler service throws error during shutdown if it wasn't initialized properly Created: 2015/09/15  Updated: 2018/03/30

Status: Accepted
Project: Trapperkeeper
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Chris Price Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: low-hanging-fruit, server
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Team: Server

 Description   

There is some logic in the stop function of the scheduler service that assumes that "pool" and "jobs" have been initialized in the context. If they haven't, it will throw an NPE.

We saw this in an acceptance test failure, where a SIGINT was sent to the server while it was still initializing the app, and this caused the shutdown sequence to start.

http://jenkins-enterprise.delivery.puppetlabs.net/view/pe-puppet-server-extensions/job/enterprise_pe-puppet-server-extensions_integration-system_smoke-master/10/LAYOUT=64mdca,LDAP_TYPE=default,PLATFORM=centos7,label=beaker/consoleFull



 Comments   
Comment by Kevin Corcoran [ 2016/02/24 ]

https://github.com/puppetlabs/trapperkeeper-scheduler

Generated at Mon Dec 09 13:45:43 PST 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.