Is there a way we can specify the JDK version we are running on? Specifically, I have a java app (non webapp) that has an incompatibility with 1.6.0_35 and is erroring out for me on CloudBees. The package recommends 1.6.0_27, is that possible to specify at deployment time?
you can specify the version with -Rjava_version on the command line - however, fine grained versions are not available (as we tend to update those) - it is more just 1.6, 1.7 or 1.8 lineage. I would recommend in that case -Rjava_version=1.7.
Related
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.
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
I am trying to run my pharo2.0 application on CentoOS which was previously been installed in a mac. The original version is pharo2.0 so I need to run the same image CentoOS too, but I get an error which says this below :
/lib/libc.so.6: version `GLIBC_2.15' not found (required by xxxxx)
Should I be trying to upgrade the CentoOS and see if pharo2.0 works or port my whole application to a later version of pharo?
There is now a VM build especially for systems with an older libc version. In fact there is a build for Centos specifically (which has a slight variation in linkages from Debian), the latest version of which is permalinked here. See http://pharo.org/download#custom for more info.
I am attempting to start Apache Geronimo using the command:
./bin/geronimo run
When I do this, it spins for a minute, issues the message "Main not found" and exits.
This article suggests that it is a system resource issue:
http://apache-geronimo.328035.n3.nabble.com/jira-Created-GERONIMO-5551-Failing-to-start-the-server-with-the-error-quot-Main-not-found-quot-td1324013.html
I have tried it on both an Amazon EC2 box (running Linux), and an Azure A1 box (running Windows Server), and I have tried the "Full Profile Release" and "Web Profile Release" of Geronimo, all with no change.
I'm at a complete loss as to what I could try. I am led to believe that the EC2 box, at the very least, should have the muscle to run Geronimo.
Any suggestions would be welcome.
Version 3 of Apache Geronimo is designed to run on JRE 1.7 instead of JRE 1.8. As stated in the other answers, the issue was caused by Geronimo being run on JRE 1.7 instead of 1.8.
You are not limited to JRE 1.7 and earlier in order to run Geronimo though. Therefore, all you have to do is to rename or copy the property jre-1.7 in the file etc/config.properties in your installation to jre-1.8. Afterwards, you should be able to run Geronimo without an error.
This has a huge benefit, since now you will be able to run programs on Geronimo that use Java 8 features.
It turns out that the issue is that I had the wrong version of the JDK installed. I had installed the most recent version (8), but Geronimo apparently won't work with that. When I instead installed version 6, everything worked fine.
I was getting the same error with Java 8. I tried the latest version of Java SE 7 and that resolved the problem. So I wouldn't use Java 6, since it is and has been out of support for awhile now (read: security issue).
I have been using the dynamic code evaluation for dynamic loading of my changed classes in my Jboss server ,
I have found this tool very helpful and interesting , but it have a problem that it works with jdk 1.6 , but As i am trying to use java 7 in my project it fails .
Can anyone suggest similar type of tool with java7 support
I suggest using... the Dynamic Code Evolution VM for Java 7 :) The DCEVM web site is not up to date and the version available for download there doesn't work with the latest versions of Java 7. For some time the Mercurial repository contained a more recent version and it has been eventually forked on Github where binaries for Windows and Linux are provided. On Debian/Ubuntu DCEVM is also available after installing the openjdk-7-jre-dcevm package.