niveathika
commented
5 years ago @Malintha1996 This is the expected behaviour since we expect a healthy database connection for the server to start. We will recover if the database goes down and starts during the run time. However, it should be healthy when the server starts. This is mandatory for databases needed for server functioning such as persistence db, permission db etc.
In your case, since this is a database used for testing in the siddhi app and you want to initialise even if the database cannot be connected you can set initializationFailTimeout=-1 for this specific data source only. Please not, this database needs to be active when you start the siddhi app.
# Datasource Configurations
dataSources:
- name: Customers
description: The datasource used for registry and user manager
definition:
type: RDBMS
configuration:
jdbcUrl: 'jdbc:mysql://localhost:3306/Customers?useSSL=false'
username: testuser
password: test
driverClassName: com.mysql.jdbc.Driver
maxPoolSize: 10
idleTimeout: 60000
connectionTestQuery: SELECT 1
validationTimeout: 30000
isAutoCommit: false
initializationFailTimeout: -1
malinthar
Description: I have few siddhi files which use rdms:cud and rdbms:query operations in the workspace folder. When I tried to start the editor when the mysql server is down,tooling fails to start.Following is the stack trace printed
I had configured the {Distribution_Home}/conf/deployment.yaml file to add the DataSource as following.
When the Customers dataSource configuration is removed, editor started to work properly.
Affected Product Version: v5.1.0-RC1 OS, DB, other environment details and versions:
OS-Windows Steps to reproduce: Deploy a siddhi file which uses rdbms:cud or rdbms:query operations