On 20/07/2011 21:37, Matthew Tyson wrote: > java -version: > > java version "1.6.0_26" > Java(TM) SE Runtime Environment (build 1.6.0_26-b03) > Java HotSpot(TM) Server VM (build 20.1-b02, mixed mode) > > We just upgraded it from 1.6.0_22 to see if it would address this problem > (it didn't).
Are you sure that is the version of Java that Tomcat is starting with? Mark > >> 1. Are you using Tomcat downloaded from tomcat.apache.org? > > Yes. > >> 3. Maybe if you enable debug logging in "org.apache.tomcat.util.bcel" >> you will able to provide some context where the issue happens? > > Did that - its actually how I got the name of the files failing. > > Thanks for taking a look. > > Matt > > > On Wed, Jul 20, 2011 at 11:43 AM, Konstantin Kolinko <knst.koli...@gmail.com >> wrote: > >> 2011/7/20 Matthew Tyson <matthewcarlty...@gmail.com>: >>> Adding that to the skip list definitely prevented that error, but I'm >>> getting many jars with the same problem. I thought I could maybe get >> away >>> with just skipping them all, but I'm starting to see some jars that have >>> taglibs in them (and so need to be scanned). >>> >>> All these jars are giving the same error: >> >> >> >> 2. Where that JDK 1.6.0_22 is from? What is shown by `java -version`? >> >> 3. Maybe if you enable debug logging in "org.apache.tomcat.util.bcel" >> you will able to provide some context where the issue happens? >> >> Best regards, >> Konstantin Kolinko >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
