javax.xml.parsers.FactoryConfigurationError running JBoss AS 7.1 with Java 7 update 171

Question

Upgrading Java from 7u161 to 7u171 prevents JBoss AS 7.1.1.Final from starting. I know JBoss AS 7.1.1 is EOL but for compatibility reasons, we still need to run this version.

Very early in the startup, a NullPointerException occurs in some JBoss method. Following is the exception:

Exception in thread "main" javax.xml.parsers.FactoryConfigurationError: Provider __redirected.__SAXParserFactory could not be instantiated: java.lang.NullPointerException
[...]
Caused by: java.lang.NullPointerException
at __redirected.__RedirectedUtils.loadProvider(__RedirectedUtils.java:94)

The full stack is here.

I have tested both Oracle JDK 7 Update 171 (Patch 27217226) and Oracle JDK 7 Update 171 b31 (Patch 27334355), with the same results. — David Le Borgne, Jan 23 '18 at 14:22
This question was also asked in Oracle Community : https://community.oracle.com/message/14679602 — David Le Borgne, Jan 23 '18 at 14:30

score 91 · Accepted Answer · answered Feb 01 '18 at 11:20

91

Could you try upgrading jboss-modules.jar (found in the root folder of the jboss-as binary distribution) to 1.1.5.GA? The version of jboss-modules which comes with jboss-7.1.1.Final is 1.1.1.GA and it has a few issues with initialisation order and multiple-initialisation which could be causing the issue.

answered Feb 01 '18 at 11:20

effegi

926
7
3

19

Replacing the original jboss-modules.jar (1.1.1.GA) with [jboss-modules-1.1.5.GA.jar](http://repo1.maven.org/maven2/org/jboss/modules/jboss-modules/1.1.5.GA/jboss-modules-1.1.5.GA.jar) solved the issue. Thanks. – David Le Borgne Feb 01 '18 at 15:57
download the jar file from here ( http://www.java2s.com/Code/Jar/j/Downloadjbossmodules115gajar.htm ) and rename it to jboss-module.jar and replace the original jar. – Kartik ganiga Sep 25 '19 at 08:54

score 13 · Answer 2 · answered Dec 03 '18 at 18:14

13

Are you sure you are using a jdk 1.7?

This issue can happen when you try to start Jboss with java version > 1.7, try to check your JDK installation folder.

answered Dec 03 '18 at 18:14

Mike D3ViD Tyson

1,701
1
21
31

Spot on! Must check the JAVA_HOME in the environment variables too. – Borjovsky Apr 04 '19 at 15:17
1

`OpenJDK 1.7.0_261` caused this, too. – Attacktive Nov 02 '20 at 07:29

score 6 · Answer 3 · answered Aug 20 '18 at 10:35

6

Environment as Follow: Jboss: JBoss AS 7.1.1.Final, OS: Ubuntu 16.04.1, and, java: 1.8.0_181.

I have downloaded jboss-modules-1.1.5.GA.jar and replace to jboss-modules.jar at JBOSS_HOME. It worked for me.

answered Aug 20 '18 at 10:35

Umy Angel

61
1
3

score 1 · Answer 4 · answered Oct 31 '18 at 11:26

I had same issue on my Production Server

My Environment :-

JBoss AS 7.1.1.Final      
Red Hat Enterprise Linux 6.5     
java: 1.7.0_181

Even i had jboss-modules.jar which comes by default in JBoss AS 7.1.1.Final ,
So i downloaded jboss-modules-1.1.5.GA.jar , renamed it as jboss-modules.jar
and replaced it with original jboss-modules.jar.

javax.xml.parsers.FactoryConfigurationError running JBoss AS 7.1 with Java 7 update 171

4 Answers4

Linked