Have a problem. Before start server jboss 7.1.1, I have a problem:
**Error:** JDK 1.7 (or earlier) should be specified either as project SDK or
alternative JRE
I am using jdk 1.8 In project. And I can use only 1.6 JRE for working with JBOSS.
If I used 1.8 at project, and 1.6 jre with jboss, I take error with unsupported major.minor version 52.0.
Can I change jdk for JBOSS on 1.8? And how to do it?
I found the posting below on the JBoss developer developer forum.
The short version is that you would need to backport various bug fixes to JBoss AS 7 in order to get it run on a Java 8 JRE. It would be better / easier to upgrade to Wildfly. (He says.)
Re: AS 7 on Java 8 by Tomaz Cerar Apr 8, 2015 6:18 AM (in response to Matija Vizintin)
Any big reason you cannot upgrade to WildFly 8?
Core issue that prevents boot of AS7 on JDK8 is
https://issues.jboss.org/browse/WFLY-2057
which was fixed by
https://github.com/wildfly/wildfly/commit/fa93ceff49c3e84851cb8b00157e4fbed1d2cdb7
You could apply this commit to
https://github.com/wildfly/wildfly/releases/tag/7.2.0.Final-testsuite-fix
tag and rebuild it.
but, this will only make sure server starts on JDK8, there ware
handful of other fixes / changes that we needed to address to make
sure testsuite passes properly.
In any case, i would recommend you to go with WildFly 8.2.0.Final.
Related
I've recently been restoring my Java EE setup after a computer crash and I thought I'd try Open JDK 16 and Glassfish 6.1.0 but on deploying my application I get the following exception which I've never seen before:
java.io.IOException: com.sun.enterprise.admin.remote.RemoteFailureException: Error occurred during deployment: Exception while deploying the app [myapp-0.0.1-SNAPSHOT] : org.xml.sax.SAXException: Requested schema is not found in local repository, please ensure that there are no typos in the XML namespace declaration.. Please see server.log for more details.
I'm not sure how to resolve that, or maybe I should just roll back to JDK11. I was previously running JDK 1.8.0 and Glassfish 5.1.0
Eclipse Glassfisch 6.1.0 does not currenctly support JDK 16. Only JDK11.
From the documentation found here:
Eclipse GlassFish 6.2.0 is a Jakarta EE 9.1 Compatible Implementation and the latest release of Eclipse GlassFish. It supports Jakarta MVC as a major new feature. Officially supports JDK 11. Runs on JDK 16 (but not fully tested on 16).
Eclipse GlassFish 6.1.0 is a Jakarta EE 9.1 Compatible Implementation and the previous release of Eclipse GlassFish. It's functionally identical to Eclipse GlassFish 6.0.0, but supports JDK 11.
Eclipse GlassFish 6.0.0 is a Jakarta EE 9 Compatible Implementation and and older release of Eclipse GlassFish. This release only supports JDK 8.
So you need to either compile your application with jdk11 or upgrade to glassfish 6.2.0. But be aware: it is not fully tested with jdk 16 yet.
I have a application with Java 1.7 . Trying to integrate Kafka but any Kafka version am trying my jetty(6.1.10) server is not running , throwing error Unsupported major.minor version 52.0: Which is the latest version which can support Java 1.7.
Jetty 6 is deprecated / End of Life.
See: https://www.eclipse.org/jetty/documentation/current/what-jetty-version.html
So, before I answer, know that ALL versions of Java 1.7 are now End of Life, Expired, and not suitable for use in production.
If you need Java 1.7 support, use Jetty 9.2.x series, that was the last version of Jetty to support Java 1.7.
But know that even Jetty 9.2.x is End of Life.
We are planning to migrate our project from Oracle JDK to OpenJDK. I have some questions regarding the same.
After doing some analysis I found that OpenJDK will have a feature release every 6 months which is only supported until the next feature release.It's essentially a continuous stream of releases targeted to developers. Now my question is will it be a good idea to migrate to OpenJDK. Because if the
above statement is correct then we need to upgrade OpenJDK in our application every 6 months
Ref : Differences between Oracle JDK and OpenJDK
What are the basic changes required to do this migration. When I say basic changes, I mean I need to understand in very high level.One thing I know that is
Oracle JDK and Open JDK are having different jar licences. So do I need to replace all Oracle JDK jars with OpenJDK jars as its mentioned in
Migrating to OpenJDK from Oracle JDK ?
Currently we are using :
JDK 1.8
Tomcat 8
Windows Operating System for development. Services gets deployed in linux OS
Maven Build tool
Appreciate your help.
Thanks
Now my question is will it be a good idea to migrate to OpenJDK
For Java 11 you might want to, though by Java 11 they will be almost identical.
So do I need to replace all Oracle JDK jars with OpenJDK jars
I would install a version of OpenJDK and use the JARs which came with it. I wouldn't mix and match them.
JDK 1.8
I am not sure gain anything by migrating Java 8. Oracle Java 8 is still supported at least until Jan 2019. After that, you might not get any update, but you might not with OpenJDK either.
If your concern is getting support for Java 8, I suggest contacting a company which will give commercial support Java 8 such as Azul for what seemed like a reasonable price. https://www.azul.com/downloads/zulu/zulu-windows/
I wanted to upgrade the JDK version of my WebLogic server (10.3.6) from 1.7 to 1.8. What can be the possible steps required to do this?
I have existing weblogic and JDK old versions on Windows platform. I want to update them. But when I search document about update steps on internet, I couldn't find anything. They just mention about installing process.
As you want to update weblogic and jdk version 1.7 to 1.8,
Then you can uninstall both of them.
Then download weblogic 12.2.1 and jdk 8 from following link.
Weblogic download link: weblogic download from here
JDK8 download link: jdk 8 download from here
Then install JDK8 first and then weblogic. Hope it is easy.
From Oracle blogs documentation,
WebLogic 12.2.1 requires Java 8 (JDK 8) as a runtime.
WebLogic 12.1.3 can be used with Java 7 or Java 8. Using WebLogic
12.1.3 with Java 7 caused warnings because of the permspace settings in the WebLogic start scripts. Permspace is removed from JDK 8, so
also these warnings are gone now with WebLogic 12.2.1 and JDK8.
JDK 8 comes with Nashorn JavaScript engine. Try the jjs command line
tool. Read the complete article here.
You can also follow the link: JRE 8 compatibility with weblogic 10.3.6 (11g
I thought the support for Java 1.8 has begun with WLS 12.1.3.
So I assume its not possible/realistic to get wls10.x.x work with a newer jdk as 1.7.x.
https://community.oracle.com/thread/3539686
I recently one of my projects to Spring 4.0.0.RELEASE
After deploying the project to my staging environment, I recognized an Exception with the following Message: bad major version at offset=6. My assumption is, that Sping 4 is not working with Java 6 (which I am forced to, because I can not change it on the system)
(Actually I even was not aware, that a JAR is depending on the Java Version)
Christian Rockrohr My assumption is, that Sping 4 is not working with Java 6
This is wrong assumption.
Spring requires JVM 1.6 or higher, as of Spring 4.0. *****
Java 8 (as well as 6 and 7)
Spring remains compatible with older versions of Java and the JDK: Concretely, Java SE 6 (specifically, a minimum level equivalent to JDK 6 update 10, as released in late 2008) and above are still fully supported. However, for newly started development projects based on Spring 4, we recommend the use of Java 7 or 8.
Read also:
java.lang.UnsupportedClassVersionError: bad major version at offset=6
This look like running a Spring 4 application with JDK 1.5.
Confirmed:
Christian Rockrohr: Indeet, there is Java 1.5 installed on my AS400, it is not Java 1.6. That's is the reason, why Spring did not work. I just returned to Spring 3.1.0.RELEASE and it worked.
*****) http://docs.spring.io/spring/docs/current/javadoc-api/org/springframework/core/JdkVersion.html
jdk 1.6 update-18 or above(latest in 1.6 jdk is jdk-6u-45) versions will support spring 4.0
An exception like this
java.lang.UnsupportedClassVersionError: bad major version at offset=6
Will occure when code is compiled for java version 6, but one try to run it with java 5.