I don't use Scala anywhere in my project still getting this error. Cannot find the root cause here.
Kafka uses Scala internally, however Zookeeper isn't used for Consumers any longer, so I suggest you try using a newer version of spring-kafka
Related
I'm working on Oracle JDK 8 to AdoptOpenJDK 11 migration. We are also using Apache Camel 2.20.2. After JDK migration, I'm facing below issues in Camel Context XML file.
not able to recognize exchangePattern parameter
enum value not permissible
Even after having above issues, sometimes my application runs successfully and sometimes it gives error that it is not able to create spring bean. While creating below bean it says trustAllPackages is not a valid parameter which I know is not actually causing the issue.
bean creation
I think the issue is somewhat related to the errors in XML file. My question is:
Is Camel 2.20.2 compatible with JDK 11? If not, are above errors result of this incompatibility?
How to resolve these errors and why isn't this causing issue every time I run my application?
Currently we are using :
AdoptOpenJDK 11
Spring 4.3.11.RELEASE
Camel 2.20.2
ActiveMQ 5.15.0
Maven Build Tool
Thanks in advance.
You can see here what JDK version Camel supports
https://camel.apache.org/manual/latest/what-are-the-dependencies.html
Camel 2.x only supports Java 8.
You need Camel 3.x for Java 11 support.
I am trying to rebuild a grails application using ggts 3.4.0 with groovy 2.1.8, grails 2.3.3 and java 1.7.
In the services files I'm getting these error messages:
Groovy.class grails.transaction.Transactional is not an annotation in #grails.transaction.Transactional
I believe that one of the components listed above is causing this problem. Can someone suggest which particular one and the required version I need?
Incidentally, I've successfully built this in the past with different versions of the various components but I'm not sure what they were. I do have backups - so if you can suggest where can I find details of these builds that would help.
I would welcome any suggestions?
-mike
I've been on a very old version of GAE for a long time. Every time I try to update to the latest version I get this error when deploying it to GCP:
java.lang.IllegalArgumentException: Class file is Java 8 but max supported is
Java 7: org/eclipse/jetty/http/BadMessageException.class in C:\Users\XXXXXXXXXXX\
backendservlet\build\exploded-app\WEB-
INF\lib\jetty-http-9.3.2.v20150730.jar
I think jetty comes with GAE so how do I fix this? When I deploy it locally it runs without errors. It also builds without error. This only happens when deploying to GCP.
My appengine instance is on JAVA 7 runtime so maybe that's the issue? How do I change that? I tried deplying with a different version and name and it still didn't work.
Please help.
Looks like jetty (or at least the version you're using) needs Java 8, which is not supported on GAE: Does Google App Engine support Java 8?.
GAE does not yet support Java 8. If jetty is a dependency of your project, you need to use a version that has source 1.7. Otherwise delete C:\Users\XXXXXXXXXXX\
backendservlet\build\exploded-app\WEB-
INF\lib\jetty-http-9.3.2.v20150730.jar
Wondering if any guru out there could shed an idea on why the following randomly happens.
We have a web application we deploy in Jetty 6.1.26 running on a Linux installation with JRE 1.7_03
Not every time, but every now and then, when Jetty starts up - what appears to be a random class (from our project) seems to be the source of a NoClassDefFound error. If we restart Jetty they problem disappears.
The only pattern that occurs seems to be the classes at the root of the error are populated via JAXB annotations.
To give more of an idea of the frequency it feels this happens 1/50 times, if that.
I would be interested to know the how and the why for this error.
Not sure this can help but we ran into annotations problems with Jetty 8 and java 6.
To make a long story short, annotations processing in that version seem to rely on libasm e.g. bytecode inspection. So we have to be careful with
what we compile our classes with (e.g; JDK version, etc...)
that we do not pull multiple asm/javassist librairies through our dependencies and end up loading the wrong one
I am not familiar with with the way Jetty 6 and Jaxb process annotations but I am actually surprised you can get both running on Java 7. Can you try running you code with Java 6 ?
This issue seems to have been resolved in the latest Cassandra 1.1.2 but I shall leave it here for those still on 1.1.0...
I have just upgraded to Cassandra 1.1.0, compiling it from source, and now I cannot find the CassandraStorage() class anywhere, and the contrib directory has disappeared!
May I know where I could find it? This class is important and utmost essential to the operation of Pig and Hadoop via Cassandra.
Also, executing the pig_cassandra from the examples directory produced the error that the CassandraStorage() could not be found. Is there a way around this?
Thanks!
org.apache.cassandra.hadoop.pig.CassandraStorage