Thanks for your inputs. On Wed, Dec 12, 2018 at 11:26 AM Greg Wilkins <[email protected]> wrote:
> > Kapil, > > sorry, but 50+ production servers is not a good reason for us to give open > source support to an end-of-life version of jetty. It is however, very > much a good reason to have commercial support for jetty, as putting in > effort to help with upgrades from old releases is exactly the kind of thing > we do for our commercial clients. If we gave that away for free to others, > then they wouldn't subscribe and then there would be no Jetty. > > However, mercenary comments aside, I think you are on the right track: > asm3.1 is obviously too old to be able to scan spring4 classes. You need > to work out how to upgrade asm (perhaps not all the way to 7?) in a way > that will work with jetty 8. You may need to build jetty against new > version of asm, as from memory there are API changes (or at least some > statics) that need to be updated. Good luck. > > cheers > > > > > On Wed, 12 Dec 2018 at 15:14, kapil gupta <[email protected]> wrote: > >> Hi, >> >> Currently my application uses Spring 3 with Jetty 8. Now I am upgrading >> tech stack with Spring 4 and Jetty 9.4.14 >> >> With this exercise I want to ensure the code works with Jetty 8 in case >> some of the production servers didnt get upgrade or missed out by chance. >> >> My upgraded application works absolutely fine with Jetty 9.4.14 but when >> I run the same on Jetty 8 to ensure backward compatibility of application >> then I get below error: >> WARN:oeja.AnnotationParser:Problem processing jar entry >> org/springframework/data/auditing/MappingAuditableBeanWrapperFactory$MappingMetadataAuditableBeanWrapper.class >> java.lang.ArrayIndexOutOfBoundsException: 18176 >> at org.objectweb.asm.ClassReader.readClass(Unknown Source) >> at org.objectweb.asm.ClassReader.accept(Unknown Source) >> at org.objectweb.asm.ClassReader.accept(Unknown Source) >> at >> org.eclipse.jetty.annotations.AnnotationParser.scanClass(AnnotationParser.java:658) >> at >> org.eclipse.jetty.annotations.AnnotationParser$2.processEntry(AnnotationParser.java:630) >> at org.eclipse.jetty.webapp.JarScanner.matched(JarScanner.java:155) >> at >> org.eclipse.jetty.util.PatternMatcher.matchPatterns(PatternMatcher.java:82) >> >> >> Below is the asm jar version in jetty servers: >> Jetty 8 - asm3.1 >> Jetty 9.4 - asm 7 >> >> I tried to add explicitly asm 7 jar in my application but still get the >> mentioned error. >> >> I understand that Jetty 8 has met its EOL, and thats why we are upgrading >> the servers. But currently we have 50+ production servers and it might >> happen that server got some error at upgradation time or it gets missed by >> chance. So need to resolve this error in such scenarios. >> >> Please help me with it. >> _______________________________________________ >> jetty-users mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://www.eclipse.org/mailman/listinfo/jetty-users > > > > -- > Greg Wilkins <[email protected]> CTO http://webtide.com > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://www.eclipse.org/mailman/listinfo/jetty-users
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users
