Detected parallel usage of another jsreport instance with the same license key?
-
Hi all, been using JSReport for the past year.
Recently upgraded to version 3.3 which was great, however, now I am getting "Detected parallel usage of another jsreport instance with the same license key" on both prod and dev instance (1 each, no where else).
Running this in azure as app service (can this be the bug?), this is my config.
[
{
"name": "chrome_numberOfWorkers",
"value": "4",
"slotSetting": false
},
{
"name": "chrome_strategy",
"value": "chrome-pool",
"slotSetting": false
},
{
"name": "chrome_timeout",
"value": "90000",
"slotSetting": false
},
{
"name": "DOCKER_REGISTRY_SERVER_PASSWORD",
"value": "docker password",
"slotSetting": false
},
{
"name": "DOCKER_REGISTRY_SERVER_URL",
"value": "https://index.docker.io/v1",
"slotSetting": false
},
{
"name": "DOCKER_REGISTRY_SERVER_USERNAME",
"value": "docker username",
"slotSetting": false
},
{
"name": "extensions_fsStore_persistence_provider",
"value": "azure-storage",
"slotSetting": false
},
{
"name": "extensions_fsStoreAzureSbSync_connectionString",
"value": "",
"slotSetting": false
},
{
"name": "extensions_fsStoreAzureStoragePersistence_accountKey",
"value": some key",
"slotSetting": false
},
{
"name": "extensions_fsStoreAzureStoragePersistence_accountName",
"value": "relab",
"slotSetting": false
},
{
"name": "licenseKey",
"value": "jsreport license",
"slotSetting": false
},
{
"name": "logger_console_level",
"value": "debug",
"slotSetting": false
},
{
"name": "logger_console_transport",
"value": "console",
"slotSetting": false
},
{
"name": "templatingEngines_numberOfWorkers",
"value": "4",
"slotSetting": false
},
{
"name": "templatingEngines_strategy",
"value": "http-server",
"slotSetting": false
},
{
"name": "WEBSITE_HTTPLOGGING_RETENTION_DAYS",
"value": "7",
"slotSetting": false
},
{
"name": "WEBSITES_ENABLE_APP_SERVICE_STORAGE",
"value": "false",
"slotSetting": false
}
]
-
You have to add the property values
"license": { "development": true }to your jsreport.config.json or similar file. It's explained in the v3 migration guide under "licensing development mode". https://jsreport.net/learn/v3-migration-guideThat should eliminate that message.