Clarity

Expand all | Collapse all

Jaspersoft 6.4.2 Upgrade - Failing Tomcat 8.5 from Windows services. 

Jump to Best Answer
  • 1.  Jaspersoft 6.4.2 Upgrade - Failing Tomcat 8.5 from Windows services. 

    Posted 05-22-2018 12:33 PM
      |   view attached

    Hi Team , We have done the Jaspersoft upgrade to 6.4.2 . The Jaspersoft is running fine from Command prompt (startup.bat) but when I run it as a windows service ,throwing the below error - This is from the tomcat8-stderr.2018-05-22.log file . Please see the attached logfile . 

     

    [localhost-startStop-1] org.apache.catalina.core.NamingContextListener.addResource Failed to register in JMX: [javax.naming.NamingException: KeystoreManager.init was never called or there are errors instantiating an instance.]

     

    I did restore the keystore file from Clarity as per the suggestions in few posts in forum ,though It is still throwing the error . The error is coming only when running the   

    Attachment(s)

    zip
    tomcat8-stderr.txt.zip   3 K 1 version


  • 2.  Re: Jaspersoft 6.4.2 Upgrade - Failing Tomcat 8.5 from Windows services. 

    Broadcom Employee
    Posted 05-23-2018 05:03 AM

    Hi Ritesh

     

    This technical document can help How To Configure Jaspersoft As A Windows Service - CA Knowledge 

     

    Regards

    Suman Pramanik 



  • 3.  Re: Jaspersoft 6.4.2 Upgrade - Failing Tomcat 8.5 from Windows services. 

    Posted 05-30-2018 06:19 AM

    Hi Suman ,

    I've done the fresh installation and followed the aforesaid document but still getting the error . Can you please advice . 

    Here is the error log from jasper-stderr.flog file

     

    2018-05-30 06:03:19 Commons Daemon procrun stderr initialized
    30-May-2018 06:03:20.616 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.5.23
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Sep 28 2017 10:30:11 UTC
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 8.5.23.0
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Windows Server 2016
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 10.0
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: amd64
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: C:\Jaspersoft\Java\jre1.8.0_152
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.8.0_152-b16
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Oracle Corporation
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: C:\Jaspersoft\Tomcat\apache-tomcat-8.5.23
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: C:\Jaspersoft\Tomcat\apache-tomcat-8.5.23
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=C:\Jaspersoft\Tomcat\apache-tomcat-8.5.23
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=C:\Jaspersoft\Tomcat\apache-tomcat-8.5.23
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=C:\Jaspersoft\Tomcat\apache-tomcat-8.5.23\temp
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=C:\Jaspersoft\Tomcat\apache-tomcat-8.5.23\conf\logging.properties
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseConcMarkSweepGC
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+CMSClassUnloadingEnabled
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:MetaspaceSize=256m
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Duser.home=C:\Users\Administrator
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: exit
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms128m
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx256m
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xss2048k
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR based Apache Tomcat Native library [1.2.14] using APR version [1.6.2].
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
    30-May-2018 06:03:20.632 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL configuration: useAprConnector [false], useOpenSSL [true]
    30-May-2018 06:03:21.522 INFO [main] org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL successfully initialized [OpenSSL 1.0.2l 25 May 2017]
    30-May-2018 06:03:21.710 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8080"]
    30-May-2018 06:03:21.819 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
    30-May-2018 06:03:21.819 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["ajp-nio-8009"]
    30-May-2018 06:03:21.819 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
    30-May-2018 06:03:21.819 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 1753 ms
    30-May-2018 06:03:21.866 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
    30-May-2018 06:03:21.866 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.23
    30-May-2018 06:03:21.866 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [C:\Jaspersoft\Tomcat\apache-tomcat-8.5.23\webapps\docs]
    30-May-2018 06:03:23.491 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.
    30-May-2018 06:03:23.554 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [C:\Jaspersoft\Tomcat\apache-tomcat-8.5.23\webapps\docs] has finished in [1,688] ms
    30-May-2018 06:03:23.554 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [C:\Jaspersoft\Tomcat\apache-tomcat-8.5.23\webapps\examples]
    30-May-2018 06:03:25.069 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.
    30-May-2018 06:03:25.148 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [C:\Jaspersoft\Tomcat\apache-tomcat-8.5.23\webapps\examples] has finished in [1,594] ms
    30-May-2018 06:03:25.148 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [C:\Jaspersoft\Tomcat\apache-tomcat-8.5.23\webapps\host-manager]
    30-May-2018 06:03:26.366 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.
    30-May-2018 06:03:26.382 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [C:\Jaspersoft\Tomcat\apache-tomcat-8.5.23\webapps\host-manager] has finished in [1,234] ms
    30-May-2018 06:03:26.382 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [C:\Jaspersoft\Tomcat\apache-tomcat-8.5.23\webapps\manager]
    30-May-2018 06:03:27.398 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.
    30-May-2018 06:03:27.413 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [C:\Jaspersoft\Tomcat\apache-tomcat-8.5.23\webapps\manager] has finished in [1,031] ms
    30-May-2018 06:03:27.413 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [C:\Jaspersoft\Tomcat\apache-tomcat-8.5.23\webapps\ppmreports]
    30-May-2018 06:03:57.195 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.
    30-May-2018 06:04:42.894 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
    30-May-2018 06:04:42.894 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [/ppmreports] startup failed due to previous errors
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ppmreports] registered the JDBC driver [tibcosoftware.jdbc.oracle.OracleDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ppmreports] registered the JDBC driver [tibcosoftware.jdbc.oracle.OracleDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ppmreports] registered the JDBC driver [tibcosoftware.jdbc.sqlserver.SQLServerDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ppmreports] registered the JDBC driver [tibcosoftware.jdbc.sqlserver.SQLServerDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ppmreports] registered the JDBC driver [tibcosoftware.jdbc.db2.DB2Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ppmreports] registered the JDBC driver [tibcosoftware.jdbc.db2.DB2Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ppmreports] registered the JDBC driver [tibcosoftware.jdbc.hive.HiveDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ppmreports] registered the JDBC driver [tibcosoftware.jdbc.hive.HiveDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ppmreports] registered the JDBC driver [tibcosoftware.jdbc.impala.ImpalaDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ppmreports] registered the JDBC driver [tibcosoftware.jdbc.impala.ImpalaDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ppmreports] registered the JDBC driver [tibcosoftware.jdbc.mongodb.MongoDBDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ppmreports] registered the JDBC driver [tibcosoftware.jdbc.mongodb.MongoDBDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ppmreports] registered the JDBC driver [tibcosoftware.jdbc.redshift.RedshiftDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ppmreports] registered the JDBC driver [tibcosoftware.jdbc.redshift.RedshiftDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ppmreports] registered the JDBC driver [tibcosoftware.jdbc.sforce.SForceDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ppmreports] registered the JDBC driver [tibcosoftware.jdbc.sforce.SForceDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ppmreports] registered the JDBC driver [org.teiid.jdbc.TeiidDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ppmreports] appears to have started a thread named [Thread-5] 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(Unknown Source)
    com.jaspersoft.jasperserver.war.themes.ThemeCache$RefreshThread.run(ThemeCache.java:330)
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ppmreports] appears to have started a thread named [Thread-6] 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(Unknown Source)
    com.ca.jasper.theme.JaasThemeCache$RefreshThread.run(JaasThemeCache.java:334)
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ppmreports] appears to have started a thread named [Timer-0] 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(Unknown Source)
    java.util.TimerThread.mainLoop(Unknown Source)
    java.util.TimerThread.run(Unknown Source)
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ppmreports] appears to have started a thread named [oracle.jdbc.driver.BlockSource.ThreadedCachingBlockSource.BlockReleaser] 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)
    oracle.jdbc.driver.BlockSource$ThreadedCachingBlockSource$BlockReleaser.run(BlockSource.java:329)
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ppmreports] appears to have started a thread named [InterruptTimer] 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(Unknown Source)
    java.util.TimerThread.mainLoop(Unknown Source)
    java.util.TimerThread.run(Unknown Source)
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ppmreports] appears to have started a thread named [CascadeCacheCleaner] 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.util.TimerThread.mainLoop(Unknown Source)
    java.util.TimerThread.run(Unknown Source)
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ppmreports] appears to have started a thread named [bitronix-task-scheduler] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    java.lang.Thread.sleep(Native Method)
    bitronix.tm.timer.TaskScheduler.run(TaskScheduler.java:245)
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ppmreports] appears to have started a thread named [BufferManager Cleaner] 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)
    org.teiid.common.buffer.impl.BufferManagerImpl$Cleaner.run(BufferManagerImpl.java:120)
    java.util.TimerThread.mainLoop(Unknown Source)
    java.util.TimerThread.run(Unknown Source)
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ppmreports] appears to have started a thread named [Scheduled-eviction-thread-0] 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.parkNanos(Unknown Source)
    java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown Source)
    java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(Unknown Source)
    java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(Unknown Source)
    java.util.concurrent.ThreadPoolExecutor.getTask(Unknown Source)
    java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    java.lang.Thread.run(Unknown Source)
    30-May-2018 06:04:43.066 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ppmreports] appears to have started a thread named [JasperServer Adhoc EhCache Cleaner] 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.util.TimerThread.mainLoop(Unknown Source)
    java.util.TimerThread.run(Unknown Source)
    30-May-2018 06:04:43.066 SEVERE [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ppmreports] created a ThreadLocal with key of type [org.teiid.query.parser.QueryParser$1] (value [org.teiid.query.parser.QueryParser$1@2cb254a3]) and a value of type [org.teiid.query.parser.QueryParser] (value [org.teiid.query.parser.QueryParser@355d0b80]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
    30-May-2018 06:04:43.097 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [C:\Jaspersoft\Tomcat\apache-tomcat-8.5.23\webapps\ppmreports] has finished in [75,684] ms
    30-May-2018 06:04:43.097 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [C:\Jaspersoft\Tomcat\apache-tomcat-8.5.23\webapps\ROOT]
    30-May-2018 06:04:44.488 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.
    30-May-2018 06:04:44.488 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [C:\Jaspersoft\Tomcat\apache-tomcat-8.5.23\webapps\ROOT] has finished in [1,391] ms
    30-May-2018 06:04:44.503 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
    30-May-2018 06:04:44.519 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-8009"]
    30-May-2018 06:04:44.519 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 82697 ms
    30-May-2018 06:05:39.769 INFO [Scheduled-eviction-thread-0] org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading Illegal access: this web application instance has been stopped already. Could not load [org.infinispan.util.concurrent.BoundedConcurrentHashMap$Values]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
    java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load [org.infinispan.util.concurrent.BoundedConcurrentHashMap$Values]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
    at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1311)
    at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1299)
    at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1158)
    at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1119)
    at org.infinispan.util.concurrent.BoundedConcurrentHashMap.values(BoundedConcurrentHashMap.java:2113)
    at org.infinispan.container.DefaultDataContainer.purgeExpired(DefaultDataContainer.java:189)
    at org.infinispan.eviction.EvictionManagerImpl.processEviction(EvictionManagerImpl.java:102)
    at org.infinispan.eviction.EvictionManagerImpl$ScheduledTask.run(EvictionManagerImpl.java:144)
    at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
    at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)



  • 4.  Re: Jaspersoft 6.4.2 Upgrade - Failing Tomcat 8.5 from Windows services. 

    Posted 08-29-2018 08:48 AM

    It appears that the Apache Tomcat release included in the distribution 'CA BUSINESS INTELLIGENCE JASPERSOFT REPORTS SERVER 6.4.2_5.4.2.15 FOR CA PPM.', file: DVD500000000001272.iso does include the stripped version of Apache which does not include the service wrapper. The Apache Tomcat release paired with the CA PPM installation binaries does have the service wrapper but is a different version: Apache Tomcat 8.5.28 instead of Apache Tomcat 8.5.23.



  • 5.  Re: Jaspersoft 6.4.2 Upgrade - Failing Tomcat 8.5 from Windows services. 

    Broadcom Employee
    Posted 05-23-2018 05:26 AM

    Hi Ritesh,

     

    1. Check whether the Jaspersoft  service is configured with the any windows service account.

    2.Check the License files are present in the install user home directory.

    3.Check if the License Path is mentioned in the JVM Parameters then correct the path location.

     

    Regards,

    Arun



  • 6.  Re: Jaspersoft 6.4.2 Upgrade - Failing Tomcat 8.5 from Windows services. 

    Posted 05-23-2018 12:54 PM

    Thanks Arun for your reply ! Please find my answer below - 

     

    1.. Check whether the Jaspersoft  service is configured with the any windows service account.

    Ritesh - What do you mean by windows service account , I created the Jaspersoft as windows service using my account from CMD ->Run as a Administrator . Are you referring something else .

    2.Check the License files are present in the install user home directory.

    Ritesh - Yes, it is present .

    3.Check if the License Path is mentioned in the JVM Parameters then correct the path location.

    Ritesh - Can you please guide me how do I check this ?



  • 7.  Re: Jaspersoft 6.4.2 Upgrade - Failing Tomcat 8.5 from Windows services. 
    Best Answer

    Posted 05-30-2018 10:56 AM

    Thanks Everyone for your input . This is fixed .