Does mule 3.4 runs with jdk 1.7 & 1.8? Is there any document mentioning about software requirements for running mule 3.4
Actually the question in the title should be the other way around: Does Mule 3.4 supports JDK 1.7 and 1.8?
The answer is that Mule 3.4 does support JDK 1.7 (AKA Java 7) but does not support JDK 1.8 (AKA Java 8). The documentation for 3.4 is archived and it is still available at https://docs.archive.mulesoft.com/mule-user-guide/v/3.4/hardware-and-software-requirements
Note that Mule 3.7.0 is the first release to support Java 8.
Mule 3.4 is a very old release. I would recommend to migrate to a modern, recently released release.
Related
I am trying to find out what is the latest JDK level supported by TomEE 8 or 9. Specifically if JDK 15 will work. The install documentation says only Java 6 or 7 are supported. That seems a bit too old.
The JDK compatibility and support of TomEE is not well documented. The "java compatibility" note in the official documentation is outdated. The Java versions mentioned in the install documentation are an obsolete minimum requirement - propably a copy & paste thingy.
Here is what is known:
TomEE 8.0.9 definitely supports JDK 8, JDK 11, JDK 17
From a short stackoverflow research, for some users JDK 14 or JDK 15 also worked
TomEE 9.x does only support the Jakarta namespace (Jakarta EE 8, Jakarta EE 9.x)
Watch the Release Notes for updates.
According to this documentation page only JDK 8 is supported by TomEE 8.
We have a product that is running fine with JBoss 4.2.2/java 7.
We are now moving to JDK 11. simply added java 11 in the classpath and tried starting the server.
Encountered below error
OpenJDK 64-Bit Server VM warning: Ignoring option MaxPermSize; support was removed in 8.0
-Djava.endorsed.dirs=C:\PathBuilder\GE\EMEA\vp\jboss\lib\endorsed is not supported. Endorsed standards and standalone APIs in modular form
will be supported via the concept of upgradeable modules.
removed below configurations from run.bat and started the server again
-XX:MaxPermSize=128m
"-Djava.endorsed.dirs=%JBOSS_ENDORSED_DIRS%"
now getting below error and which is
interrupting the ear deployment Caused by:
java.lang.ClassNotFoundException: No ClassLoaders found for:
org.omg.CORBA.Object
Is Java 4.2.2 compatible with JDK 11 or we need to update JBoss to 7.2 or latest versions?
can someone help with this or provide related links?
JBoss 4.2 is a very old and outdated version and it only tested with JDK 1.5 and 1.6 version. If you are upgrading your JDK to 11 then you should update the JBoss to 7.3 version which is the latest available GA release from Red Hat.
You can download the jdk files of older versions like jdk6 and then replace JAVA path in the jboss run file from "set JAVA=%JAVA_HOME%\bin\java" to
"set JAVA=C:\Users\jdk1.6.0_45\bin\java"
Of course it's better to upgrade to a higher JBoss version... But in case that's not possible, you can avoid the ClassNotFoundException for org.omg.CORBA.Object by placing rt.jar from Java 8 in your JBoss-libs folder.
With this configuration you can run older JBoss versions with Java 11.
Which version of payara or glassfish should I use with jdk 14?
I've already tried glassfish 5.1.0 and payara 5.201.
Both server support Jdk 11. There isn't clear information available about Jdk 14 yet.
Payara
Offical Reference
With much excitement from users, JDK 11 support has been in technical preview since 5.192.
Glassfish
Official Reference
GlassFish 6.0.0 will support JDK 11+. Support for JDK 8 is not a goal for GlassFish 6.0.0
I am currently involved in a project, that requires migration of 3.5 to 4.x, 4.14 is working fine. I am raising this question because, mule 2 is supporting Java 11, while mule recommended approach is to work on adoptopenjdk 8.0
https://docs.mulesoft.com/release-notes/mule-runtime/mule-4.2.0-release-notes
It is not clear exactly what is the question, however migrating from Mule 4.1.x to 4.2.x doesn't require usually changes to applications. You are free to use Java 8 or 11, though 8 is recommended.
You can upgrade from 4.1 to 4.2 without changing the code or the java version.
So the best approach to migrate would be to use the same configuration as in 4.1
Furthermore, it's a good practice to upgrade the connectors versions of your app.
We have a legacy system that runs on Coldfusion 6.1 with JVM 1.6.0 build 24. It appears that TLSv 1.1 was added in build 111. Is it possible to get Coldfusion 6.1 to work with that build (or higher) and what would I have to do?
TLS 1.1 is only supported in Java 1.8 on CF10 (Oddly 1.7 and above in CF11)
I dont think CF 6.1 will work properly on higher versions of JDK. You may want to try to upgrade it to 1.8 to see if that helps.
See this Adobe Blog as a starting guide to updating your Java: http://blogs.coldfusion.com/post.cfm/how-to-change-upgrade-jdk-version-of-coldfusion-server
Also see this: http://www.coldfusionmuse.com/index.cfm/2014/12/8/colfusion-jvm-versions-sslv3-tls