groovy-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jochen Theodorou <blackd...@gmx.org>
Subject Re: Illegal type in constant pool
Date Sun, 10 Jul 2016 20:08:47 GMT
On 10.07.2016 16:30, NETEASE wrote:
> Hi, the following stack trace is thrown when I upgraded groovy(indy)
> from 2.3.11 to 2.4.7 and replaced groovy-eclipse-compiler
> with GMavenPlus which supports INDY feature.
> Caused by: java.lang.VerifyError: (class:
> com/xxx/yyydaemon/ScheduleTransferChannelTask, method: executeTask
> signature:
> (Lcom/xxx/yyy/client/executor/simple/processor/SimpleJobContext;)V)
> Illegal type in constant pool
> the output of javap -v ScheduleTransferChannelTask is the following:
> Classfile
> /home/wangyin.wy/com/xxx/yyydaemon/ScheduleTransferChannelTask.class
>    Last modified 2016-7-8; size 10220 bytes
>    MD5 checksum f0262d363ad22b0e64e8e3e59d344cbc
>    Compiled from "ScheduleTransferChannelTask.groovy"
>
> Has anyone seen the same issue and share how to solve it?
> Thanks~

I think without looking at the actual bytecode there is no chance to 
tell what the problem is. "Illegal type in constant pool" is a very 
generic error, and it could mean anything from using the wrong invoke to 
a wrong ldc somewhere...

bye Jochen


Mime
View raw message