Skip to main content
New Participant
September 24, 2024
Question

Appdynamics issue when upgrade to Appian 24.2

  • September 24, 2024
  • 4 replies
  • 0 views

We are using AppDynamics for monitoring, post upgrade to 24.2 version from 23.2  we see below error in tomcat logs and we see 404 error when we try opening the processmodel.

2024-09-24 14:11:47 SEVERE [main] org.apache.catalina.core.StandardContext.loadOnStartup Servlet [action] in web application [/suite] threw load() exception
java.lang.VerifyError: Inconsistent stackmap frames at branch target 56
Exception Details:
Location:
com/appiancorp/common/struts/DelegateActionServlet.<init>()V @56: putfield
Reason:
Type 'com/appiancorp/common/struts/AppianWebMvcActionServlet' (current frame, stack[1]) is not assignable to 'javax/servlet/http/HttpServlet' (stack map, stack[1])
Current Frame:
bci: @46
flags: { }
locals: { 'com/appiancorp/common/struts/DelegateActionServlet' }
stack: { 'com/appiancorp/common/struts/DelegateActionServlet', 'com/appiancorp/common/struts/AppianWebMvcActionServlet' }
Stackmap Frame:
bci: @56
flags: { }
locals: { 'com/appiancorp/common/struts/DelegateActionServlet' }
stack: { 'com/appiancorp/common/struts/DelegateActionServlet', 'javax/servlet/http/HttpServlet' }
Bytecode:
0000000: 2ab7 0001 2a12 07b8 0009 c000 07b5 000f
0000010: 2a12 15b8 0009 c000 15b6 0017 b500 1b2a
0000020: 2ab4 001b 9900 0dbb 001e 59b7 0020 a700
0000030: 0abb 0021 59b7 0023 b500 24b2 0028 2ab4
0000040: 001b 9900 0812 2ca7 0005 122e ba00 3000
0000050: 00b6 0034 2abb 0021 59b7 0023 b500 3a2a
0000060: bb00 1e59 b700 20b5 003e b1
Stackmap Table:
full_frame(@49,{Object[#16]},{Object[#16]})
full_frame(@56,{Object[#16]},{Object[#16],Object[#221]})
same_locals_1_stack_item_frame(@74,Object[#53])
full_frame(@76,{Object[#16]},{Object[#53],Object[#178]})

at java.base/java.lang.Class.getDeclaredConstructors0(Native Method)
at java.base/java.lang.Class.privateGetDeclaredConstructors(Class.java:3373)
at java.base/java.lang.Class.getConstructor0(Class.java:3578)
at java.base/java.lang.Class.getConstructor(Class.java:2271)
at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:144)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:865)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:805)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4631)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4924)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:171)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:683)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:658)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:712)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:635)
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1889)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:123)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:530)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:421)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1629)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:303)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:114)
at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402)
at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:345)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:893)
at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:845)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:171)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1332)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1322)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:145)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:866)
at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:240)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:171)
at org.apache.catalina.core.StandardService.startInternal(StandardService.java:433)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:171)
at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:921)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:171)
at org.apache.catalina.startup.Catalina.start(Catalina.java:757)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:345)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:473)
2024-09-24 14:11:47 INFO [main] org.apache.catalina.startup.HostConfig.deployDescriptor Deployment of deployment descriptor [/opt/middleware/appian/tomcat/apache-tomcat/conf/Catalina/localhost/suite.xml] has finished in [450,375] ms

we see below when we open the process model.

Error 404 - Page Not Found

Sorry, we can not find what you are looking for.

    4 replies

    stefanhelzle0001
    Brainy
    September 24, 2024

    I suggest to open a support case.

    New Participant
    September 25, 2024

    Appian response below

     As KB-1414 [1] mentions, external monitoring agents can introduce unexpected behavior in Appian. In order to resolve this issue, please disable the external monitoring agent and clear the application server cache. Unfortunately as AppDynamics is an external monitoring agent, and is out of scope for Appian Support, we are unable to provide guidance/workarounds outside of the above. Please let me know if you have any additional questions or concerns. [1] community.appian.com/.../kb-1414-dynatrace-interfering-with-appian-components

    somasundaram.d
    September 25, 2024

    Please reach out to Appian Support

    New Participant
    September 25, 2024

    Appian response below

     As KB-1414 [1] mentions, external monitoring agents can introduce unexpected behavior in Appian. In order to resolve this issue, please disable the external monitoring agent and clear the application server cache. Unfortunately as AppDynamics is an external monitoring agent, and is out of scope for Appian Support, we are unable to provide guidance/workarounds outside of the above. Please let me know if you have any additional questions or concerns. [1] community.appian.com/.../kb-1414-dynatrace-interfering-with-appian-components