Jim W

Problem Description: After applying hotfix package to v8.0.4, jasperserver would not start. You might be getting some missing jars related Jackson or the following error in localhost.log. 25-Jan-2024 12:07:21.755 INFO [Catalina-utility-3] org.apache.catalina.core.ApplicationContext.log 1 Spring WebApplicationInitializers detected on classpath 25-Jan-2024 12:07:21.798 SEVERE [Catalina-utility-3] org.apache.catalina.core.StandardContext.listenerStart Error configuring application listener of class [net.sf.jasperreports.phantomjs.PhantomJSServletContextListener] java.lang.ClassNotFoundException: net.sf.jasperreports.phantomjs.PhantomJSServletContextListener at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1407) at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1215) at org.apache.catalina.core.DefaultInstanceManager.loadClass(DefaultInstanceManager.java:539) at org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(DefaultInstanceManager.java:520) at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:150) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4691) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5230) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:728) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:700) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:696) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1185) at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1933) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:748) 25-Jan-2024 12:07:21.799 SEVERE [Catalina-utility-3] org.apache.catalina.core.StandardContext.listenerStart Skipped installing application listeners due to previous error(s) Solution: When applying the hotfix package for v8.0.4, there are the following sections, Added files: Modified files: Deleted files: IMPORTANT If you plan to apply this hotfix to JasperReports Server Pro 8.0.1, 8.0.2, 8.0.3 or 8.0.4 additionally delete the following libraries if found: WEB-INF/lib/athena-jdbc42-2.0.28.1000.jar WEB-INF/lib/commons-fileupload-1.*.jar WEB-INF/lib/jackson-annotations-2.1*.jar.... etc. *** You must delete all the IMPORTANT files before applying the hotfix files, then delete the files in Deleted files.

Problem Description On v8.2.0 , you will see a message at login if the credentials are incorrect: Invalid credentials supplied. Could not login to JasperReports Server Number of login attempts remaining: 9 How do I set the number of attempts allowed? Solution: In applicationContext-security.xml change this line, <property name="allowedNumberOfLoginAttempts" value="10"></property>

Problem Description: Suppose you developed a jasperserver report using the webservice datasource package https://community.jaspersoft.com/wiki/installing-webservice-datasource. You upgraded your jasperserver to v8x from v7x. You are getting the following error when running the report. 2023-11-20T12:30:21,527 ERROR JRFillSubreport,pool-11-thread-69:961 [] - Fill 1: exception net.sf.jasperreports.util.JacksonRuntimException: com.fasterxml.jackson.databind.exc.MismatchedInputException: Cannot construct instance of `com.jaspersoft.webservice.data.enumerations.LanguageType` (although at least one Creator exists): cannot deserialize from Object value (no delegate- or property-based Creator) at [Source: (com.jaspersoft.jasperserver.api.metadata.common.domain.util.FileBufferedOutputStream$DataStream); line: 2, column: 230] (through reference chain: com.jaspersoft.webservice.data.WebServiceDataAdapterImpl["language"]) Workaround: This problem is a result of migration of data adapter from Castor to Jackson happened in JR 6.19.0/JRS 8.1. a) The webservice datasource package is a community contribution, it is not a part of the jasperserver product. Therefore, it is not supported. Jasperserver is subject to change without notice regarding unsupported third party components. b) In this case, you can try the following workaround, Download jasperreports-castor-6.20.0.jar from this link, https://repo1.maven.org/maven2/net/sf/jasperreports/jasperreports-castor/6.20.0/ Stop JRS, add the jar to WEB-INF/lib, restart JRS.

Suppose you have a crosstab with multiple groups. If you add the group totals by hand, you might find the Grand Total has a different value. Most likely you are using distinct count for these groups. The explanation for the discrepancy is as follows. In group A: if you have values A, B, B, C, D, then the value for distinct count for group A will be 4. In Group B: if you have values A, A, E, E, F then the value for distinct count for group B will be 3 However, the grand total distinct count value will be 6 and not 7 because there are only 6 distinct values in the whole column (group A and B): A, B, C, D, E, F. Returning 7 (4 + 3) would be incorrect.

Problem Description You have an application that used to run fine on v7x. When upgraded to v8x, you are getting 404 errors regarding missing chunks in a HAR trace. For example, http://x.com:8080/aai/web/v1/_chunks/chunk.9622.js http://x.com:8080/aai/web/v1/_chunks/chunk.2973.js Explanation The following is a description of a customer's rare corner case usage. If you are getting the same error with some other implementation, you might want to try this solution too. This type of issue can only be remedied by using the following publicPath syntax described below. It cannot be fixed in jasperserver code. For this particular customer case, the application visualize.js code is generated from java code. In the generated script code, it is using iQuery.getScript function. When loading visualize.js script this way, it requires adding the publicPath property to the visaulize.js configuration. This is similar to when using CDN to host visualize.js. The reason being, jQuery when loading scripts dynamically does not add them to the DOM as a script tag. As a result, jasperserver cannot resolve the path to load the chunks. This is not the case before JRS 8.0.0 where visualize.js is loaded as one chunk. In v8.0.0, many chunks and maps are created and managed by webpack. When using visualize.js in this unusual way or other ways, you must have something like the following in the script code instead of just the Url. publicPath: jasperBaseUrl + '/visualize/scripts' See section 1.7.2 for a full description of the usage under certain circumstances. https://docs.tibco.com/pub/js-jrs/8.1.0/doc/pdf/TIB_js-jrs_8.1.0_Visualize.js-Guide.pdf

Problem Description If you have 2 subreports in the summary band, The first one starts in the middle of the page where the summary band is. A second subreport with the exact declarations for some reason always starts in a new page. But you want both subreports to run continuously with no blank space in between. Solution Be sure to set both subreports with runToBottom to false, and stretch type to NoStretch. You can start with this working sample and add what ever else you want to change. <summary> <band height="458" splitType="Immediate"> <subreport isUsingCache="true" runToBottom="false"> <reportElement positionType="Float" x="0" y="0" width="572" height="0" isRemoveLineWhenBlank="true" isPrintInFirstWholeBand="true" uuid="9ba40442-05ff-483c-8d0f-f84dc2238114"> <property name="net.sf.jasperreports.band.split.allowed" value="true"/> </reportElement> <subreportParameter name="P1"> <subreportParameterExpression><![CDATA[$P{P1}]]></subreportParameterExpression> </subreportParameter> <connectionExpression><![CDATA[$P{REPORT_CONNECTION}]]></connectionExpression> <subreportExpression><![CDATA["Sub1.jrxml"]]></subreportExpression> </subreport> <subreport isUsingCache="true" runToBottom="false"> <reportElement positionType="Float" x="0" y="21" width="572" height="0" isRemoveLineWhenBlank="true" isPrintInFirstWholeBand="true" uuid="515eefdc-9ab1-4af0-a3cf-2667ef6276a3"> <property name="net.sf.jasperreports.band.split.allowed" value="true"/> </reportElement> <subreportParameter name="P1"> <subreportParameterExpression><![CDATA[$P{P1}]]></subreportParameterExpression> </subreportParameter> <connectionExpression><![CDATA[$P{REPORT_CONNECTION}]]></connectionExpression> <subreportExpression><![CDATA["Sub2.jrxml"]]></subreportExpression> </subreport> </band> </summary>

Problem Description When running a report using json datassource, you might encounter the following error [only with HTTPS]. 2023-05-23T12:14:14,162 ERROR AsyncJasperPrintAccessor,pool-7-thread-1:321 - Error during report execution net.sf.jasperreports.engine.JRRuntimeException: net.sf.jasperreports.engine.JRException: Error opening input stream from URL: https://abc.com:4443/aaa/cs/ldap/userInformation. at net.sf.jasperreports.repo.DefaultRepositoryService.getInputStream(DefaultRepositoryService.java:139) at net.sf.jasperreports.repo.InputStreamPersistenceService.load(InputStreamPersistenceService.java:51) at net.sf.jasperreports.repo.DefaultRepositoryService.getResource(DefaultRepositoryService.java:196) at net.sf.jasperreports.repo.RepositoryUtil.findInputStream(RepositoryUtil.java:195) at net.sf.jasperreports.repo.RepositoryUtil.getInputStreamFromLocation(RepositoryUtil.java:172) at net.sf.jasperreports.engine.util.JsonUtil.parseJson(JsonUtil.java:172) at net.sf.jasperreports.engine.data.JsonDataSource.<init>(JsonDataSource.java:146) at net.sf.jasperreports.engine.query.JsonQueryExecuter.getJsonDataInstance(JsonQueryExecuter.java:89) at net.sf.jasperreports.engine.query.JsonQueryExecuter.getJsonDataInstance(JsonQueryExecuter.java:43) at net.sf.jasperreports.engine.query.AbstractJsonQueryExecuter.createDatasource(AbstractJsonQueryExecuter.java:93) at net.sf.jasperreports.engine.fill.JRFillDataset.createQueryDatasource(JRFillDataset.java:1257) at net.sf.jasperreports.engine.fill.JRFillDataset.initDatasource(JRFillDataset.java:726) at net.sf.jasperreports.engine.fill.BaseReportFiller.setParameters(BaseReportFiller.java:457) at net.sf.jasperreports.engine.fill.JRBaseFiller.fill(JRBaseFiller.java:584) at net.sf.jasperreports.engine.fill.BaseReportFiller.fill(BaseReportFiller.java:414) at net.sf.jasperreports.engine.fill.JRFillSubreport.fillSubreport(JRFillSubreport.java:826) at net.sf.jasperreports.engine.fill.JRSubreportRunnable.run(JRSubreportRunnable.java:61) at net.sf.jasperreports.engine.fill.AbstractThreadSubreportRunner.run(AbstractThreadSubreportRunner.java:221) 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) Caused by: net.sf.jasperreports.engine.JRException: Error opening input stream from URL: https://abc.com:4443/aaa/cs/ldap/userInformation. at net.sf.jasperreports.engine.util.JRLoader.getInputStream(JRLoader.java:343) at net.sf.jasperreports.repo.DefaultRepositoryService.getInputStream(DefaultRepositoryService.java:122) ... 20 more Caused by: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure Solution: The cause could be quite complex related to SSL/TLS, certificate or network/firewall type of issues. However, there is also a simple cause. Check this possibility first before diving into it. Check and see if you are using java version "1.8.0.241" [This version is usually included in v7 and v8 JRS bundled install. Upgrade to this version or above, java version "1.8.0_371" If that does not work, will need to check out the more complex possibilities.

Problem Description After importing a zip from Manage->Server Settings->Import, the login screen loses the background image and the login button and links are locked. HAR trace shows 403 errors in loading of UI components, and CSRF errors in the console tab of the browser developer debug panel. Solution There might be other causes. Check this one first. If you are using HTTPS at the time, try HTTP and see if you can log in. If so, check server attributes. The import operation may have cleared your domain whitelist.

Problem Description: There are many reasons for getting a CORS error. For example, you may be getting the error: CORS header ‘Access-Control-Allow-Origin’ missing If you have tried all known configurations and it is still not working, the cause may be a bug in Apache httpd. Workaround: a) Check and see if you are using Apache httpd. b) Check this link for details on this bug, https://bz.apache.org/bugzilla/show_bug.cgi?id=61820https://bz.apache.org/bugzilla/show_bug.cgi?id=61820 c) Try nginx if possible, to see if it works better.

Problem Description: If you are getting an HTTP 401 error from calling REST_V2 that cannot be explained by normal thorectical analysis. The problem may be else where unexpected. For example, you are getting an HTTP 401 error when using ROLE_AMINISTRATOR with a root user to login but you cannot duplicate the problem on a default installation. Solution: For this particular situation, turned out there is an overflow in the number of organization [2100] on the jasperserver when using MSSQL database as repository. You might also see an error like this, Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:262) Jasperserver issues the MSSQL call with the number of parameters based on the number of organizations. However, MSSQL has a limit of 2100 and therefore the REST_V2 call fails. Currently, as of v8x, there is no patch fix for this issue. You can delete unused organizations to get it down to below 2100 or migrate the repository to a different database type.

Description By default, you would log into jasperserver using the default webapp name, e.g. http://localhost:8080/jasperserver-pro Suppose you want to change it to, http://localhost:8080/myWebSite There is a standard set of files you need to change when dealing with a generic jasperserver installation. The procedure will need to be modified when you are using Docker Compose. Instructions First, you will need to get familiar with the main guide here. https://github.com/TIBCOSoftware/js-docker Second, review the image build process. Preferably try it a couple of times to be familiar with the process. https://github.com/TIBCOSoftware/js-docker/tree/main/jaspersoft-containers/Docker/jrs#deploying-jasperreports-server-and-scalable-query-engine You may skip the steps related to scalableQueryEngine if you want to deploy just jasperserver. Then when you are more comfortable with Docker Compose, you can proceed to customizing images. You would customize the image with the following steps. These changes rely on customization of features we introduced in the jaspersoft-containers project link above. 1. These steps should be performed before building the image, and after the step when you did ./unpackWARInstaller.sh mkdir /tmp/jrs cd /tmp/jrs unzip /opt/docker/js-docker/jasperreports-server-pro-8.1.0-bin/jasperserver-pro.war 2. edit /tmp/jrs/WEB-INF/web.xml <context-param> <param-name>webAppRootKey</param-name> <param-value>jasperserver.root</param-value> </context-param> to <context-param> <param-name>webAppRootKey</param-name> <param-value>myWebSite.root</param-value> </context-param> 3. edit /tmp/jrs/WEB-INF/js.quartz.properties, set report.scheduler.web.deployment.uri=http://localhost:8080/myWebSite 4. edit /tmp/jrs/WEB-INF/js.diagnostic.properties, set diagnostic.name = myWebSite 5. create folder customizations folder: cd /opt/docker/js-docker/jaspersoft-containers/Docker/jrs/resources/jasperserver-customization mkdir -p webapps/jasperserver-pro/WEB-INF 6. copy edited files cd /opt/docker/js-docker/jaspersoft-containers/Docker/jrs/resources/jasperserver-customization/webapps/jasperserver-pro/WEB-INF cp /tmp/jrs/WEB-INF/web.xml /tmp/jrs/WEB-INF/js.quartz.properties /tmp/jrs/WEB-INF/js.diagnostic.properties ./ 7. edit Docker/jrs/Dockerfile In the line before EXPOSE 8080 8443, add RUN mv $CATALINA_HOME/webapps/jasperserver-pro $CATALINA_HOME/webapps/myWebSite 8. now you can build images using Docker Compose and then start jasperserver using Docker Compose

Problem Description: 00269: 12-May-2022 13:31:17.902 SEVERE [localhost-startStop-1] org.apache.catalina.startup.ContextConfig.processAnnotationsJar Unable to process Jar entry [module-info.class] from Jar [jar:file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/jaxws-tools-2.3.2.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/picocli-4.5.2.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/jackson-core-2.11.4.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/jackson-dataformat-smile-2.11.4.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/streambuffer-1.5.7.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/policy-2.7.6.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/jackson-annotations-2.11.4.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/jackson-databind-2.11.4.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/saaj-impl-1.5.1.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/spark-jdbc42-2.6.18.1023.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/jakarta.jws-api-1.1.1.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/jakarta.xml.soap-api-1.4.1.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/cache2k-config-2.2.1.Final.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/jakarta.xml.bind-api-2.3.2.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/jakarta.xml.ws-api-2.3.2.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/cache2k-core-2.2.1.Final.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/cache2k-api-2.2.1.Final.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/snowflake-jdbc-3.13.5.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/jackson-jaxrs-json-provider-2.11.4.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/jaxws-rt-2.3.2.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/bcprov-jdk15on-1.68.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/jackson-jaxrs-base-2.11.4.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/bcpkix-jdk15on-1.68.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/neo4j-jdbc42-1.0.8.1009.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/jackson-dataformat-cbor-2.11.4.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/impala-jdbc42-2.6.21.1025.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/istack-commons-runtime-3.0.8.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/stax-ex-1.8.1.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/jaxb-api-2.3.1.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/jaxb-runtime-2.3.2.jar!/] for annotations file:/C:/opt/Jasper-Server/Tomcat%208.0/webapps/Jasper/WEB-INF/lib/jackson-module-jaxb-annotations-2.11.4.jar!/] for annotations 01110: org.apache.tomcat.util.bcel.classfile.ClassFormatException: Invalid byte tag in constant pool: 19 01111: at org.apache.tomcat.util.bcel.classfile.Constant.readConstant(Constant.java:97) Solution: If you are getting similar errors especially during upgrade, the problem may be you are using an older uncertified version of Tomcat. For example, in a previous version of JRS, you were using Tomcat 8.0. But you upgraded to JRS 8.0 without upgrading Tomcat. That would be one reason, if not the only reason, that you are getting these errors.

Problem Description: If you see the following error during upgrading to v8.0, try the solution below. 22-Apr-2022 01:37:54.192 SEVERE [localhost-startStop-1] org.apache.catalina.core.ContainerBase.addChildInternal ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [standardEngine[Catalina].StandardHost[localhost].StandardContext[/jasperserver]] at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:440) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:753) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:727) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:695) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1177) at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1925) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829) Caused by: java.lang.IllegalArgumentException: More than one fragment with the name [spring_web] was found. This is not legal with relative ordering. See section 8.2.2 2c of the Servlet specification for details. Consider using absolute ordering. at org.apache.tomcat.util.descriptor.web.WebXml.orderWebFragments(WebXml.java:2205) at org.apache.tomcat.util.descriptor.web.WebXml.orderWebFragments(WebXml.java:2164) at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1083) at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:779) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:299) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5130) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) ... 10 more Solution: Add <absolute-ordering /> in web.xml right under <display-name>: <display-name>JasperServer UI application</display-name> <absolute-ordering />

Problem: You may be getting the following error when trying to run a CVC component on version v7.2.0 that still uses phantomjs to generate SVG image:net.sf.jasperreports.engine.JRRuntimeException: Error while executing the javascript file to generate the SVG image: External process did not end properly; exit value: 502; process output: SCRIPT_ERROR Script timeout producing svg within 3 seconds. Possible script error.Solution: a) In js.config.properties SET net.sf.jasperreports.phantomjs.executable.path instead of com.jaspersoft.jasperreports.components.customvisualization.phantomjs.executable.path b) Add net.sf.jasperreports.phantomjs.options.1=--web-security=false If you are using one of the samples from the community that uses leaflet.css, here are some suggestions. After SVG is generated, it might be failing to render because there might be CSS styles defined, e.g. in leaflet.css, that are not supported. You can remove them. Or, use renderAsPng=true. For example, these are not supported: display: inline-block; and pointer-events: auto;