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

REST API /engine/start v1.9.0 breaks when starting a started tenant. #102

nmarus opened this Issue May 17, 2017 · 2 comments


None yet
2 participants

nmarus commented May 17, 2017

This only happens when sending the REST API call to start a tenant that is already started, I get the following response:

{"taskName":"START TENANT 'Test1'","totalOperations":14,"currentOperation":1,"message":"Preparing tenant"}
{"taskName":"START TENANT 'Test1'","totalOperations":14,"currentOperation":2,"message":"Starting tenant Groovy script engine"}
{"taskName":"START TENANT 'Test1'","totalOperations":14,"currentOperation":3,"message":"Starting asset management cache provider"}
{"taskName":"START TENANT 'Test1'","totalOperations":14,"currentOperation":4,"message":"Starting asset management"}
{"taskName":"START TENANT 'Test1'","totalOperations":14,"currentOperation":5,"message":"Starting device management cache provider"}
{"taskName":"START TENANT 'Test1'","totalOperations":14,"currentOperation":6,"message":"Starting device management"}
{"taskName":"START TENANT 'Test1'","totalOperations":14,"currentOperation":7,"message":"Starting device event management"}
{"taskName":"START TENANT 'Test1'","totalOperations":14,"currentOperation":8,"message":"Starting schedule management"}
{"taskName":"START TENANT 'Test1'","totalOperations":14,"currentOperation":9,"message":"Starting asset module manager"}
{"taskName":"START TENANT 'Test1'","totalOperations":14,"currentOperation":10,"message":"Starting search provider manager"}
{"taskName":"START TENANT 'Test1'","totalOperations":14,"currentOperation":11,"message":"Starting event processing subsystem"}
{"taskName":"START TENANT 'Test1'","totalOperations":14,"currentOperation":12,"message":"Starting device communication subsystem"}
{"taskName":"START TENANT 'Test1'","totalOperations":14,"currentOperation":13,"message":"Starting schedule manager"}
{"result":"Failed","message":"java.lang.RuntimeException: Unable to create Quartz scheduler for schedule manager."}

However, the tenant goes into a state of 'error' and I can no longer start this or ANY new tenants without rebooting/restarting sitewhere.

Everything works fine if the tenant is stopped when attempting to start it.

I am working around this by first checking if a tenant is started before sending a start, but wanted to let you know that this happens under these circumstances.


This comment has been minimized.


derekadams commented May 17, 2017

Thanks for reporting the issue. We are about to release 1.10.0 and there is a chance it's fixed in there because we refactored some of the tenant lifecycle code. If not, we will schedule a fix for the 1.11.0 release. Sorry for the inconvenience!

@derekadams derekadams self-assigned this May 17, 2017

@derekadams derekadams added the bug label May 17, 2017


This comment has been minimized.

nmarus commented May 17, 2017

No worries. Easy workaround. Excited to play with 1.10 when you guys release. Loving this project. Great work!

@derekadams derekadams added this to the 1.11.0 milestone Jun 2, 2017

derekadams added a commit that referenced this issue Jun 15, 2017

@derekadams derekadams closed this Jun 15, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment