search

daust / JasperReportsIntegration

JasperReportsIntegration provides an interface to use the JasperReports reporting engine in an Oracle database application, specifically with Oracle Application Express (Oracle APEX).
BSD 3-Clause "New" or "Revised" License
55 stars 23 forks source link

Does this work on Tomcat 10.1.3 #135

Closed badger95 closed 10 months ago

badger95 commented 10 months ago

I've been using JasperReportsIntegration for 10 years and have never had issue. I recently upgraded to Tomcat 10.1.3 and am having issues. I've deployed to webapps directory and get: FAIL - Application at context path [/jri] could not be started I've deployed also to webapps-javaee directory and can get the jri home test page to load but when trying to run the test.pdf it returns java errors.

ON page it lists: The current configuration is loaded from: F:/JasperIntegrationforTomcat10 Config-Directory: F:/JasperIntegrationforTomcat10\conf Config-File: F:/JasperIntegrationforTomcat10\conf\application.properties Reports-Path: F:\JasperIntegrationforTomcat10\conf..\reports Temp-Directory: C:\Program Files\Apache Software Foundation\Tomcat 10.1\webapps\jri\reporttmp Logs-Directory: F:/JasperIntegrationforTomcat10\logs Java-Runtime-Version: 20.0.2 JasperReports-Version: 6.20.0-51a71b12f8db21cb011628dd221240da17b0feaa-migrated-1.0.7 Your ip address: 127.0.0.1 Classpath: C:\Program Files\Apache Software Foundation\Tomcat 10.1\bin\bootstrap.jar C:\Program Files\Apache Software Foundation\Tomcat 10.1\bin\tomcat-juli.jar __ERROR PAGE __ Type Exception Report

Message Servlet execution threw an exception

Description The server encountered an unexpected condition that prevented it from fulfilling the request.

Exception

jakarta.servlet.ServletException: Servlet execution threw an exception org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51) Root Cause

BUG! exception in phase 'semantic analysis' in source unit 'calculator_test_1697119302414_957837' Unsupported class file major version 64 org.codehaus.groovy.control.CompilationUnit$ISourceUnitOperation.doPhaseOperation(CompilationUnit.java:906) org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:628) net.sf.jasperreports.compilers.JRGroovyCompiler.compileUnits(JRGroovyCompiler.java:112) net.sf.jasperreports.engine.design.JRAbstractCompiler.compileReport(JRAbstractCompiler.java:230) net.sf.jasperreports.engine.JasperCompileManager.compile(JasperCompileManager.java:358) net.sf.jasperreports.engine.JasperCompileManager.compileToFile(JasperCompileManager.java:274) net.sf.jasperreports.engine.JasperCompileManager.compileToFile(JasperCompileManager.java:256) net.sf.jasperreports.engine.JasperCompileManager.compileReportToFile(JasperCompileManager.java:555) de.oc.jasper.ReportUtilities.compileJRXMLIfNecessary(ReportUtilities.java:134) de.oc.integration.jasper.webapp.ReportWrapper.service(ReportWrapper.java:197) jakarta.servlet.http.HttpServlet.service(HttpServlet.java:658) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51) Before I spend more time more time debugging....is it supported on 10.1.3 ? Thanks.

daust commented 10 months ago

Hi,

yes, should work.

I am testing releases now on Windows with:

For Tomcat 10.1.5 I am using JDK 11, though. And your error messages indicates an issue with the Java version.

Please use the latest version 2.10.1: https://github.com/daust/JasperReportsIntegration/releases

And definitely make sure to use the Tomcat10 specific version: jri-2.10.1-jasper-6.20.0-tomcat10.war.

Please let me know if this fixes the problem.

Best, Dietmar.

badger95 commented 10 months ago

Appreciated...I change Java to JDK 11 and see what happens.thx! I'll keep you posted.

On Sat, Oct 14, 2023 at 7:25 AM Dietmar Aust @.***> wrote:

Hi,

yes, should work.

I am testing releases now on Windows with:

  • apache-tomcat-10.0.27
  • apache-tomcat-10.1.5
  • glassfish-4.1
  • wildfly-26.1.1.Final
  • Weblogic wls1411
  • Weblogic wls12214

For Tomcat 10.1.5 I am using JDK 11, though. And your error messages indicates an issue with the Java version.

Please use the latest version 2.10.1: https://github.com/daust/JasperReportsIntegration/releases

And definitely make sure to use the Tomcat10 specific version: jri-2.10.1-jasper-6.20.0-tomcat10.war.

Please let me know if this fixes the problem.

Best, Dietmar.

— Reply to this email directly, view it on GitHub https://github.com/daust/JasperReportsIntegration/issues/135#issuecomment-1762823721, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDHC7M7IGVWF42QYHFTAPKLX7JZB7ANCNFSM6AAAAAA55VRWIM . You are receiving this because you authored the thread.Message ID: @.***>

badger95 commented 10 months ago

Just a quick follow up..I'm using Tomcat version 10.1.13. Do I need to put the jri.war into /webapps or /webapps-j2ee folder in Tomcat? When putting into /webapps it continually can't start:

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

When placed in webapps-j2ee folder then I can run the page and connect to database, but reports won't run. I've tried setting JAVA_HOME to JDK 11 and also to JDK 20 and get same results. My customer wants me off Tomcat 10.1.5 and on latest for security purposes, otherwise I'd stay on 10.1.5.

On Sun, Oct 15, 2023 at 9:52 AM Radiology Geocoding < @.***> wrote:

Appreciated...I change Java to JDK 11 and see what happens.thx! I'll keep you posted.

On Sat, Oct 14, 2023 at 7:25 AM Dietmar Aust @.***> wrote:

Hi,

yes, should work.

I am testing releases now on Windows with:

  • apache-tomcat-10.0.27
  • apache-tomcat-10.1.5
  • glassfish-4.1
  • wildfly-26.1.1.Final
  • Weblogic wls1411
  • Weblogic wls12214

For Tomcat 10.1.5 I am using JDK 11, though. And your error messages indicates an issue with the Java version.

Please use the latest version 2.10.1: https://github.com/daust/JasperReportsIntegration/releases

And definitely make sure to use the Tomcat10 specific version: jri-2.10.1-jasper-6.20.0-tomcat10.war.

Please let me know if this fixes the problem.

Best, Dietmar.

— Reply to this email directly, view it on GitHub https://github.com/daust/JasperReportsIntegration/issues/135#issuecomment-1762823721, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDHC7M7IGVWF42QYHFTAPKLX7JZB7ANCNFSM6AAAAAA55VRWIM . You are receiving this because you authored the thread.Message ID: @.***>

badger95 commented 10 months ago

sorry, folder webapps-javaee not webapps-j2ee....mistyped in first message...

On Sun, Oct 15, 2023 at 10:32 AM Radiology Geocoding < @.***> wrote:

Just a quick follow up..I'm using Tomcat version 10.1.13. Do I need to put the jri.war into /webapps or /webapps-j2ee folder in Tomcat? When putting into /webapps it continually can't start:

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

When placed in webapps-j2ee folder then I can run the page and connect to database, but reports won't run. I've tried setting JAVA_HOME to JDK 11 and also to JDK 20 and get same results. My customer wants me off Tomcat 10.1.5 and on latest for security purposes, otherwise I'd stay on 10.1.5.

On Sun, Oct 15, 2023 at 9:52 AM Radiology Geocoding < @.***> wrote:

Appreciated...I change Java to JDK 11 and see what happens.thx! I'll keep you posted.

On Sat, Oct 14, 2023 at 7:25 AM Dietmar Aust @.***> wrote:

Hi,

yes, should work.

I am testing releases now on Windows with:

  • apache-tomcat-10.0.27
  • apache-tomcat-10.1.5
  • glassfish-4.1
  • wildfly-26.1.1.Final
  • Weblogic wls1411
  • Weblogic wls12214

For Tomcat 10.1.5 I am using JDK 11, though. And your error messages indicates an issue with the Java version.

Please use the latest version 2.10.1: https://github.com/daust/JasperReportsIntegration/releases

And definitely make sure to use the Tomcat10 specific version: jri-2.10.1-jasper-6.20.0-tomcat10.war.

Please let me know if this fixes the problem.

Best, Dietmar.

— Reply to this email directly, view it on GitHub https://github.com/daust/JasperReportsIntegration/issues/135#issuecomment-1762823721, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDHC7M7IGVWF42QYHFTAPKLX7JZB7ANCNFSM6AAAAAA55VRWIM . You are receiving this because you authored the thread.Message ID: @.***>

daust commented 10 months ago

Hhhm. It works for me without problems. I am using Windows 11 in a virtual machine running Parallels. It is a 64bit system.

image

I have downloaded Tomcat 10.1.13 image

yet I don't see the the other webapps directory.

image

Either you are giving incorrect / missing information or I don't know.

And yes, you need to put the file jri-2.10.1-jasper-6.20.0-tomcat10.war into the directory webapps.

Also, this time you didn't give the detailed error message ... just said it won't start ... not helpful.

badger95 commented 10 months ago

Dietmar, Things seem to be working now. I can't say for sure what fixed it, but thanks so much for the quick response and willingness to help out. Really appreciate it.

On Sun, Oct 15, 2023 at 11:55 AM Dietmar Aust @.***> wrote:

Hhhm. It works for me without problems. I am using Windows 11 in a virtual machine running Parallels. It is a 64bit system.

[image: image] https://user-images.githubusercontent.com/4840057/275337493-61ac8b3f-f311-46db-929f-f1bfd6b4d877.png

I have downloaded Tomcat 10.1.13 [image: image] https://user-images.githubusercontent.com/4840057/275337600-b344a584-0113-4af6-afa0-dd5488e1b3e6.png

yet I don't see the the other webapps directory. [image: image] https://user-images.githubusercontent.com/4840057/275337644-e60098e1-6d30-403c-a57f-9fc45ef8aecc.png

Either you are giving incorrect / missing information or I don't know.

And yes, you need to put the file jri-2.10.1-jasper-6.20.0-tomcat10.war into the directory webapps.

Also, this time you didn't give the error message ... just said it won't start ... not helpful.

— Reply to this email directly, view it on GitHub https://github.com/daust/JasperReportsIntegration/issues/135#issuecomment-1763431724, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDHC7M4H3TF2OD6GE52SGPTX7QBOFANCNFSM6AAAAAA55VRWIM . You are receiving this because you authored the thread.Message ID: @.***>

daust commented 10 months ago

Wonderful. I guess in the end, it might have been that the JDK 11 was not picked up by the Tomcat environment for some reason. This would explain the behavior. Anyhow, glad you have it working now. Best, ~Dietmar.