# Flowable Idm not working in AWS EC2 linux instance

**URL:** <https://forum.flowable.org/t/flowable-idm-not-working-in-aws-ec2-linux-instance/4467>\
**Category:** Flowable Application\
**Created:** [September 5, 2019, 3:13am UTC](https://forum.flowable.org/t/flowable-idm-not-working-in-aws-ec2-linux-instance/4467 "2019-09-05T03:13:41Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![harry](https://avatars.discourse-cdn.com/v4/letter/h/f6c823/32.png) [@harry](https://forum.flowable.org/u/harry)\
**Post date:** [September 5, 2019, 3:13am UTC](https://forum.flowable.org/t/flowable-idm-not-working-in-aws-ec2-linux-instance/4467/1 "2019-09-05T03:13:41Z")

</div>

Hello Guys,

I have setup flowable in AWS EC2 instance. Basically I have copied flowable idm war file in webapps folder and connected the properties file with RDS instance of AWS.

flowable schema and required tables are created in RDS.

after starting tomcat8 i get below error. Please help

Catalina log

* * *

05-Sep-2019 02:02:06.566 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [/var/lib/tomcat8/webapps/DB-idm.war]  
05-Sep-2019 02:03:24.715 SEVERE [localhost-startStop-1] org.apache.catalina.core.ContainerBase.addChildInternal ContainerBase.addChild: start:  
org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/DB-idm]]  
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167)  
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:754)  
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:730)  
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:744)  
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:980)  
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1851)  
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)  
at java.util.concurrent.FutureTask.run(FutureTask.java:266)  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)  
at java.lang.Thread.run(Thread.java:748)  
Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘securityConfiguration’: Unsatisfied dependency expressed through field ‘identityService’; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘idmIdentityService’ defined in class path resource [org/flowable/spring/boot/idm/IdmEngineServicesAutoConfiguration.class]: Unsatisfied dependency expressed through method ‘idmIdentityService’ parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘idmEngine’: FactoryBean threw exception on object creation; nested exception is org.springframework.transaction.CannotCreateTransactionException: Could not open JDBC Connection for transaction; nested exception is com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.  
at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:584)  
at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:90)  
at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:370)  
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1336)  
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:572)  
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:495)  
at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:317)  
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)  
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:315)  
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199)  
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:759)  
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867)  
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:548)  
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:142)  
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:754)  
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:386)  
at org.springframework.boot.SpringApplication.run(SpringApplication.java:307)  
at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.run(SpringBootServletInitializer.java:157)  
at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.createRootApplicationContext(SpringBootServletInitializer.java:137)  
at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.onStartup(SpringBootServletInitializer.java:91)  
at org.springframework.web.SpringServletContainerInitializer.onStartup(SpringServletContainerInitializer.java:172)  
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5225)  
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)  
… 10 more  
Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘idmIdentityService’ defined in class path resource [org/flowable/spring/boot/idm/IdmEngineServicesAutoConfiguration.class]: Unsatisfied dependency expressed through method ‘idmIdentityService’ parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘idmEngine’: FactoryBean threw exception on object creation; nested exception is org.springframework.transaction.CannotCreateTransactionException: Could not open JDBC Connection for transaction; nested exception is com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.  
at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:733)  
at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:475)  
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1246)  
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1096)  
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:535)  
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:495)  
at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:317)  
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)  
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:315)  
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199)  
at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:251)  
at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1135)  
at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1062)  
at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:581)  
… 32 more  
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘idmEngine’: FactoryBean threw exception on object creation; nested exception is org.springframework.transaction.CannotCreateTransactionException: Could not open JDBC Connection for transaction; nested exception is com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.  
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:178)  
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:101)  
at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1654)  
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.getObjectForBeanInstance(AbstractAutowireCapableBeanFactory.java:1174)  
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:327)  
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199)  
at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:251)  
at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1135)  
at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1062)  
at org.springframework.beans.factory.support.ConstructorResolver.resolveAutowiredArgument(ConstructorResolver.java:819)  
at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:725)  
… 45 more  
Caused by: org.springframework.transaction.CannotCreateTransactionException: Could not open JDBC Connection for transaction; nested exception is com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.  
at org.springframework.jdbc.datasource.DataSourceTransactionManager.doBegin(DataSourceTransactionManager.java:305)  
at org.springframework.transaction.support.AbstractPlatformTransactionManager.getTransaction(AbstractPlatformTransactionManager.java:378)  
at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:137)  
at org.flowable.idm.spring.SpringTransactionInterceptor.execute(SpringTransactionInterceptor.java:46)  
at org.flowable.common.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:30)  
at org.flowable.common.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:56)  
at org.flowable.idm.engine.impl.IdmEngineImpl.(IdmEngineImpl.java:45)  
at org.flowable.idm.engine.IdmEngineConfiguration.buildIdmEngine(IdmEngineConfiguration.java:166)  
at org.flowable.idm.spring.SpringIdmEngineConfiguration.buildIdmEngine(SpringIdmEngineConfiguration.java:48)  
at org.flowable.idm.spring.IdmEngineFactoryBean.getObject(IdmEngineFactoryBean.java:58)  
at org.flowable.idm.spring.IdmEngineFactoryBean.getObject(IdmEngineFactoryBean.java:31)  
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:171)  
… 55 more  
Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.  
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)  
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)  
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)  
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)  
at com.mysql.jdbc.Util.handleNewInstance(Util.java:425)  
at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:990)  
at com.mysql.jdbc.MysqlIO.(MysqlIO.java:342)  
at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2188)  
at com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2221)  
at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2016)  
at com.mysql.jdbc.ConnectionImpl.(ConnectionImpl.java:776)  
at com.mysql.jdbc.JDBC4Connection.(JDBC4Connection.java:47)  
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)  
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)  
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)  
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)  
at com.mysql.jdbc.Util.handleNewInstance(Util.java:425)  
at com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:386)  
at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:330)  
at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:117)  
at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:123)  
at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:365)  
at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:194)  
at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:460)  
at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:534)  
at com.zaxxer.hikari.pool.HikariPool.(HikariPool.java:115)  
at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:112)  
at org.springframework.jdbc.datasource.DataSourceTransactionManager.doBegin(DataSourceTransactionManager.java:262)  
… 66 more  
Caused by: java.net.SocketTimeoutException: connect timed out  
at java.net.PlainSocketImpl.socketConnect(Native Method)  
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)  
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)  
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)  
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)  
at java.net.Socket.connect(Socket.java:589)  
at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:211)  
at com.mysql.jdbc.MysqlIO.(MysqlIO.java:301)  
… 87 more  
05-Sep-2019 02:03:24.717 SEVERE [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Error deploying web application archive [/var/lib/tomcat8/webapps/DB-idm.war]  
java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/DB-idm]

* * *

I have renamed flowable-idm war to DB-idm war. Below is the propeerties file.

server.port=80  
server.servlet.context-path=/DB-idm  
management.endpoints.jmx.unique-names=true

# This is needed to force use of JDK proxies instead of using CGLIB

spring.aop.proxy-target-class=false  
spring.aop.auto=false  
spring.application.name=flowable-ui-idm  
spring.banner.location=classpath:/org/flowable/spring/boot/flowable-banner.txt

# The default domain for generating ObjectNames must be specified. Otherwise when multiple Spring Boot applications start in the same servlet container

# all would be created with the same name (com.zaxxer.hikari:name=dataSource,type=HikariDataSource) for example

spring.jmx.default-domain=${spring.application.name}

# Expose all actuator endpoints to the web

# They are exposed, but only authenticated users can see /info and /health abd users with access-admin can see the others

management.endpoints.web.exposure.include=\*

# Full health details should only be displayed when a user is authorized

management.endpoint.health.show-details=when\_authorized

# Only users with role access-admin can access full health details

management.endpoint.health.roles=access-admin

# Spring prefixes the roles with ROLE\_. However, Flowable does not have that concept yet, so we need to override that with an empty string

flowable.common.app.role-prefix=

# 

# SECURITY

# 

flowable.idm.app.security.remember-me-key=testkey

#flowable.idm.password-encoder=spring\_bcrypt  
spring.security.filter.dispatcher-types=REQUEST,FORWARD,ASYNC

# 

# DATABASE

# 

#spring.datasource.driver-class-name=org.h2.Driver  
#spring.datasource.url=jdbc:h2:~/flowable-db/db;AUTO\_SERVER=TRUE;AUTO\_SERVER\_PORT=9091;DB\_CLOSE\_DELAY=-1

#spring.datasource.driver-class-name=com.mysql.jdbc.Driver  
#spring.datasource.url=jdbc:mysql://127.0.0.1:3306/flowable?characterEncoding=UTF-8

#spring.datasource.driver-class-name=org.postgresql.Driver  
#spring.datasource.url=jdbc:postgresql://localhost:5432/flowableidm

#spring.datasource.driver-class-name=com.microsoft.sqlserver.jdbc.SQLServerDriver  
#spring.datasource.url=jdbc:sqlserver://localhost:1433;databaseName=flowableidm

# datasource

#spring.datasource.driver-class-name=oracle.jdbc.driver.OracleDriver  
#spring.datasource.url=jdbc:oracle:thin:@localhost:1521:BOLTADVANCE  
#spring.datasource.username=SYSTEM  
#spring.datasource.password=\<\>  
spring.datasource.driver-class-name=com.mysql.jdbc.Driver  
spring.datasource.url=jdbc:mysql://decisionbox.clvlijauqazq.ap-south-1.rds.amazonaws.com:3306/flowable?characterEncoding=UTF-8  
spring.datasource.username=decisionbox  
spring.datasource.password=\<\>

# 10 minutes

spring.datasource.hikari.maxLifetime=600000

# 5 minutes

spring.datasource.hikari.idleTimeout=300000  
spring.datasource.hikari.minimumIdle=5  
spring.datasource.hikari.maximumPoolSize=50

# test query for H2, MySQL, PostgreSQL and Microsoft SQL Server

#spring.datasource.hikari.connection-test-query=select 1

# test query for Oracle

#spring.datasource.hikari.connection-test-query=SELECT 1 FROM DUAL

# test query for DB2

#spring.datasource.hikari.connection-test-query=SELECT current date FROM sysibm.sysdummy1

# 

# LDAP

# 

#flowable.idm.ldap.enabled=true  
#flowable.idm.ldap.server=ldap://localhost  
#flowable.idm.ldap.port=10389  
#flowable.idm.ldap.user=uid=admin, ou=system  
#flowable.idm.ldap.password=secret  
#flowable.idm.ldap.base-dn=o=flowable  
#flowable.idm.ldap.query.user-by-id=(&(objectClass=inetOrgPerson)(uid={0}))  
#flowable.idm.ldap.query.user-by-full-name-like=(&(objectClass=inetOrgPerson)(|({0}=_{1}_)({2}=_{3}_)))  
#flowable.idm.ldap.query.all-users=(objectClass=inetOrgPerson)  
#flowable.idm.ldap.query.groups-for-user=(&(objectClass=groupOfUniqueNames)(uniqueMember={0}))  
#flowable.idm.ldap.query.all-groups=(objectClass=groupOfUniqueNames)  
#flowable.idm.ldap.query.group-by-id=(&(objectClass=groupOfUniqueNames)(uniqueId={0}))  
#flowable.idm.ldap.attribute.user-id=uid  
#flowable.idm.ldap.attribute.first-name=cn  
#flowable.idm.ldap.attribute.last-name=sn  
#flowable.idm.ldap.attribute.email=mail  
#flowable.idm.ldap.attribute.group-id=cn  
#flowable.idm.ldap.attribute.group-name=cn  
#flowable.idm.ldap.cache.group-size=10000  
#flowable.idm.ldap.cache.group-expiration=180000

# 

# DEFAULT ADMINISTRATOR ACCOUNT

# 

flowable.idm.app.admin.user-id=admin  
flowable.idm.app.admin.password=test  
flowable.idm.app.admin.first-name=Test  
flowable.idm.app.admin.last-name=Administrator  
[flowable.idm.app.admin.email=admin@flowable.org](mailto:flowable.idm.app.admin.email=admin@flowable.org)

# Rest api in IDM app

flowable.idm.app.rest-enabled=true

# Configures the way user credentials are verified when doing a REST API call:

# ‘any-user’ : the user needs to exist and the password need to match. Any user is allowed to do the call (this is the pre 6.3.0 behavior)

# ‘verify-privilege’ : the user needs to exist, the password needs to match and the user needs to have the ‘rest-api’ privilege

# If nothing set, defaults to ‘verify-privilege’

flowable.rest.app.authentication-mode=verify-privilege

---

<div class="post-metadata">

**Author:** ![joram](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/joram/32/26_2.png) [@joram](https://forum.flowable.org/u/joram)\
**Post date:** [September 10, 2019, 10:40am UTC](https://forum.flowable.org/t/flowable-idm-not-working-in-aws-ec2-linux-instance/4467/2 "2019-09-10T10:40:19Z")

</div>

> [@harry](#):
>
> Could not open JDBC Connection for transaction; nested exception is com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

The exception seems to indicate the EC2 server can’t access the RDS instance. To my knowledge, this typically means (if you’re sure about the connection details of the RDS instance and the fact it’s up and running) that the RDS instance is in a different security group or the security rules have not been configured in such a way that both instances can see each other.

---

<div class="post-metadata">

**Author:** ![harry](https://avatars.discourse-cdn.com/v4/letter/h/f6c823/32.png) [@harry](https://forum.flowable.org/u/harry)\
**Post date:** [September 16, 2019, 6:02pm UTC](https://forum.flowable.org/t/flowable-idm-not-working-in-aws-ec2-linux-instance/4467/3 "2019-09-16T18:02:15Z")

</div>

Hi Joram,

Thanks for the response. But I am able to connect RDS mysql from EC2 linux instance. Doesn’t seem to be connection issue between EC2 linux and RDS instance.

Below are the connection details. I am getting error only when connecting through flowable.

[ec2-user@ip-172-31-36-78 bin]$ mysql -h \<\> -P 3306 -u \<\> -p  
Enter password:  
Welcome to the MySQL monitor. Commands end with ; or \g.  
Your MySQL connection id is 10385  
Server version: 5.7.26-log Source distribution

Copyright © 2000, 2018, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its  
affiliates. Other names may be trademarks of their respective  
owners.

Type ‘help;’ or ‘\h’ for help. Type ‘\c’ to clear the current input statement.

mysql\> USE flowable;  
Reading table information for completion of table and column names  
You can turn off this feature to get a quicker startup with -A

Database changed  
mysql\> select \* from act\_id\_user;  
ERROR 1146 (42S02): Table ‘flowable.act\_id\_user’ doesn’t exist  
mysql\> select \* from ACT\_ID\_USER;  
±--------±-----±--------±--------------±--------------±-------------------±-----±------------±-----------+  
| ID\_ | REV\_ | FIRST\_ | LAST\_ | DISPLAY\_NAME\_ | EMAIL\_ | PWD\_ | PICTURE\_ID\_ | TENANT\_ID\_ |  
±--------±-----±--------±--------------±--------------±-------------------±-----±------------±-----------+  
| admin | 1 | Test | Administrator | NULL | [admin@flowable.org](mailto:admin@flowable.org) | test | NULL | NULL |  
±--------±-----±--------±--------------±--------------±-------------------±-----±------------±-----------+  
4 rows in set (0.01 sec)

---

<div class="post-metadata">

**Author:** ![joram](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/joram/32/26_2.png) [@joram](https://forum.flowable.org/u/joram)\
**Post date:** [September 17, 2019, 8:33am UTC](https://forum.flowable.org/t/flowable-idm-not-working-in-aws-ec2-linux-instance/4467/4 "2019-09-17T08:33:28Z")

</div>

Not sure why it can’t communicate it in that case. If I do a search on that error + EC2/RDS it all seems to point in the direction of security groups (e.g. [https://stackoverflow.com/questions/46311096/unable-to-establish-connection-to-jdbcmysql-communication-link-failure](https://stackoverflow.com/questions/46311096/unable-to-establish-connection-to-jdbcmysql-communication-link-failure)). Can you maybe try open up the security group completely for a moment (don’t forget to set it back afterwards) and try to boot it up again?

---

<div class="post-metadata">

**Author:** ![harry](https://avatars.discourse-cdn.com/v4/letter/h/f6c823/32.png) [@harry](https://forum.flowable.org/u/harry)\
**Post date:** [September 18, 2019, 8:02pm UTC](https://forum.flowable.org/t/flowable-idm-not-working-in-aws-ec2-linux-instance/4467/5 "2019-09-18T20:02:17Z")

</div>

Hi Joram,

I am not getting any communication link failure now. But, I am getting below. Please help.

org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/flowable-idm]]  
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167)  
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:754)  
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:730)  
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:744)  
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:980)  
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1851)  
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)  
at java.util.concurrent.FutureTask.run(FutureTask.java:266)  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)  
at java.lang.Thread.run(Thread.java:748)  
Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘bootstrapper’: Unsatisfied dependency expressed through field ‘identityService’; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘idmIdentityService’ defined in class path resource [org/flowable/spring/boot/idm/IdmEngineServicesAutoConfiguration.class]: Unsatisfied dependency expressed through method ‘idmIdentityService’ parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘idmEngine’: FactoryBean threw exception on object creation; nested exception is org.flowable.common.engine.api.FlowableException: couldn’t create db schema: create table ACT\_ID\_PROPERTY (  
NAME\_ varchar(64),  
VALUE\_ varchar(300),  
REV\_ integer,  
primary key (NAME\_)  
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE utf8\_bin

---

<div class="post-metadata">

**Author:** ![harry](https://avatars.discourse-cdn.com/v4/letter/h/f6c823/32.png) [@harry](https://forum.flowable.org/u/harry)\
**Post date:** [September 29, 2019, 4:38am UTC](https://forum.flowable.org/t/flowable-idm-not-working-in-aws-ec2-linux-instance/4467/6 "2019-09-29T04:38:15Z")

</div>

Hi Joram,

The issue is resolved. I will post the steps and solution here.

1. place flowable wars (admin, task, modeler) in tomcat-\>webapps folder

2. To change the connection to RDS my sql, enter the below connection string in the flowable-default.properties file available in the WEB-INF-\> classes folder

spring.datasource.driver-class-name=com.mysql.jdbc.Driver  
spring.datasource.url=jdbc:mysql://\<\>:3306/flowable?characterEncoding=UTF-8  
spring.datasource.username=username  
spring.datasource.password=password

1. Place mysql connector jar in the lib folder of tomcat and in the lib folder of individual war (task, modeler, idm, etc). Make sure the version of mysql connector jar is same in both the places.

2. Install mysql client in EC2 instance.

3. Make sure appropriate permission is given to mysql and tomcat folders/directories.

4. Make sure inbound rules in EC2 of the security group select allow traffic from all ips.

5. Find the mysql installatoin in your ec2 instance with command whereis mysql. Navigate to usr/bin folder

6. Connect to mysql. Follow the steps in the below url

> **[How to reset MySQL root password (even if you've forgotten it)](http://techgenix.com/reset-mysql-root-password-forgotten/)**
>
> You've forgotten your MySQL root password? Whether you're on EC2 or on a Ubuntu, Fedora, or other server, we've got you covered.

---

<div class="post-metadata">

**Author:** ![joram](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/joram/32/26_2.png) [@joram](https://forum.flowable.org/u/joram)\
**Post date:** [October 2, 2019, 8:52am UTC](https://forum.flowable.org/t/flowable-idm-not-working-in-aws-ec2-linux-instance/4467/7 "2019-10-02T08:52:36Z")

</div>

Happy to hear you found the solution. Many thanks for posting the detailed steps!

Do you know which of the steps wasn’t working before?

---

<div class="post-metadata">

**Author:** ![harry](https://avatars.discourse-cdn.com/v4/letter/h/f6c823/32.png) [@harry](https://forum.flowable.org/u/harry)\
**Post date:** [October 2, 2019, 4:35pm UTC](https://forum.flowable.org/t/flowable-idm-not-working-in-aws-ec2-linux-instance/4467/8 "2019-10-02T16:35:40Z")

</div>

Hi Joram,

It was step no. 8.