After upgrading Remedy AR System Mid Tier to 20.02.01, Jar file processing errors " Invalid byte tag in constant pool: 19" are seen in the Tomcat logs

Knowledge Article

After upgrading Remedy AR System Mid Tier to 20.02.01, Jar file processing errors " Invalid byte tag in constant pool: 19" are seen in the Tomcat logs
After upgrading to Mid Tier version 20.02.01, the Tomcat logs contain jar file processing errors, " Invalid byte tag in constant pool: 19"
Remedy AR System Server
AR System Mid Tier
Tomcat 7.0.59, upgraded Midtier
After applying the MT 20.02.01 patch, Tomcat 7.0.59 produces the following error in the tomcat-stderr.log
"SEVERE: Unable to process Jar entry [module-info.class] from Jar [jar:file:/C:/Program%20Files/Apache%20Software%20Foundation/apache-tomcat-7.0.59/webapps/arsys2002001/WEB-INF/lib/jakarta.xml.bind-api-2.3.2.jar!/] for annotations
org.apache.tomcat.util.bcel.classfile.ClassFormatException: Invalid byte tag in constant pool: 19 " 

The Mid Tier application still initializes but slow performance may result. 
Tomcat bug: https://bz.apache.org/bugzilla/show_bug.cgi?id=60688
This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers.

To resolve the issue, Tomcat needs to be upgraded to one of the following versions:   
- 9.0.0 onwards
- 8.5.x for 8.5.12 onwards
- 8.0.x for 8.0.42 onwards
- 7.0.x for 7.0.76 onwards

See this article for more instructions on how to upgrade Tomcat supporting the midtier application: 
https://selfservice.bmc.com/casemgmt/sc_KnowledgeArticle?sfdcid=000342204
Remedy AR System Server
AR System Mid Tier
Tomcat 7.0.59, upgraded Midtier
Remedy AR System Server
AR System Mid Tier
Tomcat 7.0.59, upgraded Midtier
Attachment(s):