Jboss 7.1.1 startup throws Unable to read the logging config - jboss7.x

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

Related

Is jboss 4.2.2 GA compatible with java 11?

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.

Weblogic 12.2.1 Application server JDK 11 support

Creating a new domain in Weblogic 12.2.1 server with Oracle JDK 11 fails
What we have tried:
As JDK 8 is already in End of life,
We have upgraded our java servlet based web application to compile with JDK 11.
Tried to deploy in Tomcat 9, it is working fine.
To deploy the same war in WebLogic, When we try to create a new domain in Weblogic 12.2.1 server with Oracle JDK 11, it fails with the below error.
Weblogic Error while creating new domain
WebLogic Server 12c does not support and does not run under Java >= 9. You will have to wait for next major release in 2020.
Check the Certification Matrix for details.
WebLogic Server 14c (14.1.1.0.0) supports JDK 11.
WebLogic Server 12.2.1.4 supports Oracle JDK 8 and Oracle JDK 11

How to configure jboss to run as a service in rhel 7

How to run jboss as a service if installed using zip package ?
You can check the coresponding JBoss EAP 7 documentation Installation Guide - Configuring JBoss EAP to run as a Service for detailed information.

Does ejb.jar and jboss-client.jar support java 11?

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.

Tomcat7 - creation of jvm failed Windows 10

I installed tomcat 7 with Java 11.
When I try to start the tomcat service it crush.
I get an error the creation of jvm failed.
Tomcat 7 is not compatible with Java 11.
I downgraded the Java to 8, now it's working.