пн, 9 дек. 2019 г. в 03:58, Nelligan, Steven M <snell...@illinois.edu>:
>
>
> I am trying to rebuild my applications and all of a sudden, I am getting the 
> following error:
>
> Our backend application (from third party has been updated) It is using Java 
> 11.
>
> My tomcat servers are running version 7.34 of tomcat and version 1.7.0_45.

1.7.0_45 is the version of Java? But you say that those web
applications need at least Java 11?

> I have rebuilt and deploy a large number of our Apps; but there are about 4 
> with the following error:
> SEVERE: Unable to process Jar entry [module-info.class] from Jar 
> [jar:file:/G:/Tomcat7/temp/44-bannertools/WEB-INF/lib/jaxb-api-2.3.0.jar!/] 
> for SEVERE: Unable to process Jar entry [module-info.class] from Jar 
> [jar:file:/G:/Tomcat7/temp/44-bannertools/WEB-INF/lib/jaxb-api-2.3.0.jar!/] 
> for annotations
> org.apache.tomcat.util.bcel.classfile.ClassFormatException: Invalid byte tag 
> in constant pool: 19
>         at 
> org.apache.tomcat.util.bcel.classfile.Constant.readConstant(Constant.java:133)

Sounds a lot like this issue that I answered a year ago:
https://stackoverflow.com/questions/52867430/invalid-byte-tag-in-constant-pool-19-error-message

>
> When I first tried this a couple of weeks ago... I needed up trying to 
> upgrade Tomcat to the latest release of 7.0_94

The latest release of Tomcat 7 is 7.0.96, released in July.

> Everything started to fall apart, the javax modules were failing, etc.  I 
> finally realized I was chasing my tail.
> Every time I got one thing working, two more broke.
>
> Restored everything back and went through the rebuild.
>
> I tried to copy the annotation_api.jar file from Tomcat 7.0_94 into tomcat 
> 7.0_45 but nothing would deploy...
>
> I'm at a loss on what could be happening....
>
> Any help would be appreciate any guidance.
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to