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.
Related
I want to change log4j version from 2.8.2 to 2.17.2 for fix vulnerable. I have changed the jars underneath of mule-enterprise-standalone-3.9.4\lib\boot but i am getting below error.
Please advise what else need to to changed.
I have added below jars though i'm getting below error.
log4j-slf4j-impl-2.17.2 ,
log4j-jul-2.17.2 ,
log4j-jcl-2.17.2 ,
log4j-api-2.17.2 ,
log4j-1.2-api-2.17.2
I have referenced the question : log4j2 for MULE 3 CE patch update
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=1024m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=1024m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: Using the ParNew young collector with the Serial old collector is deprecated and will likely be removed in a future release
Exception in thread "main" java.lang.NoSuchMethodError: com.lmax.disruptor.dsl.Disruptor.<init>(Lcom/lmax/disruptor/EventFactory;ILjava/util/concurrent/ThreadFactory;Lcom/lmax/disruptor/dsl/ProducerType;Lcom/lmax/disruptor/WaitStrategy;)V
at org.apache.logging.log4j.core.async.AsyncLoggerConfigDisruptor.start(AsyncLoggerConfigDisruptor.java:212)
at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:303)
at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:137)
at org.apache.logging.slf4j.Log4jLoggerFactory.getContext(Log4jLoggerFactory.java:55)
at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:47)
at org.apache.logging.slf4j.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:33)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:358)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:383)
at org.mule.module.boot.LicenseKeyHandler.<clinit>(LicenseKeyHandler.java:23)
at org.mule.module.reboot.MuleContainerBootstrap.handleLicenseKey(MuleContainerBootstrap.java:221)
at org.mule.module.reboot.MuleContainerBootstrap.main(MuleContainerBootstrap.java:69)
JVM exited while loading the application.
Mule versions are developed with a specific log4j2 target version. Changing the version directly can lead to unpredictably errors like you are experiencing. To avoid the vulnerabilities in log4j2 without having compatibility issues you need to follow the instructions in MuleSoft Help Center that are available to Enterprise Edition customers. Note that the version that you are using is an Enterprise Edition release, not a Community Edition release. Alternatively downloading the last released build for your version may already incorporate the patches to fix the vulnerabilities. Although I would recommend to use Mule 3.9.5 since it is the final release of Mule 3.x and has additional bug fixes compared to 3.9.4.
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.
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 downloaded and installed jdk 11 and am now trying to install netbeans 8.2. But i get an error which states "JAVA SE was not found on this computer.Make sure JDK is properly installed and run installer again. You can specify valid JDK location using --javahome installer argument."
I created a JAVA_HOME variable and set the value to "C:\Program Files\Java\jdk-11.0.1\bin" and set the same value for PATH variable as well.
How do i fix this?
You face a couple of issues:
NetBeans 8.2 requires JDK 8, and it will not work with any version of Java > 8.
NetBeans does not yet support JDK 11, though the release of a new version which does (NetBeans 10) is imminent.
The easiest approach would be to remove JDK 11 (unless you need it for other reasons apart from NetBeans), install Java 8 then reinstall NetBeans 8.2. It used to be possible to download NetBeans 8.2 bundled with Java 8, but if you try that now Oracle will just redirect you to the Apache NetBeans 9.0 web site.
There is a newer release of NetBeans than 8.2, Apache NetBeans 9.0. While it supports Java 9 and Java 10, it also does not support Java 11.
Updated to reflect that NetBeans 10 was released on December 27, 2018:
If you really want to use Java 11 with NetBeans you can download the latest Jenkins build of the beta version of NetBeans 10 at your own risk.
If you want to use Java 11 with NetBeans then download NetBeans 10.0. The download is a zip file and it works on all platforms.
Find netbeans.conf file in C:\Program Files\NetBeans 8.1 RC\etc.
In that atlas you'll find the netbeans_jdkhome. Set it accordingly.
You can specify the JDK to use by installing from the command line. So install a JDK 8 (e.g. Azul Zulu Open JDK 8) and then launch the netbeans installer:
netbeans-8.2-javaee-windows.exe --javahome "c:\Program Files\Zulu\zulu-8"
Once the installation starts, you will be asked which JDK to use for the IDE; make sure to choose your JDK 8 instead of the JDK 11. I have used this to install NetBeans 8.2RC successfully on Windows 10.
Need to integrate JBoss 7.1.1 to MyEclipse 8.5 any ideas how can i doit cause i can't see JBoss 7.x.x for this MyEclipse version. Thanks in advance!
You could try using the connector for an earlier release of JBoss and see if that works (just specify the install location for JBoss 7.1.
For full support, you'd be better off moving to the latest release of MyEclipse (2013). A MyEclipse license is not based on the release, so you can install any release during the period of your license.