-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JavaAssist and Java 8 #59
Comments
I am unable to reproduce this issue on Java 8. The pom compiles and all of the tests run. Is there a longer stack trace? The one above terminates at a I checked in a minor change into the |
I was using 1.3.5, Let me try it with 1.3.6 |
This is 1.3.5 again, The 1.3.6-snapshot dependency didn't work through maven. I can build it if needed. Here's another stack trace, where I got a different error: 17:07:01.617 478551 [pool-4-thread-14] ERROR com.zaxxer.hikari.proxy.JavassistProxyFactory - Fatal exception during proxy generation |
That error seems to be caused by having debug logging enabled and the executing process not having write permissions to Re: 1.3.6-SNAPSHOT, yes you'll have to build it to test it:
Then use 1.3.6-SNAPSHOT as a dependency in your pom. |
Has anyone mentioned any surefire errors when building this? I'm getting strange issues with maven: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on project HikariCP: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test failed: Unable to load the mojo 'test' in the plugin 'org.apache.maven.plugins:maven-surefire-plugin:2.17'. A required class is missing: org/apache/maven/plugin/surefire/SurefireReportParameters I tried adding it manually to the pom, but the same error came up. Tried clearing out my /.m2/org/apache/maven directory and reloading them, but they download with [WARNING] checksum issues. I think this is a maven bug. |
Here's the maven version: |
I haven't had any reports of this issue. But in the past when i've had maven issues, I just wipe out .m2 completely and allow it to rebuild. |
I'm getting a strange error when instantiating hikariCP when using java 8.
Here's a description of the problem:
http://www.symphonious.net/2014/03/21/javassist-java-8-invalid-constant-type-15/
The stacktrace is here:
at com.zaxxer.hikari.HikariConfig.(HikariConfig.java:82)
...
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: java.io.IOException: invalid constant type: 15
at com.zaxxer.hikari.proxy.JavassistProxyFactory.(JavassistProxyFactory.java:63)
... 6 more
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: java.io.IOException: invalid constant type: 15
at com.zaxxer.hikari.proxy.JavassistProxyFactory.(JavassistProxyFactory.java:103)
at com.zaxxer.hikari.proxy.JavassistProxyFactory.(JavassistProxyFactory.java:57)
... 6 more
Caused by: java.lang.RuntimeException: java.io.IOException: invalid constant type: 15
The text was updated successfully, but these errors were encountered: