Does below jar support java 11?
ejb.jar - javax.ejb API v.3.1 -Bundle-Vendor: GlassFish Community
jboss-client.jar - 7.1.1.Final - JBoss by Red Hat
JBoss 7.1.1.Final doesn't support Java 8 so it's highly unlikely it would work with Java 11. WildFly 16 should work with Java 11 however.
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 using JBoss7.1.1.Final with jdk 1.8.0_20. When i run standalone. it throws error as
"Unable to read the logging configuration from 'file:/c/jboss-as-7.1.1.Final/jbos s-as-7.1.1.Final/standalone/configuration/logging.properties' (java.io.FileNotFo undException: \c\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\standalone\configurat ion\logging.properties (The system cannot find the path specified))"
JBoss AS 7.1.1.Final does not work with Java 8 https://developer.jboss.org/message/926279#926279.
If you're required to use Java 8 I'd suggest using the JBoss AS 7 predecessor WildFly. Starting with WildFly 10 Java 8 is a requirement.
You can start using OpenJDK 1.8 from JbossAS 7.4.1, Oracle and IBM from JBoss AS 7.3.3 https://access.redhat.com/articles/111663
I heard that JBoss 7 is not certified for FreeBSD - is that correct?
Where can I find a list of supported platforms? (I spent some time googling, but was not successful)
Strictly speaking there is no certified OS for JBoss 7 as only JBoss EAP 6 is supported by Red Hat.
The supported configuration for JBoss EAP 6 (the supported version of community JBoss 7) can be found here: https://access.redhat.com/knowledge/articles/111663
As JBoss is pure java application, a compliant JDK is enough to have a supported system. So if you have the Oracle or IBM JDK running on FreeBSD is will be supported by Red Hat. But they haven't test them with JBoss.
Any way if you want Red Hat support for the EAP you better check with there representative to discus the extends of the support (if the FreeBSD JDK have some compliance bug, they will probably send you back to the JDK supplier. If you chose RHEL with OpenJDK you will have one supplier to blame for any software stack issue, no redirect to another suplier.)
For community JBoss as for other platform, you will be responsible to make it work with your stack. An good first test can be performed by running the standard compliance tests included in the JBoss sources, if it runs on your target platform and JDK it is a good sign that JBoss is working on it.
Certified Support as per Redhat only goes up to 6:
https://access.redhat.com/knowledge/articles/111663
However if you look back at the release docs they have not changed. OS's are the same.