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.
Related
I want to change java version in mule standalone server that means different java version from what set in Java home. I have referred example How to configure Mule ESB (mule.bat) with different Java Version? but I'm still getting an error. Please help.
I have added specified java version in wrapper.java.command as per example but still referring to java home version not specified wrapper.conf file.
Appreciate your help.
Mule Version : 3.9.4
confg/wrapper.conf
Under Wrapper Properties
wrapper.java.command=C:/java/jdk8u262/bin/java
I didn't change mule.bat.
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
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
I'm getting the following exception for Dandelion datatables when the application is deployed on Tomcat 8. The application works just fine on Tomcat 7. I've searched everywhere but can't find a resolution.
Snippet of the trace on Tomcat 8:
org.apache.catalina.core.ApplicationDispatcher.invoke Servlet.service() for servlet jsp threw exception
java.lang.NullPointerException
at com.github.dandelion.datatables.core.configuration.Configuration.applyConfiguration(Configuration.java:283)
at com.github.dandelion.datatables.jsp.tag.TableTag.doStartTag(TableTag.java:102)
at org.gvnix.datatables.tags.RooTableTag.doStartTag(RooTableTag.java:133)
at org.apache.jsp.tag.webdatatables.table_tagx.doTag(table_tagx.java:1346)
Dandelion in my web app is embedded in the "gvNix" dependencies. The gvNix version is 1.4.0.RELEASE, which I assume includes the 0.10.1 version of Dandelion. The configuration being used is default. The application is packaged and deployed using Maven.
Currently, gvNIX uses a Dandelion Datatables 0.9.2 custom-version which includes some patches than hadn't been applied until 0.10.0 (it was due to release-time problems).
As far I know, we didn't make any test over Tomcat 8, so I think you found a bug ;-). If you want, you could report it on github project. Now a days, I can't provide you any workaround to run it on Tomcat 8.
I know that is planed to update Dandelion version but I can't provide you any schedule.
Regards.
I created an issue in the GitHub but I also managed to workaround the problem. Please refer to https://github.com/gvSIGAssociation/gvnix/issues/28