Open axelfontaine opened 10 years ago
It appears that Spring-loaded has some issue with Java 8 lambas. The line of code that is blowing up has a more descriptive message in the master branch:
@Override
public void visitInvokeDynamicInsn(String name, String desc, Handle bsm, Object... bsmArgs) {
// TODO *shudder* what about invoke dynamic calls that target reflective APIs
int classId = typeRegistry.getTypeIdFor(slashedclassname, true);
if (classId==-1) {
throw new IllegalStateException("Unable to find classId for "+slashedclassname+" referenced from invokedynamic in "+this.methodname+"()");
}
// Initially only rewriting use of INVOKEDYNAMIC to support Lambda execution
// TODO support the more general invokedynamic usage
The class being loaded that is causing Sprint-loaded grief is com.zaxxer.hikari.pool.HikariPool
, and it does indeed use lamdas in the Java 8 incarnation.
If you want to work around this issue, drop back to using the HikariCP-java6
artifact, it is functionally the same as the Java 8 HikariCP
artifact.
Environment:
Stacktrace:
Offending code: