#1 2022-07-19 06:09:35

Johann
Member
Registered: 2022-05-30

Upgrade to v4.2.0: Unable to start ReportServer

Following the instructions here: https://reportserver.net/en/tutorials/upgrade-30/

After step 5 and starting my Tomcat server, the reportserver application fails to start, with the earliest error I can find occurring is "One or more listeners failed to start. Full details will be found in the appropriate container log file"

Here is the tomcat catalina log output:

19-Jul-2022 13:56:57.311 INFO [main] org.apache.catalina.core.StandardServer.await A valid shutdown command was received via the shutdown port. Stopping the Server instance.
19-Jul-2022 13:56:57.313 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-0.0.0.0-8080"]
19-Jul-2022 13:56:57.322 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["https-jsse-nio-0.0.0.0-8443"]
19-Jul-2022 13:56:57.328 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Catalina]
19-Jul-2022 13:56:57.366 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-0.0.0.0-8080"]
19-Jul-2022 13:56:57.370 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["https-jsse-nio-0.0.0.0-8443"]
19-Jul-2022 13:56:57.373 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-0.0.0.0-8080"]
19-Jul-2022 13:56:57.374 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["https-jsse-nio-0.0.0.0-8443"]
19-Jul-2022 13:57:09.161 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version name:   Apache Tomcat/9.0.27
19-Jul-2022 13:57:09.163 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built:          Oct 7 2019 09:57:22 UTC
19-Jul-2022 13:57:09.164 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version number: 9.0.27.0
19-Jul-2022 13:57:09.164 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name:               Linux
19-Jul-2022 13:57:09.164 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version:            3.10.0-957.el7.x86_64
19-Jul-2022 13:57:09.164 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture:          amd64
19-Jul-2022 13:57:09.164 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home:             /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.181-7.b13.el7.x86_64/jre
19-Jul-2022 13:57:09.164 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version:           1.8.0_181-b13
19-Jul-2022 13:57:09.164 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor:            Oracle Corporation
19-Jul-2022 13:57:09.164 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE:         /opt/tomcat/apache-tomcat-9.0.27
19-Jul-2022 13:57:09.164 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME:         /opt/tomcat/apache-tomcat-9.0.27
19-Jul-2022 13:57:09.166 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=/opt/tomcat/apache-tomcat-9.0.27/conf/logging.properties
19-Jul-2022 13:57:09.166 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
19-Jul-2022 13:57:09.166 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djdk.tls.ephemeralDHKeySize=2048
19-Jul-2022 13:57:09.166 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
19-Jul-2022 13:57:09.166 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.net.preferIPv4Stack=true
19-Jul-2022 13:57:09.166 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.net.preferIPv4Addresses=true
19-Jul-2022 13:57:09.167 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.apache.catalina.security.SecurityListener.UMASK=0027
19-Jul-2022 13:57:09.167 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dignore.endorsed.dirs=
19-Jul-2022 13:57:09.167 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=/opt/tomcat/apache-tomcat-9.0.27
19-Jul-2022 13:57:09.167 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=/opt/tomcat/apache-tomcat-9.0.27
19-Jul-2022 13:57:09.167 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=/opt/tomcat/apache-tomcat-9.0.27/temp
19-Jul-2022 13:57:09.167 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib]
19-Jul-2022 13:57:09.447 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-0.0.0.0-8080"]
19-Jul-2022 13:57:09.472 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["https-jsse-nio-0.0.0.0-8443"]
19-Jul-2022 13:57:09.665 INFO [main] org.apache.catalina.startup.Catalina.load Server initialization in [722] milliseconds
19-Jul-2022 13:57:09.694 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
19-Jul-2022 13:57:09.694 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/9.0.27]
19-Jul-2022 13:57:09.703 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/docs]
19-Jul-2022 13:57:10.195 INFO [main] 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.
19-Jul-2022 13:57:10.247 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/docs] has finished in [543] ms
19-Jul-2022 13:57:10.247 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/examples]
19-Jul-2022 13:57:10.625 INFO [main] 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.
19-Jul-2022 13:57:10.662 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/examples] has finished in [414] ms
19-Jul-2022 13:57:10.662 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/host-manager]
19-Jul-2022 13:57:10.885 INFO [main] 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.
19-Jul-2022 13:57:10.889 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/host-manager] has finished in [227] ms
19-Jul-2022 13:57:10.889 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/manager]
19-Jul-2022 13:57:11.087 INFO [main] 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.
19-Jul-2022 13:57:11.089 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/manager] has finished in [199] ms
19-Jul-2022 13:57:11.089 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/ROOT]
19-Jul-2022 13:57:11.324 INFO [main] 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.
19-Jul-2022 13:57:11.326 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/ROOT] has finished in [237] ms
19-Jul-2022 13:57:11.326 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/M1Reports]
19-Jul-2022 13:57:13.485 INFO [main] 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.
19-Jul-2022 13:57:13.579 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/M1Reports] has finished in [2,252] ms
19-Jul-2022 13:57:13.579 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/rs420]
19-Jul-2022 13:57:26.589 INFO [main] 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.
19-Jul-2022 13:57:33.190 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
19-Jul-2022 13:57:33.192 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal Context [/rs420] startup failed due to previous errors
19-Jul-2022 13:57:33.206 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [rs420] registered the JDBC driver [com.mysql.cj.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
19-Jul-2022 13:57:33.207 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [rs420] appears to have started a thread named [mysql-cj-abandoned-connection-cleanup] 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:144)
 com.mysql.cj.jdbc.AbandonedConnectionCleanupThread.run(AbandonedConnectionCleanupThread.java:91)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)
19-Jul-2022 13:57:33.208 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [rs420] appears to have started a thread named [C3P0PooledConnectionPoolManager[identityToken->z8kfltaq5u3afiuh4poc|38b44ba1]-AdminTaskTimer] 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(Timer.java:552)
 java.util.TimerThread.run(Timer.java:505)
19-Jul-2022 13:57:33.208 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [rs420] appears to have started a thread named [C3P0PooledConnectionPoolManager[identityToken->z8kfltaq5u3afiuh4poc|38b44ba1]-HelperThread-#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)
 com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:683)
19-Jul-2022 13:57:33.209 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [rs420] appears to have started a thread named [C3P0PooledConnectionPoolManager[identityToken->z8kfltaq5u3afiuh4poc|38b44ba1]-HelperThread-#1] 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)
 com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:683)
19-Jul-2022 13:57:33.210 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [rs420] appears to have started a thread named [C3P0PooledConnectionPoolManager[identityToken->z8kfltaq5u3afiuh4poc|38b44ba1]-HelperThread-#2] 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)
 com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:683)
19-Jul-2022 13:57:33.224 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/rs420] has finished in [19,645] ms
19-Jul-2022 13:57:33.225 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/reportserver]
19-Jul-2022 13:57:33.797 INFO [17] org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading Illegal access: this web application instance has been stopped already. Could not load []. 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 []. 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:1385)
                at org.apache.catalina.loader.WebappClassLoaderBase.getResource(WebappClassLoaderBase.java:1038)
                at com.mysql.cj.jdbc.AbandonedConnectionCleanupThread.checkThreadContextClassLoader(AbandonedConnectionCleanupThread.java:123)
                at com.mysql.cj.jdbc.AbandonedConnectionCleanupThread.run(AbandonedConnectionCleanupThread.java:90)
                at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
                at java.lang.Thread.run(Thread.java:748)
19-Jul-2022 13:57:33.798 INFO [17] org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading Illegal access: this web application instance has been stopped already. Could not load []. 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 []. 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:1385)
                at org.apache.catalina.loader.WebappClassLoaderBase.getResource(WebappClassLoaderBase.java:1038)
                at com.mysql.cj.jdbc.AbandonedConnectionCleanupThread.checkThreadContextClassLoader(AbandonedConnectionCleanupThread.java:123)
                at com.mysql.cj.jdbc.AbandonedConnectionCleanupThread.run(AbandonedConnectionCleanupThread.java:90)
                at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
                at java.lang.Thread.run(Thread.java:748)
19-Jul-2022 13:57:33.799 INFO [17] org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading Illegal access: this web application instance has been stopped already. Could not load []. 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 []. 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:1385)
                at org.apache.catalina.loader.WebappClassLoaderBase.getResource(WebappClassLoaderBase.java:1038)
                at com.mysql.cj.jdbc.AbandonedConnectionCleanupThread.checkThreadContextClassLoader(AbandonedConnectionCleanupThread.java:123)
                at com.mysql.cj.jdbc.AbandonedConnectionCleanupThread.run(AbandonedConnectionCleanupThread.java:90)
                at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
                at java.lang.Thread.run(Thread.java:748)


When I inspect the log file "localhost.2022-07-19.log", I see the following result which I do not understand as it does not seemed linked to the error above:

19-Jul-2022 13:56:57.340 INFO [main] org.apache.catalina.core.ApplicationContext.log SessionListener: contextDestroyed()
19-Jul-2022 13:56:57.340 INFO [main] org.apache.catalina.core.ApplicationContext.log ContextListener: contextDestroyed()
19-Jul-2022 13:57:10.217 SEVERE [main] org.apache.tomcat.util.descriptor.web.SecurityConstraint.findUncoveredHttpMethods For security constraints with URL pattern [/*] only the HTTP methods [POST GET] are covered. All other methods are uncovered.
19-Jul-2022 13:57:10.655 INFO [main] org.apache.catalina.core.ApplicationContext.log ContextListener: contextInitialized()
19-Jul-2022 13:57:10.655 INFO [main] org.apache.catalina.core.ApplicationContext.log SessionListener: contextInitialized()
19-Jul-2022 13:57:10.656 INFO [main] org.apache.catalina.core.ApplicationContext.log ContextListener: attributeAdded('StockTicker', 'async.Stockticker@47f08b81')
19-Jul-2022 13:57:10.656 SEVERE [main] org.apache.tomcat.util.descriptor.web.SecurityConstraint.findUncoveredHttpMethods For security constraints with URL pattern [/*] only the HTTP methods [POST GET] are covered. All other methods are uncovered.
19-Jul-2022 13:57:11.324 SEVERE [main] org.apache.tomcat.util.descriptor.web.SecurityConstraint.findUncoveredHttpMethods For security constraints with URL pattern [/*] only the HTTP methods [POST GET] are covered. All other methods are uncovered.
19-Jul-2022 13:57:13.497 SEVERE [main] org.apache.tomcat.util.descriptor.web.SecurityConstraint.findUncoveredHttpMethods For security constraints with URL pattern [*.jspx] only the HTTP methods [TRACE HEAD DELETE POST GET OPTIONS PUT] are covered. All other methods are uncovered.
19-Jul-2022 13:57:13.497 SEVERE [main] org.apache.tomcat.util.descriptor.web.SecurityConstraint.findUncoveredHttpMethods For security constraints with URL pattern [/navigation/tech/*] only the HTTP methods [TRACE HEAD DELETE POST GET OPTIONS PUT] are covered. All other methods are uncovered.
19-Jul-2022 13:57:13.497 SEVERE [main] org.apache.tomcat.util.descriptor.web.SecurityConstraint.findUncoveredHttpMethods For security constraints with URL pattern [/navigation/manager/*] only the HTTP methods [TRACE HEAD DELETE POST GET OPTIONS PUT] are covered. All other methods are uncovered.
19-Jul-2022 13:57:13.497 SEVERE [main] org.apache.tomcat.util.descriptor.web.SecurityConstraint.findUncoveredHttpMethods For security constraints with URL pattern [/navigation/admin/*] only the HTTP methods [TRACE HEAD DELETE POST GET OPTIONS PUT] are covered. All other methods are uncovered.
19-Jul-2022 13:57:13.497 SEVERE [main] org.apache.tomcat.util.descriptor.web.SecurityConstraint.findUncoveredHttpMethods For security constraints with URL pattern [/*] only the HTTP methods [POST GET] are covered. All other methods are uncovered.
19-Jul-2022 13:57:13.497 SEVERE [main] org.apache.tomcat.util.descriptor.web.SecurityConstraint.findUncoveredHttpMethods For security constraints with URL pattern [/support/AnATests/*] only the HTTP methods [TRACE HEAD DELETE POST GET OPTIONS PUT] are covered. All other methods are uncovered.

Update: I believe this issue could be related to the files used in `webapps/reportserver/WEB-INF/lib`. Using the unzipped files, I run into the errors/warnings listed above. However, when using my previous installation's (v3.7.1) library files instead of the unzipped ones, Tomcat is able to successfully start the ReportServer application. The catch then is that when loading the reportserver page, I get a message saying "This application is out of date...":
Microsoft-Teams-image.jpg

In my reportserver logs, there is a ClassNotFoundException thrown, but it is not obvious to me what could be causing this:

                _
 |  __ \                     | |  / ____|                          |  ____|     | |                     (_)
 | |__) |___ _ __   ___  _ __| |_| (___   ___ _ ____   _____ _ __  | |__   _ __ | |_ ___ _ __ _ __  _ __ _ ___  ___
 |  _  // _ \ '_ \ / _ \| '__| __|\___ \ / _ \ '__\ \ / / _ \ '__| |  __| | '_ \| __/ _ \ '__| '_ \| '__| / __|/ _ \
 | | \ \  __/ |_) | (_) | |  | |_ ____) |  __/ |   \ V /  __/ |    | |____| | | | ||  __/ |  | |_) | |  | \__ \  __/
 |_|  \_\___| .__/ \___/|_|   \__|_____/ \___|_|    \_/ \___|_|    |______|_| |_|\__\___|_|  | .__/|_|  |_|___/\___|
            | |                                                                              | |
            |_|                                                                              |_|

Version: RS4.2.0-6066 2022-06-29-18-43-47
Code Version: 2021-11-08-11-18-29
Java Version: Oracle Corporation OpenJDK 64-Bit Server VM 25.181-b13 (1.8)
VM Args: -Djava.util.logging.config.file=/opt/tomcat/apache-tomcat-9.0.27/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv4Addresses=true -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 -Dignore.endorsed.dirs= -Dcatalina.base=/opt/tomcat/apache-tomcat-9.0.27 -Dcatalina.home=/opt/tomcat/apache-tomcat-9.0.27 -Djava.io.tmpdir=/opt/tomcat/apache-tomcat-9.0.27/temp
rs.configdir: Not Configured

### DB Config ###
hibernate.dialect: net.datenwerke.rs.utils.hibernate.MySQL5Dialect (OK)
hibernate.connection.driver_class: com.mysql.cj.jdbc.Driver (OK)
hibernate.connection.url: jdbc:mysql://localhost:3306/reportserver (OK)
hibernate.connection.username: omc
hibernate.connection.password: **********
hibernate.default_schema:

Connection Test: OK
Schema Version: RS3.0-23

19-Jul-2022 14:24:56.388 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup Validating database schema...
19-Jul-2022 14:25:07.154 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.AdminResource
19-Jul-2022 14:25:07.155 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.AdminResource
19-Jul-2022 14:25:07.155 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.BasicRepositoryResource2
19-Jul-2022 14:25:07.155 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.BasicRepositoryResource2
19-Jul-2022 14:25:07.155 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.DataSourceResource
19-Jul-2022 14:25:07.156 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.DataSourceResource
19-Jul-2022 14:25:07.156 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.ExporterResource
19-Jul-2022 14:25:07.156 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.ExporterResource
19-Jul-2022 14:25:07.156 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.FilterRepositoryResource
19-Jul-2022 14:25:07.157 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.FilterRepositoryResource
19-Jul-2022 14:25:07.157 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.InfoResource
19-Jul-2022 14:25:07.157 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.InfoResource
19-Jul-2022 14:25:07.157 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.License
19-Jul-2022 14:25:07.157 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.License
19-Jul-2022 14:25:07.158 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.OlapDiscoverResource
19-Jul-2022 14:25:07.158 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.OlapDiscoverResource
19-Jul-2022 14:25:07.158 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.Query2Resource
19-Jul-2022 14:25:07.158 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.Query2Resource
19-Jul-2022 14:25:07.158 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.SessionResource
19-Jul-2022 14:25:07.159 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.SessionResource
19-Jul-2022 14:25:07.159 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.SaikuI18nResource
19-Jul-2022 14:25:07.159 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.SaikuI18nResource
19-Jul-2022 14:25:07.159 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure try to bind: net.datenwerke.rs.saiku.server.rest.resources.StatisticsResource
19-Jul-2022 14:25:07.159 INFO [main] net.datenwerke.rs.saiku.server.rest.SaikuRestModule.configure done binding: net.datenwerke.rs.saiku.server.rest.resources.StatisticsResource
19-Jul-2022 14:25:07.487 INFO [main] net.datenwerke.rsenterprise.main.service.RsEnterpriseModule.configureServlets SAP Crystal libraries not present
19-Jul-2022 14:25:12.688 WARNING [main] net.datenwerke.rs.configservice.service.configservice.ConfigServiceImpl.getConfigFailsafe Configfile scheduler/scheduler.cf could not be loaded. Default values are in effect.
19-Jul-2022 14:25:12.692 WARNING [main] net.datenwerke.rs.configservice.service.configservice.ConfigServiceImpl.getConfigFailsafe Configfile exportfilemd/pdfexport.cf could not be loaded. Default values are in effect.
19-Jul-2022 14:25:12.694 WARNING [main] net.datenwerke.rs.configservice.service.configservice.ConfigServiceImpl.getConfigFailsafe Configfile exportfilemd/pdfexport.cf could not be loaded. Default values are in effect.
19-Jul-2022 14:25:12.942 INFO [main] net.datenwerke.rs.saiku.service.saiku.ThinQueryServiceImpl.<init> loaded thinqueryservice
19-Jul-2022 14:25:13.192 INFO [main] net.datenwerke.rs.core.service.i18ntools.RemoteMessageServiceImpl.<init> Loading messages...
19-Jul-2022 14:25:22.061 INFO [main] net.datenwerke.rs.core.service.i18ntools.RemoteMessageServiceImpl.<init> Available locales: de, hi, lo, pt, lt, hr, lv, hu, zh-CN, hy, uk, id, mk, mn, af, uz, ms, el, mt, en, is, it, my, es, et, eu, vi, ja, ne, ro, nl, no, ru, be, fi, bg, keys, fr, bn, jw, bs, ka, si, sk, sl, ga, gd, ca, sq, sr, kk, km, sv, ko, zh-TW, ta, cs, th, lb, tl, pl, da, tr
19-Jul-2022 14:25:22.092 SEVERE [main] org.apache.catalina.session.StandardManager.startInternal Exception loading sessions from persistent storage
        java.lang.NoClassDefFoundError: org/slf4j/event/LoggingEvent
                at java.lang.Class.getDeclaredMethods0(Native Method)
                at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
                at java.lang.Class.getDeclaredMethod(Class.java:2128)
                at java.io.ObjectStreamClass.getPrivateMethod(ObjectStreamClass.java:1629)
                at java.io.ObjectStreamClass.access$1700(ObjectStreamClass.java:79)
                at java.io.ObjectStreamClass$3.run(ObjectStreamClass.java:520)
                at java.io.ObjectStreamClass$3.run(ObjectStreamClass.java:494)
                at java.security.AccessController.doPrivileged(Native Method)
                at java.io.ObjectStreamClass.<init>(ObjectStreamClass.java:494)
                at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:391)
                at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:681)
                at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1884)
                at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1750)
                at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2041)
                at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1572)
                at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2286)
                at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2210)
                at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2068)
                at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1572)
                at java.io.ObjectInputStream.readObject(ObjectInputStream.java:430)
                at org.apache.catalina.session.StandardSession.doReadObject(StandardSession.java:1576)
                at org.apache.catalina.session.StandardSession.readObjectData(StandardSession.java:1048)
                at org.apache.catalina.session.StandardManager.doLoad(StandardManager.java:218)
                at org.apache.catalina.session.StandardManager.load(StandardManager.java:162)
                at org.apache.catalina.session.StandardManager.startInternal(StandardManager.java:354)
                at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
                at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5163)
                at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
                at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:717)
                at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:690)
                at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:705)
                at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1133)
                at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1867)
                at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
                at java.util.concurrent.FutureTask.run(FutureTask.java:266)
                at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
                at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112)
                at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:1045)
                at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:429)
                at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1576)
                at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:309)
                at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)
                at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:423)
                at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:366)
                at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:936)
                at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:841)
                at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
                at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384)
                at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374)
                at java.util.concurrent.FutureTask.run(FutureTask.java:266)
                at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
                at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
                at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909)
                at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262)
                at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
                at org.apache.catalina.core.StandardService.startInternal(StandardService.java:421)
                at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
                at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:930)
                at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
                at org.apache.catalina.startup.Catalina.start(Catalina.java:633)
                at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
                at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
                at java.lang.reflect.Method.invoke(Method.java:498)
                at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:344)
                at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:475)
        Caused by: java.lang.ClassNotFoundException: org.slf4j.event.LoggingEvent
                at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1365)
                at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1188)
                ... 66 more
19-Jul-2022 14:25:28.353 INFO [Thread-29] net.datenwerke.rs.core.service.jarextension.hookers.ReportServerExtenderHooker.initialize Start loading ReportServer extensions.
19-Jul-2022 14:25:28.362 INFO [Thread-29] net.datenwerke.rs.core.service.EnvironmentAfterStartupInformation.initialize

Application Server: Apache Tomcat/9.0.27

### PAM Configuration ###
Static PAM configuration: net.datenwerke.rs.authenticator.service.pam.UserPasswordPAMAuthoritative
Finalized PAM configuration: class net.datenwerke.rs.authenticator.service.pam.UserPasswordPAMAuthoritative

While logging in, I get the following series of error messages: (my apologies that one of the images is slightly cut off as I was using a camera and the messages flashed by in an instant)
Microsoft-Teams-image-1.jpg
Microsoft-Teams-image-2.jpg
Microsoft-Teams-image-3.jpg


The logging in goes through in the end, but after logging in, the following error is displayed in a popup:

Error
404 <!doctype html><html lang="en"><head><title>HTTP Status 404 – Not Found</title><style type="text/css">h1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} h2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} h3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} body {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} b {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} p {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;} a {color:black;} a.name {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body>
HTTP Status 404 – Not Found
<hr class="line" /><p>Type Status Report</p><p>Message /reportserver/reportserver/tabledatasink</p><p>Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.</p><hr class="line" />
Apache Tomcat/9.0.27
</body></html> Statuscode: 404 EncodedResponse: <!doctype html><html lang="en"><head><title>HTTP Status 404 – Not Found</title><style type="text/css">h1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} h2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} h3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} body {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} b {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} p {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;} a {color:black;} a.name {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body>
HTTP Status 404 – Not Found
<hr class="line" /><p>Type Status Report</p><p>Message /reportserver/reportserver/tabledatasink</p><p>Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.</p><hr class="line" />
Apache Tomcat/9.0.27
</body></html>

I am quite stucked at this stage now. Does anyone have any ideas for how to proceed with the reportserver upgrade? Any help or advice would be greatly appreciated.

Last edited by Johann (2022-07-19 07:00:25)

Offline

#2 2022-07-19 07:03:40

eduardo
Administrator
Registered: 2016-11-01
Website

Re: Upgrade to v4.2.0: Unable to start ReportServer

Hi Johann,

I don't see this in your logs:

16:27:34.300 INFO  n.datenwerke.rs.EnvironmentValidator - Running script RS3.0-20-MySQL5_UPDATE.sql
16:27:34.310 INFO  n.datenwerke.rs.EnvironmentValidator - Running script RS3.0-21-MySQL5_UPDATE.sql
16:27:34.320 INFO  n.datenwerke.rs.EnvironmentValidator - Running script RS3.0-22-MySQL5_UPDATE.sql
16:27:34.330 INFO  n.datenwerke.rs.EnvironmentValidator - Running script RS3.0-23-MySQL5_UPDATE.sql
16:29:35.175 INFO  n.datenwerke.rs.EnvironmentValidator - Validating database schema...

I would recommend to return to your backups and try again. Keep in mind not to stop reportserver while the upgrade, even if it takes longer. And then check the logs and look for the db upgrade shown above.

Regards,
Eduardo

Offline

#3 2022-07-19 07:06:32

eduardo
Administrator
Registered: 2016-11-01
Website

Re: Upgrade to v4.2.0: Unable to start ReportServer

.. and after upgrade, don't forget to completely delete your browser's cache *including temporary internet files*

Regards,
Eduardo

Offline

#4 2022-07-19 07:20:20

Johann
Member
Registered: 2022-05-30

Re: Upgrade to v4.2.0: Unable to start ReportServer

Hi Eduardo,

I believe the schema update was already done previously on my first attempt to upgrade. From my logs today, it was around 10:57:

cat reportserver.2022-07-19.log | grep EnvironmentValidator
19-Jul-2022 09:40:24.881 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup
19-Jul-2022 09:40:24.902 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup Validating database schema...
19-Jul-2022 09:41:12.798 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup
19-Jul-2022 09:41:12.824 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup Validating database schema...
19-Jul-2022 09:42:00.091 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup
19-Jul-2022 09:42:00.110 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup Validating database schema...
19-Jul-2022 09:45:58.567 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup
19-Jul-2022 09:45:58.592 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup Validating database schema...
19-Jul-2022 09:46:43.461 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup
19-Jul-2022 09:46:43.483 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup Validating database schema...
19-Jul-2022 09:56:24.628 INFO [https-jsse-nio-0.0.0.0-8443-exec-10] net.datenwerke.rs.EnvironmentValidator.startup
19-Jul-2022 09:56:24.646 INFO [https-jsse-nio-0.0.0.0-8443-exec-10] net.datenwerke.rs.EnvironmentValidator.startup Validating database schema...
19-Jul-2022 10:14:47.827 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup
19-Jul-2022 10:14:47.849 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup Validating database schema...
19-Jul-2022 10:15:32.169 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup
19-Jul-2022 10:15:32.188 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup Validating database schema...
19-Jul-2022 10:53:54.835 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup
19-Jul-2022 10:54:08.080 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup
19-Jul-2022 10:57:32.625 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup
19-Jul-2022 10:57:32.648 INFO [main] net.datenwerke.rs.EnvironmentValidator.schemaupdate Performing database update RS3.0-21 -> RS3.0-23
19-Jul-2022 10:57:32.649 INFO [main] net.datenwerke.rs.EnvironmentValidator.doVersionUpdate Running script RS3.0-22-MySQL5_UPDATE.sql
19-Jul-2022 10:57:33.116 INFO [main] net.datenwerke.rs.EnvironmentValidator.doVersionUpdate Running script RS3.0-23-MySQL5_UPDATE.sql
19-Jul-2022 10:57:33.527 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup Validating database schema...
19-Jul-2022 10:57:51.960 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup
19-Jul-2022 10:57:51.977 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup Validating database schema...
19-Jul-2022 11:22:47.663 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup
19-Jul-2022 11:22:47.684 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup Validating database schema...
19-Jul-2022 11:23:06.752 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup
19-Jul-2022 11:23:06.769 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup Validating database schema...

Offline

#5 2022-07-19 07:23:08

Johann
Member
Registered: 2022-05-30

Re: Upgrade to v4.2.0: Unable to start ReportServer

As for the cache, using Google Chrome, I selected the clear "Cached images and files" option for All Time, but it does not seem to work for me.

Regards,
Johann

Offline

#6 2022-07-19 07:25:03

eduardo
Administrator
Registered: 2016-11-01
Website

Re: Upgrade to v4.2.0: Unable to start ReportServer

Hi Johann,

I would recommend to delete all, so select all in your chrome. First you can test with another browser if you don't want to delete all.

Regards,
Eduardo

Offline

#7 2022-07-19 07:35:39

Johann
Member
Registered: 2022-05-30

Re: Upgrade to v4.2.0: Unable to start ReportServer

Hi Eduardo,

I'll take note of that. However, I am not sure if the cache is the underlying issue. Using the library files I unzipped from RS4.2.0, I am unable to even start the ReportServer application (possibly) due to the error "IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load []." in my tomcat catalina logs. Could this be caused by some incompatibility between the .jar files since somehow the error disappears if I were to use my previous installation's files?

Offline

#8 2022-07-19 07:41:51

Johann
Member
Registered: 2022-05-30

Re: Upgrade to v4.2.0: Unable to start ReportServer

To clarify, regarding this step

Unzip ReportServer 4.2.0 and copy everything to the now empty folder. The structure should be identical to before, that is, you should once more find a file called ReportServer.html and a folder called ddl.

Must we use the exact same folder to copy ReportServer 4.2.0 to? Currently I created a new directory and copied the unzipped files there as my application folders are named with the version number.

Offline

#9 2022-07-19 08:27:45

Johann
Member
Registered: 2022-05-30

Re: Upgrade to v4.2.0: Unable to start ReportServer

I'll take note of that. However, I am not sure if the cache is the underlying issue. Using the library files I unzipped from RS4.2.0, I am unable to even start the ReportServer application (possibly) due to the error "IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load []." in my tomcat catalina logs. Could this be caused by some incompatibility between the .jar files since somehow the error disappears if I were to use my previous installation's files?

Turns out this issue has been persisting even while our previous installation was running (v3.7.1) according to the logs during that time. However, it is only now during upgrading that ReportServer is failing to start.

Offline

#10 2022-07-19 08:36:33

eduardo
Administrator
Registered: 2016-11-01
Website

Re: Upgrade to v4.2.0: Unable to start ReportServer

Hi Johann,

I would recommend to return to your previous backups, make sure reportserver starts and works correctly in the previous version, stop reportserver, delete all logs (moving them to a backup), try the upgrade exactly as it is explained in the upgrade guide, and look into the logs for any error messages, making sure the db upgrade logs are shown correctly. Then, open reportserver with a completely clean browser to avoid any cache issues.

After this works you can always rename your app folder to reflect the version, make modifications, etc, but first make sure everything works.

Regards,
Eduardo

Offline

#11 2022-07-19 09:39:19

Johann
Member
Registered: 2022-05-30

Re: Upgrade to v4.2.0: Unable to start ReportServer

Hi Eduardo,

I am trying to return to my previous backup v3.7.1. As highlighted in https://forum.reportserver.net/viewtopi … 9723#p9723, I have restored the reportserver db backup as well as the whole application folder. Tomcat is able to deploy it and the ReportServer login page loads. However, upon trying to log in, the following error is shown (https://ibb.co/j3LSvV0):

Error
Type 'net.datenwerke.rs.core.client.genrights.AccessRsGenericTargetIdentifier' was not assignable to 'com.google.gwt.user.client.rpc.IsSerializable' and did not have a custom field serializer. For security purposes, this type will not be deserialized.

I have even deleted my browser's cache before starting ReportServer, but the error still showed up. How could I fix this?

Offline

#12 2022-07-19 09:42:28

eduardo
Administrator
Registered: 2016-11-01
Website

Re: Upgrade to v4.2.0: Unable to start ReportServer

Hi Johann,

this error is a browser cache error. Pls not only delete the browser's cache, but also temporary internet files, etc.

Regards,
Eduardo

Offline

#13 2022-07-19 09:50:07

Johann
Member
Registered: 2022-05-30

Re: Upgrade to v4.2.0: Unable to start ReportServer

Hi Eduardo,

I followed the settings as described here to delete cache and temporary internet files: https://help.egcc.edu/portal/en/kb/arti … rnet-files

Am I missing something?

Regards,
Johann

Offline

#14 2022-07-19 09:52:51

eduardo
Administrator
Registered: 2016-11-01
Website

Re: Upgrade to v4.2.0: Unable to start ReportServer

Hi Johann,

.. advanced -> select all -> select all time. You can leave Browsing history, Form data, etc.

Regards,
Eduardo

Offline

#15 2022-07-19 10:03:59

Johann
Member
Registered: 2022-05-30

Re: Upgrade to v4.2.0: Unable to start ReportServer

Hi Eduardo,

I have selected the options like so: https://ibb.co/rvr1nPv

Regards,
Johann

Offline

#16 2022-07-19 10:05:22

Johann
Member
Registered: 2022-05-30

Re: Upgrade to v4.2.0: Unable to start ReportServer

Would the ownership of the application files be an issue? I am logged in as the root user and did the unzipping with root, so all the unzipped files have user and group as root.

Offline

#17 2022-07-19 10:11:39

Johann
Member
Registered: 2022-05-30

Re: Upgrade to v4.2.0: Unable to start ReportServer

I have followed the steps in the upgrade guide again after returning my previous reportserver installation, but Tomcat is still unable to start the new ReportServer 4.2.0. These are the log contents:

1. catalina.2022-07-19.log

 cat catalina.2022-07-19.log
19-Jul-2022 18:09:06.060 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version name:   Apache Tomcat/9.0.27
19-Jul-2022 18:09:06.062 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built:          Oct 7 2019 09:57:22 UTC
19-Jul-2022 18:09:06.063 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version number: 9.0.27.0
19-Jul-2022 18:09:06.063 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name:               Linux
19-Jul-2022 18:09:06.063 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version:            3.10.0-957.el7.x86_64
19-Jul-2022 18:09:06.063 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture:          amd64
19-Jul-2022 18:09:06.063 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home:             /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.181-7.b13.el7.x86_64/jre
19-Jul-2022 18:09:06.063 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version:           1.8.0_181-b13
19-Jul-2022 18:09:06.063 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor:            Oracle Corporation
19-Jul-2022 18:09:06.063 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE:         /opt/tomcat/apache-tomcat-9.0.27
19-Jul-2022 18:09:06.063 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME:         /opt/tomcat/apache-tomcat-9.0.27
19-Jul-2022 18:09:06.065 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=/opt/tomcat/apache-tomcat-9.0.27/conf/logging.properties
19-Jul-2022 18:09:06.065 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
19-Jul-2022 18:09:06.065 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djdk.tls.ephemeralDHKeySize=2048
19-Jul-2022 18:09:06.065 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
19-Jul-2022 18:09:06.065 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.net.preferIPv4Stack=true
19-Jul-2022 18:09:06.065 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.net.preferIPv4Addresses=true
19-Jul-2022 18:09:06.066 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.apache.catalina.security.SecurityListener.UMASK=0027
19-Jul-2022 18:09:06.066 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dignore.endorsed.dirs=
19-Jul-2022 18:09:06.066 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=/opt/tomcat/apache-tomcat-9.0.27
19-Jul-2022 18:09:06.066 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=/opt/tomcat/apache-tomcat-9.0.27
19-Jul-2022 18:09:06.066 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=/opt/tomcat/apache-tomcat-9.0.27/temp
19-Jul-2022 18:09:06.066 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib]
19-Jul-2022 18:09:06.330 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-0.0.0.0-8080"]
19-Jul-2022 18:09:06.353 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["https-jsse-nio-0.0.0.0-8443"]
19-Jul-2022 18:09:06.536 INFO [main] org.apache.catalina.startup.Catalina.load Server initialization in [690] milliseconds
19-Jul-2022 18:09:06.564 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
19-Jul-2022 18:09:06.564 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/9.0.27]
19-Jul-2022 18:09:06.572 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/docs]
19-Jul-2022 18:09:07.016 INFO [main] 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.
19-Jul-2022 18:09:07.072 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/docs] has finished in [500] ms
19-Jul-2022 18:09:07.073 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/examples]
19-Jul-2022 18:09:07.490 INFO [main] 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.
19-Jul-2022 18:09:07.530 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/examples] has finished in [458] ms
19-Jul-2022 18:09:07.531 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/host-manager]
19-Jul-2022 18:09:07.734 INFO [main] 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.
19-Jul-2022 18:09:07.739 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/host-manager] has finished in [208] ms
19-Jul-2022 18:09:07.739 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/manager]
19-Jul-2022 18:09:07.906 INFO [main] 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.
19-Jul-2022 18:09:07.927 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/manager] has finished in [188] ms
19-Jul-2022 18:09:07.927 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/ROOT]
19-Jul-2022 18:09:08.153 INFO [main] 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.
19-Jul-2022 18:09:08.155 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/ROOT] has finished in [228] ms
19-Jul-2022 18:09:08.155 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/M1Reports]
19-Jul-2022 18:09:09.774 INFO [main] 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.
19-Jul-2022 18:09:09.848 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/M1Reports] has finished in [1,693] ms
19-Jul-2022 18:09:09.848 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/rs371]
19-Jul-2022 18:09:24.475 INFO [main] 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.
19-Jul-2022 18:09:31.858 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
19-Jul-2022 18:09:31.864 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal Context [/rs371] startup failed due to previous errors
19-Jul-2022 18:09:31.877 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [rs371] registered the JDBC driver [com.mysql.cj.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
19-Jul-2022 18:09:31.878 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [rs371] appears to have started a thread named [mysql-cj-abandoned-connection-cleanup] 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:144)
 com.mysql.cj.jdbc.AbandonedConnectionCleanupThread.run(AbandonedConnectionCleanupThread.java:91)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)
19-Jul-2022 18:09:31.878 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [rs371] appears to have started a thread named [C3P0PooledConnectionPoolManager[identityToken->z8kfltaq633c8d176v8n4|4a4cc9c1]-AdminTaskTimer] 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(Timer.java:552)
 java.util.TimerThread.run(Timer.java:505)
19-Jul-2022 18:09:31.879 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [rs371] appears to have started a thread named [C3P0PooledConnectionPoolManager[identityToken->z8kfltaq633c8d176v8n4|4a4cc9c1]-HelperThread-#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)
 com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:683)
19-Jul-2022 18:09:31.879 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [rs371] appears to have started a thread named [C3P0PooledConnectionPoolManager[identityToken->z8kfltaq633c8d176v8n4|4a4cc9c1]-HelperThread-#1] 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)
 com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:683)
19-Jul-2022 18:09:31.880 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [rs371] appears to have started a thread named [C3P0PooledConnectionPoolManager[identityToken->z8kfltaq633c8d176v8n4|4a4cc9c1]-HelperThread-#2] 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)
 com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:683)
19-Jul-2022 18:09:31.891 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/opt/tomcat/apache-tomcat-9.0.27/webapps/rs371] has finished in [22,043] ms
19-Jul-2022 18:09:31.895 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-0.0.0.0-8080"]
19-Jul-2022 18:09:31.906 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["https-jsse-nio-0.0.0.0-8443"]
19-Jul-2022 18:09:31.908 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [25,371] milliseconds
19-Jul-2022 18:09:31.945 INFO [mysql-cj-abandoned-connection-cleanup] org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading Illegal access: this web application instance has been stopped already. Could not load []. 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 []. 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:1385)
                at org.apache.catalina.loader.WebappClassLoaderBase.getResource(WebappClassLoaderBase.java:1038)
                at com.mysql.cj.jdbc.AbandonedConnectionCleanupThread.checkThreadContextClassLoader(AbandonedConnectionCleanupThread.java:123)
                at com.mysql.cj.jdbc.AbandonedConnectionCleanupThread.run(AbandonedConnectionCleanupThread.java:90)
                at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
                at java.lang.Thread.run(Thread.java:748)
19-Jul-2022 18:10:28.168 INFO [C3P0PooledConnectionPoolManager[identityToken->z8kfltaq633c8d176v8n4|4a4cc9c1]-AdminTaskTimer] org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading Illegal access: this web application instance has been stopped already. Could not load [com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask]. 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 [com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask]. 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:1385)
                at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1373)
                at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1226)
                at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1188)
                at com.mchange.v2.resourcepool.BasicResourcePool.checkIdleResources(BasicResourcePool.java:1673)
                at com.mchange.v2.resourcepool.BasicResourcePool.access$2000(BasicResourcePool.java:44)
                at com.mchange.v2.resourcepool.BasicResourcePool$CheckIdleResourcesTask.run(BasicResourcePool.java:2214)
                at java.util.TimerThread.mainLoop(Timer.java:555)
                at java.util.TimerThread.run(Timer.java:505)

2. reportserver.2022-07-19.log

 cat reportserver.2022-07-19.log
19-Jul-2022 18:09:25.847 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup




  _____                       _    _____                            ______       _                       _
 |  __ \                     | |  / ____|                          |  ____|     | |                     (_)
 | |__) |___ _ __   ___  _ __| |_| (___   ___ _ ____   _____ _ __  | |__   _ __ | |_ ___ _ __ _ __  _ __ _ ___  ___
 |  _  // _ \ '_ \ / _ \| '__| __|\___ \ / _ \ '__\ \ / / _ \ '__| |  __| | '_ \| __/ _ \ '__| '_ \| '__| / __|/ _ \
 | | \ \  __/ |_) | (_) | |  | |_ ____) |  __/ |   \ V /  __/ |    | |____| | | | ||  __/ |  | |_) | |  | \__ \  __/
 |_|  \_\___| .__/ \___/|_|   \__|_____/ \___|_|    \_/ \___|_|    |______|_| |_|\__\___|_|  | .__/|_|  |_|___/\___|
            | |                                                                              | |
            |_|                                                                              |_|

Version: RS4.2.0-6066 2022-06-29-18-43-47
Code Version: 2022-06-21-12-12-32
Java Version: Oracle Corporation OpenJDK 64-Bit Server VM 25.181-b13 (1.8)
VM Args: -Djava.util.logging.config.file=/opt/tomcat/apache-tomcat-9.0.27/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv4Addresses=true -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 -Dignore.endorsed.dirs= -Dcatalina.base=/opt/tomcat/apache-tomcat-9.0.27 -Dcatalina.home=/opt/tomcat/apache-tomcat-9.0.27 -Djava.io.tmpdir=/opt/tomcat/apache-tomcat-9.0.27/temp
Max memory: 841 MB
rs.configdir: Not Configured

### DB Config ###
hibernate.dialect: net.datenwerke.rs.utils.hibernate.MySQL5Dialect (OK)
hibernate.connection.driver_class: com.mysql.cj.jdbc.Driver (OK)
hibernate.connection.url: jdbc:mysql://localhost:3306/reportserver (OK)
hibernate.connection.username: omc
hibernate.connection.password: **********
hibernate.default_schema:

Connection Test: OK
Schema Version: RS3.0-21

### Internal datasource metadata ###
Database name: MySQL
Database version: 8.0.19
Driver name: MySQL Connector/J
Driver version: mysql-connector-java-8.0.29 (Revision: dd61577595edad45c398af508cf91ad26fc4144f)
JDBC major version: 4
JDBC minor version: 2
JDBC URL: jdbc:mysql://localhost:3306/reportserver
JDBC username: omc@localhost


19-Jul-2022 18:09:25.875 INFO [main] net.datenwerke.rs.EnvironmentValidator.schemaupdate Performing database update RS3.0-21 -> RS3.0-23
19-Jul-2022 18:09:25.876 INFO [main] net.datenwerke.rs.EnvironmentValidator.doVersionUpdate Running script RS3.0-22-MySQL5_UPDATE.sql
19-Jul-2022 18:09:26.276 INFO [main] net.datenwerke.rs.EnvironmentValidator.doVersionUpdate Running script RS3.0-23-MySQL5_UPDATE.sql
19-Jul-2022 18:09:26.739 INFO [main] net.datenwerke.rs.EnvironmentValidator.startup Validating database schema...

It seems that ReportServer stops after the last step "Validating database schema...". The original data was exactly what I dumped out from my original database in ReportServer v3.7.1. Did I miss something?

Regards.
Johann

Offline

#18 2022-07-20 09:27:43

Johann
Member
Registered: 2022-05-30

Re: Upgrade to v4.2.0: Unable to start ReportServer

Hi Eduardo,

May I confirm the MySQL JDBC connector version that is required for ReportServer 4.2.0? As my installation was done a couple of years ago, I suspect it might be possible that my jdbc jar file could be outdated.

Regards,
Johann

Offline

#19 2022-08-03 09:48:10

eduardo
Administrator
Registered: 2016-11-01
Website

Re: Upgrade to v4.2.0: Unable to start ReportServer

Hi Johann,

the MySQL JDBC connector driver is delivered with each version of ReportServer, you can find it in .. WEB-INF/lib
So you don't need to install a MySQL driver in most cases.

Regards,
Eduardo

Offline

Board footer

Powered by FluxBB