Tomcat isn't starting in AWS Blu Age L3 Workshop

0

See below... Why isn't Tomcat able to start?

____  __                          _    __     __           _ __       

/ __ )/ /_ ______ _____ ____ | | / /__ / /___ () / __ / __ / / / / / __ / __ / _ \ | | / / _ / / __ / __/ / __/ / / / / // / / // / // / // / / | |/ / / / /_/ / // / // // / ///_,/_,/_, /_/ |/_//_/_//_/_, /
/
/ /___/

Main application >>>

2024-11-21 17:21:07.097 INFO 6240 --- [ main] c.n.b.g.a.JicsApplicationLauncher : The following 1 profile is active: "main" 2024-11-21 17:21:09.330 INFO 6240 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Multiple Spring Data modules found, entering strict repository configuration mode! 2024-11-21 17:21:09.331 INFO 6240 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFAULT mode. 2024-11-21 17:21:09.527 INFO 6240 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 195 ms. Found 13 JPA repository interfaces. 2024-11-21 17:21:10.127 INFO 6240 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Multiple Spring Data modules found, entering strict repository configuration mode! 2024-11-21 17:21:10.133 INFO 6240 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data Redis repositories in DEFAULT mode. 2024-11-21 17:21:10.154 INFO 6240 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 17 ms. Found 0 Redis repository interfaces. 2024-11-21 17:21:10.835 INFO 6240 --- [ main] o.s.cloud.context.scope.GenericScope : BeanFactory id=caae7f44-74b7-3d6f-a616-8668c22de813 2024-11-21 17:21:11.105 INFO 6240 --- [ main] o.a.c.c.C.[.[.[/gapwalk-application] : Initializing Spring embedded WebApplicationContext 2024-11-21 17:21:11.105 INFO 6240 --- [ main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 4000 ms 2024-11-21 17:21:11.431 INFO 6240 --- [ main] c.n.b.g.a.DataSourceConfiguration : Jics datasource look up in jndi. 2024-11-21 17:21:11.549 INFO 6240 --- [ main] o.hibernate.jpa.internal.util.LogHelper : HHH000204: Processing PersistenceUnitInfo [name: jics] 2024-11-21 17:21:11.803 INFO 6240 --- [ main] org.hibernate.dialect.Dialect : HHH000400: Using dialect: org.hibernate.dialect.PostgreSQLDialect 2024-11-21 17:21:12.996 INFO 6240 --- [ main] o.h.e.t.j.p.i.JtaPlatformInitiator : HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.AtomikosJtaPlatform] 2024-11-21 17:21:13.001 INFO 6240 --- [ main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'jics' 2024-11-21 17:21:13.118 INFO 6240 --- [ main] c.n.b.g.rt.script.ScriptControlTower : Launching Script Control Tower... 2024-11-21 17:21:13.591 INFO 6240 --- [ main] org.ehcache.core.EhcacheManager : Cache 'metadata' created in EhcacheManager. 2024-11-21 17:21:13.677 INFO 6240 --- [ main] c.n.b.g.b.c.s.WriteBehindPersistence : WriteBehindPersistence using delegate [PgsqlPersistence] with batch size = 10000 2024-11-21 17:21:13.688 INFO 6240 --- [ main] c.n.b.b.a.BluesamAutoConfiguration : Using write behind persistence. 2024-11-21 17:21:13.771 WARN 6240 --- [ main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'applicationInitializer': Unsatisfied dependency expressed through field 'bluesamManager'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'com.netfective.bluage.bluesam.autoconfigure.BluesamAutoConfiguration$EmbeddedBluesamAutoConfiguration': Unsatisfied dependency expressed through field 'metadataPersistence'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'metadataPersistence' defined in class path resource [com/netfective/bluage/bluesam/autoconfigure/BluesamAutoConfiguration$PgsqlAutoConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.netfective.bluage.gapwalk.bluesam.core.storage.MetadataPersistence]: Factory method 'metadataPersistence' threw exception; nested exception is java.lang.RuntimeException: Error while trying to create the metadata table, using script 2024-11-21 17:21:13.772 INFO 6240 --- [ main] j.LocalContainerEntityManagerFactoryBean : Closing JPA EntityManagerFactory for persistence unit 'jics' 2024-11-21 17:21:13.789 INFO 6240 --- [ main] ConditionEvaluationReportLoggingListener :

Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled. 2024-11-21 17:21:13.927 ERROR 6240 --- [ main] o.s.boot.SpringApplication : Application run failed

asked 2 months ago64 views
3 Answers
0
Accepted Answer

This was an issue with the carddemo_bluesam bluesam database having a - in the name instead of a _. It is resolved.

answered 2 months ago
0

It looks like a a dependency issue here, Could you check class the following property in catalina.properties

common.loader="${catalina.base}/lib","${catalina.base}/lib/*.jar","${catalina.home}/lib","${catalina.home}/lib/*.jar","C:/Bluage/workshop/CardDemo/Runtime-Timebomb/shared","C:/Bluage/workshop/CardDemo/Runtime-Timebomb/shared/*.jar"

AWS
answered 2 months ago
  • Here is my param in common.loader... Note my shared files are in the location as specified below. common.loader="${catalina.base}/lib","${catalina.base}/lib/.jar","${catalina.home}/lib","${catalina.home}/lib/.jar","C:/Work/AWS-BluAge/Runtime-Timebomb/shared","C:/Work/AWS-BluAge/Runtime-Timebomb/shared/*.jar"

0

The Tomcat server is unable to start due to an error in creating a bean for the Bluesam component, which is part of the AWS Blu Age Runtime. Specifically, there's an issue with creating the metadata table for the Bluesam manager.

The error message indicates that there's a problem with the database configuration or connectivity. It seems that the application is trying to create a metadata table using a script, but this operation is failing.

This could be due to several reasons:

  1. The database server might not be running or accessible.
  2. The database credentials in the configuration might be incorrect.
  3. The user specified in the database configuration might not have sufficient permissions to create tables.
  4. There could be an issue with the database schema or existing tables.

To resolve this, you should:

  1. Verify that the database server is running and accessible from the EC2 instance where Tomcat is installed.
  2. Double-check the database configuration in the application-main.yml file, ensuring that the connection details (host, port, database name, username, and password) are correct.
  3. Make sure the database user has the necessary permissions to create tables and modify the schema.
  4. Check the database logs for any specific errors that might provide more details about the failure.

If the issue persists, you may need to manually create the required metadata table or review the SQL script that's failing to execute. Additionally, enabling debug mode as suggested in the error message could provide more detailed information about the problem.

Sources
Set up configuration for AWS Blu Age Runtime - AWS Mainframe Modernization
AWS Blu Age L3 workshop - Automation step error | AWS re:Post
BluAge L3 Workshop CEEDAYS Program not found Exception when adding new transaction online | AWS re:Post

profile picture
answered 2 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions