I configured the config.json as follows
{
"ws_servers": [{
"host": "ec2-52-11-105-39.us-west-2.compute.amazonaws.com",
"port": 80
}],
"appKey": "3e871ea6-6f67-42ce-a6f0-4b2d041006f2",
"logger": {
"level":"DEBUG"
},
// Connection parameters
"ws_connection": {
"encryption": "none", // Defaults to ssl
"verbose": true
},
// Certificate settings
// NOTE: Only certificates signed with the MD5 or SHA1 hash functions will be accepted
"certificates": {
"validate": false, // Boolean. Set to false to turn off certificate validation. Default = true.
"verbose": true
}
}
Then running as follows (nothing happens). Second time when I run it doesn't even display "Starting up..."
D:\apps\MicroServer>D:\apps\MicroServer\wsems.exe -cfg D:\apps\MicroServer\etc\config.json
[INFO ] 2015-07-09 22:57:20,792 D:\apps\MicroServer\wsems.exe: Using config file: D:\apps\MicroServer\etc\config.json
[FORCE] 2015-07-09 22:57:20,792 D:\apps\MicroServer\wsems.exe: Starting up ....
D:\apps\MicroServer>
D:\apps\MicroServer>D:\apps\MicroServer\wsems.exe -cfg D:\apps\MicroServer\etc\config.json
[INFO ] 2015-07-09 23:00:04,984 D:\apps\MicroServer\wsems.exe: Using config file: D:\apps\MicroServer\etc\config.json
Not sure what is wrong? I tried with -loglevel TRACE but no additional output. Any help in debugging this will help.
Thanks and Regards
The issue was the comments embedded in the file. System did not like those comments. Removing them solved my problem. I hope it is documented somewhere.
Thanks,
Varathan
Correct, the config.json file has to be pure JSON which doesn't support comments.