On 20/07/2011 03:55, Matthew Tyson wrote:
Hey guys,
tomcat 7.0.19
Java 1.6.0_22
CentOS 5.6
I just switched the web.xml to servlet 3.0 (from a app running servlet 2.4
previously without issue) and now I'm seeing the following error (turned on
fine logging in the util class):
FINE:
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
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
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).
1. Are you using Tomcat downloaded from tomcat.apache.org?
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
org.apache.tomcat.util.bcel.classfile.ClassFormatException:
Invalid byte tag in constant pool: 60
The above message is created by
o.a.tomcat.util.bcel.classfile.Constant#readConstant(...). There is a
switch() and default: label results in this exception being thrown.
Expected values there are
Konstantin,
I may have to give the debugger a try - thanks for the info.
Matt
On Wed, Jul 20, 2011 at 1:02 PM, Konstantin Kolinko
knst.koli...@gmail.comwrote:
org.apache.tomcat.util.bcel.classfile.ClassFormatException:
Invalid byte tag in constant pool: 60
The above message is created by
Hey guys,
tomcat 7.0.19
Java 1.6.0_22
CentOS 5.6
I just switched the web.xml to servlet 3.0 (from a app running servlet 2.4
previously without issue) and now I'm seeing the following error (turned on
fine logging in the util class):
FINE: Scanning JAR