.WAR file runs on one Tomcat server but not the other - java

I'm unable to deploy a web application on my Tomcat server. Strangely, it works fine on a second testing server I set up. I did my best to make the environments on both machines as similar as possible, and to deploy the application the same way. I'm not sure how to proceed with troubleshooting at this point.
Both servers are running Tomcat/8.0.37 on JVM 1.8.0_101-b13 with a MySQL backend (Version 14.14 Distrib 5.7.15 for Linux (x86_64) using EditLine wrapper). The OS for both is Ubuntu 14.04, though they are hosted by different cloud providers. I have deployed the .WAR files on both servers through the Manager App's upload feature. On the non-working server, clicking Start yields the error FAIL - Application at context path /mediaServer could not be started. In Tomcat's logs/catalina.out file, I see this warning:
19-Sep-2016 20:45:29.239 WARNING [http-nio-8080-exec-1]
org.springframework.context.support.AbstractApplicationContext.doClose
Exception thrown from LifecycleProcessor on context close
java.lang.IllegalStateException: LifecycleProcessor not initialized - call
'refresh' before invoking lifecycle methods via the context: Root
WebApplicationContext: startup date [Mon Sep 19 20:45:29 UTC 2016]; root
of context hierarchy
at org.springframework.context.support.AbstractApplicationContext
.getLifecycleProcessor(AbstractApplicationContext.java:359)
at org.springframework.context.support.AbstractApplicationContext
.doClose(AbstractApplicationContext.java:890)
at org.springframework.context.support.AbstractApplicationContext
.close(AbstractApplicationContext.java:843)
at org.springframework.web.context.ContextLoader.closeWebApplicationContext
(ContextLoader.java:579)
at org.springframework.web.context.ContextLoaderListener.contextDestroyed
(ContextLoaderListener.java:115)
at org.apache.catalina.core.StandardContext.listenerStop
(StandardContext.java:4900)
at org.apache.catalina.core.StandardContext.stopInternal
(StandardContext.java:5537)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:221)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:149)
at org.apache.catalina.manager.ManagerServlet.start(ManagerServlet.java:1284)
at org.apache.catalina.manager.HTMLManagerServlet.start(HTMLManagerServlet.java:666)
at org.apache.catalina.manager.HTMLManagerServlet.doPost(HTMLManagerServlet.java:217)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:292)
at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:207)
at org.apache.catalina.filters.CsrfPreventionFilter.doFilter
(CsrfPreventionFilter.java:136)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:240)
at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:207)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:240)
at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:207)
at org.apache.catalina.filters.SetCharacterEncodingFilter.doFilter
(SetCharacterEncodingFilter.java:108)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:240)
at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:207)
at org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:212)
at org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:106)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke
(AuthenticatorBase.java:614)
at org.apache.catalina.valves.RequestFilterValve.process
(RequestFilterValve.java:313)
at org.apache.catalina.valves.RemoteAddrValve.invoke(RemoteAddrValve.java:86)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke
(AbstractAccessLogValve.java:616)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:528)
at org.apache.coyote.http11.AbstractHttp11Processor.process
(AbstractHttp11Processor.java:1100)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process
(AbstractProtocol.java:687)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1520)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1476)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)
19-Sep-2016 20:45:29.249 WARNING [http-nio-8080-exec-5]
org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The
web application [mediaServer] appears to have started a thread named
[Abandoned connection cleanup thread] but has failed to stop it. This is
very likely to create a memory leak. Stack trace of thread:
java.lang.Object.wait(Native Method)
java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143)
java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:164)
com.mysql.jdbc.NonRegisteringDriver$1.run(NonRegisteringDriver.java:93)
I see no such warnings on the working server.
Not sure if it's relevant, but the working server's Tomcat manager shows the OS version as 3.13.0-30-generic, whereas the non-working one shows 4.7.0-x86_64-linode72.
Other details:
I have two other .WAR files which are deployed and working fine on both servers.
The MySQL database names, contents, and credentials are identical on both servers.
Edits:
I have tried copying the .WAR file in question to the server and deploying it manually in the webapps directory. The issue persists and the full error log is here: http://sprunge.us/BKLg
I have also deployed the .WAR file successfully on my local Windows machine and a remote Windows Server VM. The issue only occurs on this one Ubuntu VM.

Related

Jasperserver FAIL - Application at context path [/jasperserver] could not be started

I can't run jasperserver. I have tried reinstall with bundle version (tomcat 8.5) and also with another (9.0) versions of tomcat. tomcatmanager screen . Services jasperreportsTomcat and jasperreportsPostrgreSQL are running services . run from browser Logs from tomcat local host and catalina:
27-Sep-2020 14:37:09.617 INFO [http-nio-8080-exec-46] org.apache.jasper.servlet.TldScanner.scanJars
least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a
complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during
scanning can improve startup time and JSP compilation time.
27-Sep-2020 14:37:23.252 SEVERE [http-nio-8080-exec-46]
org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full
details will be found in the appropriate container log file
27-Sep-2020 14:37:23.253 SEVERE [http-nio-8080-exec-46]
org.apache.catalina.core.StandardContext.startInternal Context [/jasperserver] startup failed due to
previous errors
27-Sep-2020 14:37:23.318 WARNING [http-nio-8080-exec-46]
org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application
[jasperserver] appears to have started a thread named [Thread-301] but has failed to stop it. This is
very likely to create a memory leak. Stack trace of thread:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:502)
com.jaspersoft.jasperserver.war.themes.ThemeCache$RefreshThread.run(ThemeCache.java:332)
27-Sep-2020 14:37:23.319 WARNING [http-nio-8080-exec-46]
org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application
[jasperserver] appears to have started a thread named [pool-36-thread-1] but has failed to stop it.
This is very likely to create a memory leak. Stack trace of thread:
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await
(AbstractQueuedSynchronizer.java:2039)
java.util.concurrent.PriorityBlockingQueue.take(PriorityBlockingQueue.java:550)
jmxlogger.tools.JmxLogService$3.run(JmxLogService.java:214)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
java.lang.Thread.run(Thread.java:748)
Please help me. This is useful in my first project :-)
I solved this by installing Jasper Server version 7.5 and delete .jrsks and .jrsksp from C:/users/[username here] before intalation. I chose everythink bundled during installation.

Tomcat undeploys WARs automatically after some time

I'm facing an issue with Apache Tomcat 9.0.13 with JDK 1.8, where it tries to reload memory user database & upon failure, undeploys all the WARs of webapps.
Stacktrace of the exception is as follows:
12-Dec-2018 14:16:45.739 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
12-Dec-2018 14:16:45.766 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-8009"]
12-Dec-2018 14:16:45.779 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 11788 ms
12-Dec-2018 15:34:02.582 INFO [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.users.MemoryUserDatabase.backgroundProcess Reloading memory user database [UserDatabase] from updated source [file:/P:/Tools/apache-tomcat-9.0.13/conf/tomcat-users.xml]
12-Dec-2018 15:34:02.582 SEVERE [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.users.MemoryUserDatabase.open The specified user database [conf/tomcat-users.xml] could not be found
12-Dec-2018 15:34:03.082 INFO [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.startup.HostConfig.undeploy Undeploying context []
12-Dec-2018 15:34:03.082 WARNING [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.startup.HostConfig.undeploy Error while removing context []
java.lang.NoClassDefFoundError: org/apache/catalina/Lifecycle$SingleUse
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:269)
at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:834)
at org.apache.catalina.startup.HostConfig.undeploy(HostConfig.java:1434)
at org.apache.catalina.startup.HostConfig.checkResources(HostConfig.java:1360)
at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1620)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:304)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)
at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1179)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1401)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1405)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1373)
at java.lang.Thread.run(Thread.java:745)
Please note, tomcat-users.xml is located at conf folder.
Can anyone help me fix the issue?
Thanks.
The server on which Tomcat is running lost the connection to the P: drive momentarily. That triggered both the failure to check the tomcat-users.xml file and the undeloyment of the web applications. You need to move the webapps directory to a more reliable network location or, better still, a local drive.
Seems that the file tomcat-users.xml has not been found - might be removed or corrupted. This file serves as an in-memory database for the Tomcat management users. Download the Tomcat again and add the missing/corrupted file to the conf folder.
Also, search for the following lines to the server.xml which should be included because it registers in JNDI as an instance of UserDatabase. If the lines are missing, add them:
<Resource name="UserDatabase" auth="Container"
pathname="conf/tomcat-users.xml"
description="User database that can be updated and saved"
type="org.apache.catalina.UserDatabase"
factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
/>
The conclusion and the safer way would be to download a new entire instance of Tomcat from scratch.

Cannot start Apache application after deployment on Windows

Trying to deploy Midpoint OpenSource IDM software on Windows server
Runing JAVA 9.0.1 and Tomcat Apache 8.5
Deployment of the WAR file seems to succeed but application does not start
On Tomcat Web Application Manager I get the error:
FAIL - Application at context path [/midpoint] could not be started
In the Catalina logs all I can see is:
SEVERE [http-nio-8080-exec-38] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
SEVERE [http-nio-8080-exec-38] org.apache.catalina.core.StandardContext.startInternal Context [/midpoint] startup failed due to previous errors

Pentaho 6 Quartz DB error after switching to postgres

I am moving our Pentaho 4 installation to new server and also updating it to pentaho 6 with postgresSQL databases instead of hypersql.
I have been following this guide: http://helicaltech.com/steps-migrate-oracle-pentaho/
even that it is meant for Oracle, files needed to be edited looks pretty much same.
There is one exception, as I have not changed file biserver-ce/pentaho-solutions/system/quartz/quartz.properties because it already contains org.quartz.jobStore.driverDelegateClass = org.quartz.impl.jdbcjobstore.PostgreSQLDelegate which I believe is postgres configuration.
However, when I try to start my bi-server, I am getting into error that prevents my bi-server to start. Here is the catalina.out exception:
18-Oct-2016 15:56:57.618 INFO [Thread-17] org.apache.cxf.endpoint.ServerImpl.initDestination Setting the server's publish address to be /lineage
18-Oct-2016 15:56:58.421 INFO [Thread-17] org.apache.cxf.endpoint.ServerImpl.initDestination Setting the server's publish address to be /marketplace
15:56:58,467 ERROR [0] [[org.osgi.service.cm.ConfigurationAdmin]]Cannot use configuration org.pentaho.requirejs for [org.osgi.service.cm.ManagedService, id=495, bundle=187/mvn:pentaho/pentaho-requirejs-osgi-manager/6.0.1.0-386]: No visibility to configuration bound to mvn:pentaho/pentaho-server-bundle/6.0.1.0-386
********************************************************************************
15:57:14,694 ERROR [EmbeddedQuartzSystemListener] EmbeddedQuartzSystemListener.ERROR_0007_SQLERROR
org.postgresql.util.PSQLException: ERROR: syntax error at or near "RUNSCRIPT"
Position: 1
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2198)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1927)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:561)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:405)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:333)
at org.apache.commons.dbcp.DelegatingStatement.executeUpdate(DelegatingStatement.java:228)
at org.apache.commons.dbcp.DelegatingStatement.executeUpdate(DelegatingStatement.java:228)
at org.pentaho.platform.scheduler2.quartz.EmbeddedQuartzSystemListener.verifyQuartzIsConfigured(EmbeddedQuartzSystemListener.java:176)
at org.pentaho.platform.scheduler2.quartz.EmbeddedQuartzSystemListener.startup(EmbeddedQuartzSystemListener.java:100)
at org.pentaho.platform.engine.core.system.PentahoSystem$2.call(PentahoSystem.java:436)
at org.pentaho.platform.engine.core.system.PentahoSystem$2.call(PentahoSystem.java:427)
at org.pentaho.platform.engine.core.system.PentahoSystem.runAsSystem(PentahoSystem.java:406)
at org.pentaho.platform.engine.core.system.PentahoSystem.notifySystemListenersOfStartup(PentahoSystem.java:427)
at org.pentaho.platform.engine.core.system.PentahoSystem.access$000(PentahoSystem.java:82)
at org.pentaho.platform.engine.core.system.PentahoSystem$1.call(PentahoSystem.java:358)
at org.pentaho.platform.engine.core.system.PentahoSystem$1.call(PentahoSystem.java:355)
at org.pentaho.platform.engine.core.system.PentahoSystem.runAsSystem(PentahoSystem.java:406)
at org.pentaho.platform.engine.core.system.PentahoSystem.notifySystemListenersOfStartup(PentahoSystem.java:355)
at org.pentaho.platform.engine.core.system.PentahoSystem.init(PentahoSystem.java:326)
at org.pentaho.platform.engine.core.system.PentahoSystem.init(PentahoSystem.java:222)
at org.pentaho.platform.web.http.context.SolutionContextListener.contextInitialized(SolutionContextListener.java:154)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4729)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5167)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:725)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1101)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1786)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
15:57:14,696 ERROR [Logger] Error: Pentaho
15:57:14,696 ERROR [Logger] misc-org.pentaho.platform.engine.core.system.PentahoSystem: org.pentaho.platform.api.engine.PentahoSystemException: PentahoSystem.ERROR_0014 - Error while trying to execute startup sequence for org.pentaho.platform.scheduler2.quartz.EmbeddedQuartzSystemListener
org.pentaho.platform.api.engine.PentahoSystemException: org.pentaho.platform.api.engine.PentahoSystemException: PentahoSystem.ERROR_0014 - Error while trying to execute startup sequence for org.pentaho.platform.scheduler2.quartz.EmbeddedQuartzSystemListener
at org.pentaho.platform.engine.core.system.PentahoSystem.notifySystemListenersOfStartup(PentahoSystem.java:363)
at org.pentaho.platform.engine.core.system.PentahoSystem.init(PentahoSystem.java:326)
at org.pentaho.platform.engine.core.system.PentahoSystem.init(PentahoSystem.java:222)
at org.pentaho.platform.web.http.context.SolutionContextListener.contextInitialized(SolutionContextListener.java:154)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4729)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5167)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:725)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1101)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1786)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.pentaho.platform.api.engine.PentahoSystemException: PentahoSystem.ERROR_0014 - Error while trying to execute startup sequence for org.pentaho.platform.scheduler2.quartz.EmbeddedQuartzSystemListener
at org.pentaho.platform.engine.core.system.PentahoSystem$2.call(PentahoSystem.java:445)
at org.pentaho.platform.engine.core.system.PentahoSystem$2.call(PentahoSystem.java:427)
at org.pentaho.platform.engine.core.system.PentahoSystem.runAsSystem(PentahoSystem.java:406)
at org.pentaho.platform.engine.core.system.PentahoSystem.notifySystemListenersOfStartup(PentahoSystem.java:427)
at org.pentaho.platform.engine.core.system.PentahoSystem.access$000(PentahoSystem.java:82)
at org.pentaho.platform.engine.core.system.PentahoSystem$1.call(PentahoSystem.java:358)
at org.pentaho.platform.engine.core.system.PentahoSystem$1.call(PentahoSystem.java:355)
at org.pentaho.platform.engine.core.system.PentahoSystem.runAsSystem(PentahoSystem.java:406)
at org.pentaho.platform.engine.core.system.PentahoSystem.notifySystemListenersOfStartup(PentahoSystem.java:355)
... 16 more
Caused by: org.pentaho.platform.api.engine.PentahoSystemException: PentahoSystem.ERROR_0014 - Error while trying to execute startup sequence for org.pentaho.platform.scheduler2.quartz.EmbeddedQuartzSystemListener
at org.pentaho.platform.engine.core.system.PentahoSystem$2.call(PentahoSystem.java:437)
... 24 more
15:57:14,696 ERROR [Logger] Error end:
Pentaho BI Platform server failed to properly initialize. The system will not be available for requests. (Pentaho Open Source BA Server 6.0.1.0-386) Fully Qualified Server Url = http://localhost:8080/pentaho/, Solution Path = /home/app_core/flexcore/pentaho/biserver-ce/pentaho-solutions
18-Oct-2016 15:57:17.747 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory /home/app_core/flexcore/pentaho/biserver-ce/tomcat/webapps/pentaho has finished in 43,862 ms
18-Oct-2016 15:57:17.747 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory /home/app_core/flexcore/pentaho/biserver-ce/tomcat/webapps/ROOT
18-Oct-2016 15:57:17.882 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
18-Oct-2016 15:57:17.883 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory /home/app_core/flexcore/pentaho/biserver-ce/tomcat/webapps/ROOT has finished in 136 ms
18-Oct-2016 15:57:17.885 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
18-Oct-2016 15:57:17.889 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-8009"]
18-Oct-2016 15:57:17.890 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 45068 ms
I am not very certain with Java, so I would like to ask, if anybody can give me some hints where should I look for problem. Or what files should I check.
PS:
Yes, I have used biserver-ce\data\postgres files to create
databases.
I have also checked pentaho oficial guide at link: https://help.pentaho.com/Documentation/6.0/0F0/0K0/040/0A0 but the Quartz settings looks same as mine.
I have tried different validationQuery settings, but that did not help.
I was also trying to find "Listener". And I have found it in
bi-server/pentaho-solutions/system/quartz/quartz.properties but it is commented (dummy one = #org.quartz.triggerListener.dummy.class = org.quartz.examples.DumbTriggerListener) and no guide is doing anything with that
setting.
I just hit this myself and found the answer here:
http://forums.pentaho.com/showthread.php?153231-Pentaho-ce-5-Initialization-Exception
The solution is to create a table named QRTZ in the quartz DB:
CREATE TABLE "QRTZ"
(
NAME VARCHAR(200) NOT NULL,
PRIMARY KEY (NAME)
);
This worked for me and others in the thread in the link

How to deploy a Tomcat application with URL API when using custom context XML

My application context is defined as an XML file located in my/path/to/Tomcat/conf/Catalina/localhost/my-app.xml.
<Context docBase='/my/path/to/myApp/myAppWarFile.war'>
<Environment name='my_config_dir' value='/my/path/to/myApp' type='java.lang.String'/>
</Context>
/my/path/to/myApp contains the WAR file myAppWarFile.war and a number of externalized properties that are read by Spring.
Tomcat is configured with autoDeploy turned off. When I start Tomcat, it creates my/path/to/Tomcat/conf/webapps/my-app/ and the WAR file gets unpacked into this location as expected, and the application of course can run as expected.
When I want to deploy a new version without restarting Tomcat, I run the undeploy command as follows:
curl http://localhost:8080/manager/text/undeploy?path=/my-app --user my-username:my-password
... and that works. But when I instruct Tomcat to deploy with the following curl statement, I get a failure.
curl http://localhost:8080/manager/text/deploy?config=file:/my/path/to/Tomcat/conf/Catalina/localhost/my-app.xml --user my-username:my-password
# Tomcat response
FAIL - Invalid context path null was specified
Adding the path does not help much, I still get a failure.
curl http://localhost:8080/manager/text/deploy?config=file:/my/path/to/Tomcat/conf/Catalina/localhost/my-app.xml\&path=/my-app --user my-username:my-password
# Tomcat response
FAIL - Failed to deploy application at context path /my-app
The worst part is that tailing catalina.out does not yield any insight. And on top of that, Tomcat deletes the application context XML file my/path/to/Tomcat/conf/Catalina/localhost/my-app.xml!
Naturally I have reviewed Tomcat documentation (https://tomcat.apache.org/tomcat-8.0-doc/manager-howto.html#Deploy_using_a_Context_configuration_%22.xml%22_file) and I have googled all day to figure this out, but I have not found anything that can help me with this particular configuration.
It feels as though the choice is:
Tomcat with autoDeploy on (not recommended for production) in which case simply dropping the new WAR to /my/path/to/myApp/ will cause Tomcat to hot deploy the app.
Tomcat with autoDeploy off, but re-deploying requires a Tomcat restart because the deploy API does not seem to be working as advertised.
Has anybody made this work with this configuration?
EDIT:
I turned up the logging on Catalina. When I run the first deploy command without the path, I get this set of log entries:
FINE: Start processing with input [config=file:/my/apth/to/tomcat/conf/Catalina/localhost/my-app.xml]
Oct 13, 2015 10:04:53 AM org.apache.coyote.AbstractProtocol$AbstractConnectionHandler process
FINE: Socket: [org.apache.tomcat.util.net.SocketWrapper#189651c1:Socket[addr=/0:0:0:0:0:0:0:1,port=45415,localport=8080]], Status in: [OPEN_READ], State out: [OPEN]
Oct 13, 2015 10:04:53 AM org.apache.coyote.http11.AbstractHttp11Processor process
FINE: Error parsing HTTP request header
java.io.EOFException: Unexpected EOF read on the socket
at org.apache.coyote.http11.Http11Processor.setRequestLineReadTimeout(Http11Processor.java:168)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:982)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:744)
Oct 13, 2015 10:04:53 AM org.apache.coyote.AbstractProtocol$AbstractConnectionHandler process
FINE: Socket: [org.apache.tomcat.util.net.SocketWrapper#189651c1:Socket[addr=/0:0:0:0:0:0:0:1,port=45415,localport=8080]], Status in: [OPEN_READ], State out: [CLOSED]
Oct 13, 2015 10:04:53 AM org.apache.tomcat.util.threads.LimitLatch countDown
FINE: Counting down[http-bio-8080-exec-16] latch=1
Have you tried:
curl --upload-file /my/path/to/my-app.war http://localhost:8080/manager/text/deploy?path=/my-app --user my-username:my-password

Categories