topic Re: Troubleshoot Java agent installation on Amazon EC2 instance with Tomcat server in Splunk AppDynamics

Troubleshoot Java agent installation on Amazon EC2 instance with Tomcat server

CommunityUser — Fri, 11 Jan 2019 19:12:15 GMT

Hello,

I am facing issues while trying to setup monitoring for our Amazon EC2 instance which runs JVM and Tomcat service. Following is a snapshot of the logs:

```

ERROR Cannot access RandomAccessFile {}) java.io.FileNotFoundException: /home/ubuntu/AppDynamics/appagent/ver4.5.5.24422/logs/unknown/agent.2019_01_11__18_56_37.log (No such file or directory)
2019-01-11 18:56:37,185 ERROR Unable to invoke factory method in class class com.singularity.ee.agent.util.log4j.A for element ADRRAFAppender. java.lang.reflect.InvocationTargetException
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:606)
   at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:137)
   at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:770)
   at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:706)
   at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:698)
   at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:358)
   at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:161)
   at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:352)
   at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:395)
   at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:411)
   at com.singularity.ee.agent.appagent.kernel.JavaAgent.b(JavaAgent.java:832)
   at com.singularity.ee.agent.appagent.kernel.JavaAgent.initialize(JavaAgent.java:500)
   at com.singularity.ee.agent.appagent.kernel.JavaAgent.initialize(JavaAgent.java:312)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:606)
   at com.singularity.ee.agent.appagent.AgentEntryPoint$1.run(AgentEntryPoint.java:655)
Caused by: java.lang.IllegalStateException: Unable to create a manager
   at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:73)
   at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:60)
   at org.apache.logging.log4j.core.appender.rolling.RollingRandomAccessFileManager.getRollingRandomAccessFileManager(RollingRandomAccessFileManager.java:85)
   at com.singularity.ee.agent.util.log4j.A.a(A.java:202)
   ... 21 more

```

I was able to setup monitoring for tomcat service on my personal laptop (Mac OS High Sierra) but its failing for AWS cloud.

Any help is appreciated.

Thanks,

Vijaysimha Naik

Re: Troubleshoot Java agent installation on Amazon EC2 instance with Tomcat server

Naoto_Yamamoto — Wed, 16 Jan 2019 07:39:44 GMT

Hi Vijay,

Thanks for contacting support.

It seems that you missed the node name in your agent configuration.

Could you check your configuration in <agent dir>/conf/controller-info.xml, node-name tag?

Let me know if this helped you.

Many thanks,

Naoto

Re: Troubleshoot Java agent installation on Amazon EC2 instance with Tomcat server

CommunityUser — Wed, 16 Jan 2019 19:14:13 GMT

After adding node name I see that my AppDynamics agent is started as shown below:

```

Agent Logging Directory [/home/ubuntu/AppDynamics/appagent/ver4.5.5.24422/logs/app-j-load-dev-stack]
2019-01-16 16:42:11,041 INFO Log4j appears to be running in a Servlet environment, but there's no log4j-web module available. If you want better web container support, please add the log4j-web JAR to your web archive or server lib directory.
Running obfuscated agent
Registered app server agent with Node ID[XXX] Component ID[XXX] Application ID [XXX]
Started AppDynamics Java Agent Successfully.

```

However, I am still facing issues. Attaching the errors from catalina.out log file:

```

SEVERE: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/rds]]
   at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
   at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
   at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632)
   at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1073)
   at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:473)
   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
   at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.VerifyError: (class: org/postgresql/Driver, method: timeout signature: (Ljava/util/Properties;)J) Stack size too large
   at java.lang.Class.forName0(Native Method)
   at java.lang.Class.forName(Class.java:278)
   at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(PooledConnection.java:246)
   at org.apache.tomcat.jdbc.pool.PooledConnection.connect(PooledConnection.java:182)
   at org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(ConnectionPool.java:701)
   at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:635)
   at org.apache.tomcat.jdbc.pool.ConnectionPool.init(ConnectionPool.java:486)
   at org.apache.tomcat.jdbc.pool.ConnectionPool.<init>(ConnectionPool.java:144)
   at org.apache.tomcat.jdbc.pool.DataSourceProxy.pCreatePool(DataSourceProxy.java:116)
   at org.apache.tomcat.jdbc.pool.DataSourceProxy.createPool(DataSourceProxy.java:103)
   at org.apache.tomcat.jdbc.pool.DataSourceFactory.createDataSource(DataSourceFactory.java:554)
   at org.apache.tomcat.jdbc.pool.DataSourceFactory.getObjectInstance(DataSourceFactory.java:242)
   at org.apache.naming.factory.ResourceFactory.getObjectInstance(ResourceFactory.java:141)
   at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:321)
   at org.apache.naming.NamingContext.lookup(NamingContext.java:842)
   at org.apache.naming.NamingContext.lookup(NamingContext.java:153)
   at org.apache.naming.NamingContext.lookup(NamingContext.java:830)
   at org.apache.naming.NamingContext.lookup(NamingContext.java:167)
   at org.apache.catalina.core.NamingContextListener.addResource(NamingContextListener.java:1098)
   at org.apache.catalina.core.NamingContextListener.createNamingContext(NamingContextListener.java:677)
   at org.apache.catalina.core.NamingContextListener.lifecycleEvent(NamingContextListener.java:271)
   at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
   at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
   at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5401)
   at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
   ... 10 more

```

I am trying to install Java agent on AWS EC2 instance which runs on Ubuntu 14.04.5 LTS. Also using java version "1.7.0_80".

Any help is appreciated.

Thanks,

Vijay

Re: Troubleshoot Java agent installation on Amazon EC2 instance with Tomcat server

Naoto_Yamamoto — Fri, 18 Jan 2019 03:13:16 GMT

Hi Vijay,

Good to know agent started correctly.

Could you try to add option “-XX:-UseSplitVerifier” in your Tomcat and restart your application?
If it does not work still, then could you share whole logs?

Let me know if this helped you.

Many thanks,

Naoto

Re: Troubleshoot Java agent installation on Amazon EC2 instance with Tomcat server

CommunityUser — Fri, 18 Jan 2019 16:39:19 GMT

Hello Naoto,

Thanks for the quick reply. I tried adding “-XX:-UseSplitVerifier” both to CATALINA_OPTS and JAVA_OPTS variables, still no luck!

Here is the complete log on startup of tomcat.

************************

ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
Full Agent Registration Info Resolver using selfService [true]
Full Agent Registration Info Resolver using selfService [true]
Full Agent Registration Info Resolver using selfService [true]
Full Agent Registration Info Resolver using application name [Load Dev RDS]
Full Agent Registration Info Resolver using tier name [ACME Backend Service]
Full Agent Registration Info Resolver using node name [app-j-load-dev-stack]
Install Directory resolved to[/home/ubuntu/AppDynamics/appagent]
ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
[Thread-2] Wed Jan 16 16:42:10 UTC 2019[DEBUG]: AgentInstallManager - Full Agent Registration Info Resolver is running
[Thread-2] Wed Jan 16 16:42:10 UTC 2019[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using selfService [true]
[Thread-2] Wed Jan 16 16:42:10 UTC 2019[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using selfService [true]
[Thread-2] Wed Jan 16 16:42:10 UTC 2019[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using selfService [true]
[Thread-2] Wed Jan 16 16:42:10 UTC 2019[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using application name [Load Dev RDS]
[Thread-2] Wed Jan 16 16:42:10 UTC 2019[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using tier name [ACME Backend Service]
[Thread-2] Wed Jan 16 16:42:10 UTC 2019[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using node name [app-j-load-dev-stack]
[Thread-2] Wed Jan 16 16:42:10 UTC 2019[DEBUG]: AgentInstallManager - Full Agent Registration Info Resolver finished running
[Thread-2] Wed Jan 16 16:42:10 UTC 2019[INFO]: AgentInstallManager - Agent runtime directory set to [/home/ubuntu/AppDynamics/appagent/ver4.5.5.24422]
[Thread-2] Wed Jan 16 16:42:10 UTC 2019[INFO]: AgentInstallManager - Agent node directory set to [app-j-load-dev-stack]
[Thread-2] Wed Jan 16 16:42:10 UTC 2019[INFO]: JavaAgent - Using Java Agent Version [Server Agent #4.5.5.24422 v4.5.5 GA compatible with 4.4.1.0 r6c48e890b0e5e4bdb691d9c7ded0d6cad742a64e master]
[Thread-2] Wed Jan 16 16:42:10 UTC 2019[INFO]: JavaAgent - Running IBM Java Agent [No]
[Thread-2] Wed Jan 16 16:42:10 UTC 2019[INFO]: JavaAgent - Java Agent Directory [/home/ubuntu/AppDynamics/appagent/ver4.5.5.24422]
[Thread-2] Wed Jan 16 16:42:10 UTC 2019[INFO]: JavaAgent - Java Agent AppAgent directory [/home/ubuntu/AppDynamics/appagent/ver4.5.5.24422]
Agent Logging Directory [/home/ubuntu/AppDynamics/appagent/ver4.5.5.24422/logs/app-j-load-dev-stack]
2019-01-16 16:42:11,041 INFO Log4j appears to be running in a Servlet environment, but there's no log4j-web module available. If you want better web container support, please add the log4j-web JAR to your web archive or server lib directory.
Running obfuscated agent
Registered app server agent with Node ID[949057] Component ID[817247] Application ID [277344]
Started AppDynamics Java Agent Successfully.
Jan 16, 2019 4:42:16 PM org.apache.catalina.startup.ClassLoaderFactory validateFile
WARNING: Problem with directory [/usr/share/tomcat7/common/classes], exists: [false], isDirectory: [false], canRead: [false]
Jan 16, 2019 4:42:16 PM org.apache.catalina.startup.ClassLoaderFactory validateFile
WARNING: Problem with directory [/usr/share/tomcat7/common], exists: [false], isDirectory: [false], canRead: [false]
Jan 16, 2019 4:42:16 PM org.apache.catalina.startup.ClassLoaderFactory validateFile
WARNING: Problem with directory [/usr/share/tomcat7/server/classes], exists: [false], isDirectory: [false], canRead: [false]
Jan 16, 2019 4:42:16 PM org.apache.catalina.startup.ClassLoaderFactory validateFile
WARNING: Problem with directory [/usr/share/tomcat7/server], exists: [false], isDirectory: [false], canRead: [false]
Jan 16, 2019 4:42:16 PM org.apache.catalina.startup.ClassLoaderFactory validateFile
WARNING: Problem with directory [/usr/share/tomcat7/shared/classes], exists: [false], isDirectory: [false], canRead: [false]
Jan 16, 2019 4:42:16 PM org.apache.catalina.startup.ClassLoaderFactory validateFile
WARNING: Problem with directory [/usr/share/tomcat7/shared], exists: [false], isDirectory: [false], canRead: [false]
Jan 16, 2019 4:42:17 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Jan 16, 2019 4:42:17 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 664 ms
Jan 16, 2019 4:42:17 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Jan 16, 2019 4:42:17 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.52 (Ubuntu)
Jan 16, 2019 4:42:17 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /var/lib/tomcat7/webapps/oauth.war
[WebappClassLoader@4ee2f9b4] warning javax.* types are not being woven because the weaver option '-Xset:weaveJavaxPackages=true' has not been specified
Jan 16, 2019 4:42:25 PM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jstl/core_rt is already defined
Jan 16, 2019 4:42:25 PM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jstl/core is already defined
Jan 16, 2019 4:42:25 PM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jsp/jstl/core is already defined
Jan 16, 2019 4:42:25 PM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jstl/fmt_rt is already defined
Jan 16, 2019 4:42:25 PM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jstl/fmt is already defined
Jan 16, 2019 4:42:25 PM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jsp/jstl/fmt is already defined
Jan 16, 2019 4:42:25 PM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jsp/jstl/functions is already defined
Jan 16, 2019 4:42:25 PM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://jakarta.apache.org/taglibs/standard/permittedTaglibs is already defined
Jan 16, 2019 4:42:25 PM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://jakarta.apache.org/taglibs/standard/scriptfree is already defined
Jan 16, 2019 4:42:25 PM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jstl/sql_rt is already defined
Jan 16, 2019 4:42:25 PM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jstl/sql is already defined
Jan 16, 2019 4:42:25 PM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jsp/jstl/sql is already defined
Jan 16, 2019 4:42:25 PM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jstl/xml_rt is already defined
Jan 16, 2019 4:42:25 PM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jstl/xml is already defined
Jan 16, 2019 4:42:25 PM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jsp/jstl/xml is already defined
Jan 16, 2019 4:42:25 PM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://www.springframework.org/tags is already defined
Jan 16, 2019 4:42:25 PM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://www.springframework.org/tags/form is already defined
Jan 16, 2019 4:42:25 PM org.apache.catalina.core.ContainerBase addChildInternal
SEVERE: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/oauth]]
   at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
   at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
   at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632)
   at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1073)
   at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:473)
   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
   at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.VerifyError: (class: org/postgresql/Driver, method: timeout signature: (Ljava/util/Properties;)J) Stack size too large
   at java.lang.Class.forName0(Native Method)
   at java.lang.Class.forName(Class.java:278)
   at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(PooledConnection.java:246)
   at org.apache.tomcat.jdbc.pool.PooledConnection.connect(PooledConnection.java:182)
   at org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(ConnectionPool.java:701)
   at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:635)
   at org.apache.tomcat.jdbc.pool.ConnectionPool.init(ConnectionPool.java:486)
   at org.apache.tomcat.jdbc.pool.ConnectionPool.<init>(ConnectionPool.java:144)
   at org.apache.tomcat.jdbc.pool.DataSourceProxy.pCreatePool(DataSourceProxy.java:116)
   at org.apache.tomcat.jdbc.pool.DataSourceProxy.createPool(DataSourceProxy.java:103)
   at org.apache.tomcat.jdbc.pool.DataSourceFactory.createDataSource(DataSourceFactory.java:554)
   at org.apache.tomcat.jdbc.pool.DataSourceFactory.getObjectInstance(DataSourceFactory.java:242)
   at org.apache.naming.factory.ResourceFactory.getObjectInstance(ResourceFactory.java:141)
   at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:321)
   at org.apache.naming.NamingContext.lookup(NamingContext.java:842)
   at org.apache.naming.NamingContext.lookup(NamingContext.java:153)
   at org.apache.naming.NamingContext.lookup(NamingContext.java:830)
   at org.apache.naming.NamingContext.lookup(NamingContext.java:167)
   at org.apache.catalina.core.NamingContextListener.addResource(NamingContextListener.java:1098)
   at org.apache.catalina.core.NamingContextListener.createNamingContext(NamingContextListener.java:677)
   at org.apache.catalina.core.NamingContextListener.lifecycleEvent(NamingContextListener.java:271)
   at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
   at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
   at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5401)
   at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
   ... 10 more

Jan 16, 2019 4:42:25 PM org.apache.catalina.startup.HostConfig deployWAR
SEVERE: Error deploying web application archive /var/lib/tomcat7/webapps/oauth.war
java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/oauth]]
   at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:904)
   at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632)
   at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1073)
   at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:473)
   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
   at java.lang.Thread.run(Thread.java:748)

Jan 16, 2019 4:42:25 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /var/lib/tomcat7/webapps/rds.war
[WebappClassLoader@3311fda2] warning javax.* types are not being woven because the weaver option '-Xset:weaveJavaxPackages=true' has not been specified
Jan 16, 2019 4:42:31 PM org.apache.catalina.core.ContainerBase addChildInternal
SEVERE: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/rds]]
   at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
   at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
   at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632)
   at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1073)
   at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:473)
   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
   at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.VerifyError: (class: org/postgresql/Driver, method: timeout signature: (Ljava/util/Properties;)J) Stack size too large
   at java.lang.Class.forName0(Native Method)
   at java.lang.Class.forName(Class.java:278)
   at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(PooledConnection.java:246)
   at org.apache.tomcat.jdbc.pool.PooledConnection.connect(PooledConnection.java:182)
   at org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(ConnectionPool.java:701)
   at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:635)
   at org.apache.tomcat.jdbc.pool.ConnectionPool.init(ConnectionPool.java:486)
   at org.apache.tomcat.jdbc.pool.ConnectionPool.<init>(ConnectionPool.java:144)
   at org.apache.tomcat.jdbc.pool.DataSourceProxy.pCreatePool(DataSourceProxy.java:116)
   at org.apache.tomcat.jdbc.pool.DataSourceProxy.createPool(DataSourceProxy.java:103)
   at org.apache.tomcat.jdbc.pool.DataSourceFactory.createDataSource(DataSourceFactory.java:554)
   at org.apache.tomcat.jdbc.pool.DataSourceFactory.getObjectInstance(DataSourceFactory.java:242)
   at org.apache.naming.factory.ResourceFactory.getObjectInstance(ResourceFactory.java:141)
   at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:321)
   at org.apache.naming.NamingContext.lookup(NamingContext.java:842)
   at org.apache.naming.NamingContext.lookup(NamingContext.java:153)
   at org.apache.naming.NamingContext.lookup(NamingContext.java:830)
   at org.apache.naming.NamingContext.lookup(NamingContext.java:167)
   at org.apache.catalina.core.NamingContextListener.addResource(NamingContextListener.java:1098)
   at org.apache.catalina.core.NamingContextListener.createNamingContext(NamingContextListener.java:677)
   at org.apache.catalina.core.NamingContextListener.lifecycleEvent(NamingContextListener.java:271)
   at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
   at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
   at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5401)
   at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
   ... 10 more

Jan 16, 2019 4:42:31 PM org.apache.catalina.startup.HostConfig deployWAR
SEVERE: Error deploying web application archive /var/lib/tomcat7/webapps/rds.war
java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/rds]]
   at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:904)
   at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632)
   at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1073)
   at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:473)
   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
   at java.lang.Thread.run(Thread.java:748)

Jan 16, 2019 4:42:31 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /var/lib/tomcat7/webapps/ROOT
Jan 16, 2019 4:42:31 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Jan 16, 2019 4:42:31 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 14658 ms

*************************

Please let me know if you need anything else.

Thanks,

Vijaysimha Naik