System becomes uninitialized upon Tomcat restart

[PeccatorImpius]

I am running service-1.1.war from master in Tomcat 6.0.36. Everything works great until I have to restart Tomcat. After restarting Tomcat, troia seems to become uninitialized. Commands return the following error:

{"timestamp":"2013-05-09T16:59:37.742-07:00","status":"NOT_INITIALIZED","deploy_time":"2013-05-09T16:55:32.270-07:00"}

If I go to the config page and click Submit, everything starts working. But I shouldn't need to do that every time Tomcat restarts, should I?

[kkonrad]

This is a result of our goal to make it possible to run many instances of Troia on the same machine with different configurations. Problem is that all of those instances at start would look for settings in the same places (the same code) ...
About few days ago we were thinking about adding options in troia.properties which would tell whether settings in this file should be loaded at start and frozen. Unfortunately this file needs to be modified before generating a war file. Despite that, I think it should work in your case.
Currently when we work on Troia we are using scripts to (un)deploy Troia, which makes POST request using curl in order to set it to our local settings.

For now we will implement this solution with troia.properties, but we will think about better way of doing this.

[PeccatorImpius]

Ok, thanks. I am looking forward to geting the troia.properties solution.

[PeccatorImpius]

What POST request in your scripts do you use to set the local settings?

curl -X POST -d "" "http://localhost:8080/service-1.1/config"

You can set your settings after -d, between " chars. For ex.:

curl -X POST -d "CACHE_SIZE=10&CACHE_DUMP_TIME=500" "http://localhost:8080/service-1.1/config"

[PeccatorImpius]

Thanks. Here is what we ended up using:

curl -X POST -d "CACHE_DUMP_TIME=600&CACHE_SIZE=15&DB_DRIVER_CLASS=com.mysql.jdbc.Driver&DB_NAME=Troia&DB_PASSWORD=root&DB_URL=jdbc:mysql://localhost/&DB_USER=root&DOWNLOADS_PATH=/tmp/&EXECUTOR_THREADS_NUM=10&JOBS_STORAGE=DB&MEMCACHE_EXPIRATION_TIME=3600&MEMCACHE_PORT=11211&MEMCACHE_URL=localhost&RESPONSES_CACHE_SIZE=200&RESPONSES_DUMP_TIME=86400" "http://localhost:8080/service-1.1/config"

[kkonrad]

Now at deploy Troia loads settings from troia.properties (available in .war file). Default settings were changed so that it will work purely in memory (no persistence). We have also added option to settings to *freeze them after loading so that no one will be able to modify.
To sum up: when you build your war package you can modify default configuration which will be loaded after deploy.

[PeccatorImpius]

Which commit do I need to pull for this?

Well, there were a few commits related with this issue. Just take the latest version from master branch. You've got two options:

1. change troia.properties and build your own war file. After deploying/restarting tomcat settings would load automatically and all should work (if settings are correct).
2. download war file from http://project-troia.com/media/downloads/service.war or build it without changing troia.properties. As Konrad mentioned, default settings will make troia to work purely in memory. You can of course change them by submiting the form on /config page, or by using curl.

It is important to mention that JOB_STORAGE option has changed its available values to: MEMORY_FULL, MEMORY_KV, DB_FULL, DB_KV_MEMCACHE_SIMPLE or DB_KV_SIMPLE. DB_FULL is earlier DB option and it is recommended one if we care about persistance.

[PeccatorImpius]

Here is my properties file:

$ cat service/src/main/resources/troia.properties
DB_USER = root
DB_PASSWORD = root
DB_NAME = Troia
DB_URL = jdbc:mysql://localhost/
DB_DRIVER_CLASS = com.mysql.jdbc.Driver
DOWNLOADS_PATH = /tmp/
CACHE_SIZE = 15
CACHE_DUMP_TIME = 600
RESPONSES_CACHE_SIZE = 200
RESPONSES_DUMP_TIME = 86400
EXECUTOR_THREADS_NUM = 10
JOBS_STORAGE = DB_FULL
MEMCACHE_URL = localhost
MEMCACHE_PORT = 11211
MEMCACHE_EXPIRATION_TIME = 3600
FREEZE_CONFIGURATION_AT_START = false

but when I try communicate with the server I get:

{"timestamp":"2013-05-21T18:05:54.673-07:00","status":"NOT_INITIALIZED","deploy_time":"2013-05-21T17:54:18.544-07:00"}

[PeccatorImpius]

Actually, I think I had a stale deploy. It works now. :-) Thanks!