Overview
Bring the ease of access of Appian logs from Appian Cloud to Self-Managed Clients.
NOTE: This plug-in is not approved for Cloud deployment.
Key Features & Functionality
Servlet exposing Appian logs to the Designer group.
Appian has resolved this internally with v1.0.7, which I assume will be available here shortly.
We are v1.0.6 and just upgraded the platform to 24.2 and the servlet is failing with a 500 error. Is this a known issue?
2024-05-31 13:06:39 INFO [ajp-nio-0.0.0.0-8009-exec-1] org.apache.catalina.core.ApplicationContext.log Logs Servlet: DefaultServlet.serveResource: Serving resource '/plugins/servlet/logs/' headers and data2024-05-31 13:06:39,244 [ajp-nio-0.0.0.0-8009-exec-1] ERROR com.atlassian.plugin.servlet.ServletModuleContainerServlet -jakarta.servlet.ServletException at com.appiancorp.plugins.PublicApiLoggingHttpServlet.service(PublicApiLoggingHttpServlet.java:47) at com.atlassian.plugin.servlet.ServletModuleContainerServlet.service(ServletModuleContainerServlet.java:49) at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:658) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:150) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
Caused by: java.lang.UnsupportedOperationException at com.appiancs.plugins.servlet.logs.SharedLogsResourceRoot.getContext(SharedLogsResourceRoot.java:156) at com.appiancs.plugins.servlet.logs.DefaultServlet.serveResource(DefaultServlet.java:1057) at com.appiancs.plugins.servlet.logs.DefaultServlet.doGet(DefaultServlet.java:510)
2024-05-31 13:12:02,713 [ajp-nio-0.0.0.0-8009-exec-6] ERROR com.appiancorp.ap2.PortalResponse - Error: 500 Message: null
In the 23.2 release, Appian introduced modernized file management APIs that offer a cleaner abstraction layer for easier file handling within Appian. We simultaneously announced that we are deprecating some older APIs. We are aware of the utilization of deprecated APIs within some AppMarket plug-ins that work with documents. As part of our commitment to ensuring compatibility, we anticipate all Appian-authored plug-ins currently using deprecated APIs to be updated for API compatibility by the 24.1 General Availability (GA) release. We also proactively work with Partner plug-in authors to ensure all AppMarket plug-ins have optimal performance and functionality. If you have any questions or require AppMarket assistance, please don't hesitate to reach out by sending an email to appmarket@appian.com.
In the 23.2 release, Appian introduced modernized file management APIs that offer a cleaner abstraction layer for easier file handling within Appian. We simultaneously announced that we are deprecating some older APIs. We are aware of the utilization of deprecated APIs within some AppMarket plug-ins that work with documents. As part of our commitment to ensuring compatibility, we anticipate all Appian-authored plug-ins currently using deprecated APIs to be updated for API compatibility by the 24.1 General Availability (GA) release. We also proactively work with Partner plug-in authors to ensure all AppMarket plug-ins have optimal performance and functionality.
It is planned a new version for this plugin?The heath check report continues saying that is using deprecated API's.In a future this can be a problem. "Logs-Servlet (logs-servlet) references deprecated Appian APIs[deprecated] com.appiancorp.suiteapi.common.ServiceLocator.getGroupService(com.appiancorp.services.ServiceContext)"
It looks like that even you have updated the plugin it continues using deprecated API's.This message appear at the healthcheck report with the plugin at the 1.0.2 version:
Logs-Servlet (logs-servlet) references deprecated Appian APIs[deprecated] com.appiancorp.suiteapi.common.ServiceLocator.getGroupService(com.appiancorp.services.ServiceContext)
Can this be fixes? thank you.