I am on Appian 19.3. When starting up Tomcat, I am getting the following error. What could be the issue and how should I go about resolving this?
2019-11-14 11:07:58,320 [localhost-startStop-1] INFO com.appiancorp.rdbms.hb.DataSourceManagerHbImpl - [jdbc/AppianPrimaryDS] Checking schema and migrating if necessary (appian/db/changelog/db-changelog-master.xml)...2019-11-14 11:12:59,379 [localhost-startStop-1] INFO com.appian.dl.repo.es.client.TransportClientManager - Shutting down client.2019-11-14 11:12:59,386 [localhost-startStop-1] ERROR org.springframework.web.context.ContextLoader - Context initialization failedorg.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.security.filterChains': Cannot resolve reference to bean 'org.springframework.security.web.DefaultSecurityFilterChain#58' while setting bean property 'sourceList' with key [58]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.security.web.DefaultSecurityFilterChain#58': Cannot resolve reference to bean 'mobileClientValidationFilter' while setting constructor argument with key [0]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mobileClientValidationFilter' defined in ServletContext resource [/WEB-INF/conf/security/spring-security-05-web-api.xml]: Cannot resolve reference to bean 'httpBasicAuthenticationEntryPoint' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'httpBasicAuthenticationEntryPoint' defined in ServletContext resource [/WEB-INF/conf/security/spring-security-05-web-api.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.appiancorp.security.auth.HttpBasicAuthenticationEntryPoint]: Constructor threw exception; nested exception is org.springframework.transaction.CannotCreateTransactionException: Could not open JPA EntityManager for transaction; nested exception is java.lang.IllegalStateException: [jdbc/AppianPrimaryDS] Error during schema migration.
Discussion posts and replies are publicly visible
This likely means that you are failing to connect to the database. I'd revisit your Appian Primary database connection information.
Yes, somewhat related to database. I think the services were not properly shutdown properly previously, thereby causing errors to one of the database lock tables. I have resolved it by following the instructions here: https://community.appian.com/support/w/kb/249/kb-1024-could-not-acquire-change-log-lock-currently-locked-by-user-error-thrown-during-application-server-startup
Hi Edmund,
Can you help what to do when we are getting this type of error.
Reason: liquibase.exception.DatabaseException: ORA-00955: name is already used by an existing object [Failed SQL: CREATE TABLE QABPM4.record_list_action_cfg (id NUMBER(19, 0) NOT NULL, uuid VARCHAR2(255) NOT NULL, record_type_id NUMBER(19, 0) NOT NULL, target_type VARCHAR2(255) NOT NULL, target_uuid VARCHAR2(255) NOT NULL, order_idx INTEGER NOT NULL, title CLOB, title_src NUMBER(3), description CLOB, description_src NUMBER(3), icon_id VARCHAR2(255) NOT NULL, visibility_expr CLOB NOT NULL, CONSTRAINT PK_RECORD_LIST_ACTION_CFG PRIMARY KEY (id))] at com.appiancorp.rdbms.common.schema.SchemaMigrator.migrate(SchemaMigrator.java:178) at com.appiancorp.rdbms.hb.DataSourceManagerHbImpl.migrateSchema(DataSourceManagerHbImpl.java:679) ... 113 moreCaused by: liquibase.exception.MigrationFailedException: Migration failed for change set db-changelog-000160-record-list-actions-table.xml::000160.1.0::appian:
Sounds like a liquibase issue, where it is attempting to create QABPM4.record_list_action_cfg but failed because it already exists. You might want to consult the Liquibase documentation instead.