Tomcat start up problem in L3 workshop

Question

First time starting up Tomcat in the workshop, it times out with the error in bold below:

Also in the cmd window, I see:

D:\PhotonUser>2024-11-28 18:06:41.277 UTC [6728] **FATAL:  role "jics" does not exist**
2024-11-28 18:06:43.234 UTC [4136] **FATAL:  role "bluesam" does not exist**

I can't see any mention for these roles in the installation instructions.

Can anyone help me please?
 _____ _                                   _____                       _         ___      _           _       
| ___ \ |                                 /  __ \                     | |       / _ \    | |         (_)      
| |_/ / |_   _  ___  ___  __ _ _ __ ___   | /  \/ ___  _ __  ___  ___ | | ___  / /_\ \ __| |_ __ ___  _ _ __  
| ___ \ | | | |/ _ \/ __|/ _` | '_ ` _ \  | |    / _ \| '_ \/ __|/ _ \| |/ _ \ |  _  |/ _` | '_ ` _ \| | '_ \ 
| |_/ / | |_| |  __/\__ \ (_| | | | | | | | \__/\ (_) | | | \__ \ (_) | |  __/ | | | | (_| | | | | | | | | | |
\____/|_|\__,_|\___||___/\__,_|_| |_| |_|  \____/\___/|_| |_|___/\___/|_|\___| \_| |_/\__,_|_| |_| |_|_|_| |_|

2024-11-28T18:06:19.399Z  INFO 7248 --- [           main] c.n.b.b.a.BACApplicationLauncher         : The following 2 profiles are active: "main", "bac"
2024-11-28T18:06:21.609Z  INFO 7248 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Multiple Spring Data modules found, entering strict repository configuration mode
2024-11-28T18:06:21.609Z  INFO 7248 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFAULT mode.
2024-11-28T18:06:22.781Z  INFO 7248 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 1142 ms. Found 1 JPA repository interface.
2024-11-28T18:06:23.445Z  INFO 7248 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Multiple Spring Data modules found, entering strict repository configuration mode
2024-11-28T18:06:23.453Z  INFO 7248 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data Redis repositories in DEFAULT mode.
2024-11-28T18:06:23.507Z  INFO 7248 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 19 ms. Found 0 Redis repository interfaces.
2024-11-28T18:06:24.378Z  INFO 7248 --- [           main] o.s.cloud.context.scope.GenericScope     : BeanFactory id=391f7e5e-d139-381b-ad8a-811b84939d7e
2024-11-28T18:06:24.897Z  INFO 7248 --- [           main] o.a.c.c.C.[Catalina].[localhost].[/bac]  : Initializing Spring embedded WebApplicationContext
2024-11-28T18:06:24.898Z  INFO 7248 --- [           main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 5438 ms
2024-11-28T18:06:25.087Z  INFO 7248 --- [           main] c.n.bluage.bac.application.WebConfig     : Setting max upload size to 5120MB
2024-11-28T18:06:25.618Z  INFO 7248 --- [           main] o.hibernate.jpa.internal.util.LogHelper  : HHH000204: Processing PersistenceUnitInfo [name: default]
2024-11-28T18:06:25.897Z  INFO 7248 --- [           main] org.hibernate.Version                    : HHH000412: Hibernate ORM core version 6.4.4.Final
2024-11-28T18:06:26.022Z  INFO 7248 --- [           main] o.h.c.internal.RegionFactoryInitiator    : HHH000026: Second-level cache disabled
2024-11-28T18:06:26.811Z  INFO 7248 --- [           main] o.s.o.j.p.SpringPersistenceUnitInfo      : No LoadTimeWeaver setup: ignoring JPA class transformer
2024-11-28T18:06:26.921Z  WARN 7248 --- [           main] org.hibernate.orm.deprecation            : HHH90000025: PostgreSQLDialect does not need to be specified explicitly using 'hibernate.dialect' (remove the property setting and it will be selected by default)
2024-11-28T18:06:29.865Z  INFO 7248 --- [           main] o.h.e.t.j.p.i.JtaPlatformInitiator       : HHH000489: No JTA platform available (set 'hibernate.transaction.jta.platform' to enable JTA platform integration)
2024-11-28T18:06:29.933Z  INFO 7248 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Starting...
2024-11-28T18:06:30.632Z  INFO 7248 --- [           main] com.zaxxer.hikari.pool.PoolBase          : HikariPool-1 - Driver does not support get/set network timeout for connections. (feature not supported)
2024-11-28T18:06:30.634Z  INFO 7248 --- [           main] com.zaxxer.hikari.pool.HikariPool        : HikariPool-1 - Added connection org.hsqldb.jdbc.JDBCConnection@7e84be9b
2024-11-28T18:06:30.646Z  INFO 7248 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Start completed.
**2024-11-28T18:06:30.803Z  WARN 7248 --- [           main] o.h.t.s.i.ExceptionHandlerLoggedImpl     : GenerationTarget encountered exception accepting command : Error executing DDL "create table mask (id bigserial not null, version integer default 0 not null, length integer, name varchar(250) not null, primary key (id))" via JDBC [type not found or user lacks privilege: BIGSERIAL]**

org.hibernate.tool.schema.spi.CommandAcceptanceException: Error executing DDL "create table mask (id bigserial not null, version integer default 0 not null, length integer, name varchar(250) not null, primary key (id))" via JDBC [type not found or user lacks privilege: BIGSERIAL]
	at org.hibernate.tool.schema.internal.exec.GenerationTargetToDatabase.accept(GenerationTargetToDatabase.java:94)
	at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.applySqlString(AbstractSchemaMigrator.java:574)

stepheng · Accepted Answer

I revisited what I had set up and found that I had not saved the server.xml in Eclipse when I added the data sources for Jics, Blusam, Bac. Unfortunately, it's easy to do especially if the AppStream session times out before a save is done.

Didier_Durand · Answer

Hi,

Look at those posts:
1. https://repost.aws/articles/AReHEuO4UwSVuyyxdjq5uWaA/how-to-invoke-an-aws-blu-age-jics-cics-transaction-via-rest-api-from-aws-lambda
2. https://docs.aws.amazon.com/m2/latest/userguide/ba-endpoints-jac.html

They both mention security definitions to complete to get JICS to run properly.

Best,

Didier

re:Post Agent · Answer

The Tomcat startup problem you're experiencing in the L3 workshop appears to be related to database configuration issues. The error messages indicate that the roles "jics" and "bluesam" do not exist in the PostgreSQL database.

To resolve this issue, you need to ensure that the necessary database roles are created and properly configured. Here are some steps you can take:

1. Check your database configuration: Make sure the database connection details in your application configuration files (like application-main.yml) are correct.

2. Create the missing roles: You may need to create the "jics" and "bluesam" roles in your PostgreSQL database. This can typically be done using SQL commands or a database management tool.

3. Grant appropriate permissions: After creating the roles, ensure they have the necessary permissions to access and modify the required database objects.

4. Verify datasource configurations: Double-check that all required datasources (jics, bluesam, bac, primary) are correctly configured in your application.

5. Restart the database server: Sometimes, restarting the PostgreSQL server can help resolve connection issues.

6. Review installation instructions: While you mentioned not seeing these roles in the installation instructions, it's worth double-checking the workshop documentation for any steps you might have missed regarding database setup.

If the problem persists after trying these steps, you may need to consult the workshop facilitators or AWS support for more specific guidance tailored to the L3 workshop environment.  
**Sources**  
[AWS Blu Age L3 workshop - Automation step error | AWS re:Post](https://repost.aws/questions/QUEO1mQjRSR5afMPLkruEvsQ/aws-blu-age-l3-workshop-automation-step-error)  
[Tomcat isn't starting in AWS Blu Age L3 Workshop | AWS re:Post](https://repost.aws/questions/QUN-kiWNv4RuWWnh0dAhQ38A/tomcat-isn-t-starting-in-aws-blu-age-l3-workshop)

Tomcat start up problem in L3 workshop

Relevant content