https://bz.apache.org/bugzilla/show_bug.cgi?id=57129
--- Comment #19 from fchris...@gmail.com <fchris...@gmail.com> --- Hi everybody, We also have some problems due to random jar loading order after we moved from Tomcat 7 to Tomcat 8. Application is not starting and displays error 'signer information does not match signer information of other classes in the same package'. This is because we use birt report runtime library which contains some classes of 'commons.io' package. Under Tomcat 7, 'commons.io' Jar is loaded first, but on Tomcat 8, birt Jar is loaded first, and Tomcat 8 raises an error when it loads 'commons.io' Jar Later. We are talking about two lines of code to add a 'sort', compared to hundred of teams that will lose days and money to debug their applications. That's just unfair. So, please, add the 'sort' to load jars in predictable order. Our application is huge and deployed on more than 20 Prod instances. We cannot use Tomcat 8 because every instance would have some different random errors due to random jar loading order. What is more painful than a random behavior, especialy when the application is running in production, with thousand of users connected ? We are forced to stay on Tomcat 7 :-( -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
