Export of Jaspersoft Graphical Reports fails post upgrade of Google Chrome

Products

• CA Service Management - Service Desk Manager
• CA Service Desk Manager

Issue/Introduction

Post upgrade of Google Chrome to 111.0.5563.65 , any reports which has chart fails to export and below errors are seen in the JasperSoft log 

Error Trace
net.sf.jasperreports.engine.JRRuntimeException: 
com.github.kklisura.cdt.services.exceptions.ChromeServiceException: 
Server responded with non-200 code: 405 - Method Not Allowed. Using unsafe HTTP verb GET to invoke /json/new. 
This action supports only PUT verb.
at com.jaspersoft.jasperreports.highcharts.charts.ChartPdfHandler.exportElement(ChartPdfHandler.java:45) at net.sf.jasperreports.engine.export.JRPdfExporter.exportGenericElement(JRPdfExporter.java:4141) at net.sf.jasperreports.engine.export.JRPdfExporter.exportElements(JRPdfExporter.java:1290) at net.sf.jasperreports.engine.export.JRPdfExporter.exportFrame(JRPdfExporter.java:4060) at net.sf.jasperreports.engine.export.JRPdfExporter.exportElements(JRPdfExporter.java:1286) at net.sf.jasperreports.engine.export.JRPdfExporter.exportFrame(JRPdfExporter.java:4060) at net.sf.jasperreports.engine.export.JRPdfExporter.exportElements(JRPdfExporter.java:1286) at net.sf.jasperreports.engine.export.JRPdfExporter.exportPage(JRPdfExporter.java:1210) at net.sf.jasperreports.engine.export.JRPdfExporter.exportReportToStream(JRPdfExporter.java:1074) at net.sf.jasperreports.engine.export.JRPdfExporter.exportReport(JRPdfExporter.java:691) at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl.exportToPdf(EngineServiceImpl.java:615) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213) 

Environment

JasperSoft 8.1.1

CA Service Desk Manager 17.3 RU22+ and CA Service Desk Manager 17.4

Cause

This error is observed after upgrading Chrome to 111.0.5563.65 version

• Chrome changed the way where a new tab used to be invoked, where it currently only supports the PUT method for endpoint /json/new
• JasperServer 8.1.1 still uses the GET method in their implementation to create a tab and that's where it's throwing the above error
• Tibco has acknowledged this as defect JRL-1820 

Resolution

The fix is available on Jaspersoft 8.1.1 Patch 1

Please contact Broadcom Support for further assistance.