Skip to Main Content
Forums

Java EE (Java Enterprise Edition) General Discussion

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

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

David Le BorgneJan 23 2018 — edited Feb 1 2018

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 :

Calling "C:\PRODUCT\jboss-as-7.1.1\bin\standalone.conf.bat"

"JAVA_OPTS already set in environment; overriding default settings with values: -server -Xrs -Xms256m -Xmx512m -XX:MaxPermSize=128m -Dproduct.home=C:\PRODUCT -Djboss.server.base.dir=C:\PRODUCT\jboss-as-7.1.1\standalone -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djboss.server.default.config=standalone.xml "

===============================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: C:\PRODUCT\jboss-as-7.1.1

  JAVA: C:\Java\jdk1.7.0\bin\java

  JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -server -Xrs -Xms256m -Xmx512m -XX:MaxPermSize=128m -Dproduct.home=C:\PRODUCT -Djboss.server.base.dir=C:\PRODUCT\jboss-as-7.1.1\standalone -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djboss.server.default.config=standalone.xml

===============================================================================

Exception in thread "main" javax.xml.parsers.FactoryConfigurationError: Provider __redirected.__SAXParserFactory could not be instantiated: java.lang.NullPointerException

at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:132)

at jdk.xml.internal.JdkXmlUtils.getSAXFactory(JdkXmlUtils.java:231)

at jdk.xml.internal.JdkXmlUtils.<clinit>(JdkXmlUtils.java:77)

at com.sun.org.apache.xerces.internal.impl.xs.opti.SchemaParsingConfig.<init>(SchemaParsingConfig.java:319)

at com.sun.org.apache.xerces.internal.impl.xs.opti.SchemaParsingConfig.<init>(SchemaParsingConfig.java:254)

at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.<init>(XSDHandler.java:473)

at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.<init>(XSDHandler.java:480)

at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.<init>(XMLSchemaLoader.java:357)

at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.<init>(XMLSchemaLoader.java:292)

at com.sun.org.apache.xerces.internal.jaxp.validation.XMLSchemaFactory.<init>(XMLSchemaFactory.java:96)

at javax.xml.validation.SchemaFactoryFinder._newFactory(SchemaFactoryFinder.java:238)

at javax.xml.validation.SchemaFactoryFinder.newFactory(SchemaFactoryFinder.java:145)

at javax.xml.validation.SchemaFactory.newInstance(SchemaFactory.java:202)

at __redirected.__SchemaFactory.<clinit>(__SchemaFactory.java:66)

at __redirected.__JAXPRedirected.initAll(__JAXPRedirected.java:88)

at org.jboss.modules.Module$1.run(Module.java:85)

at org.jboss.modules.Module$1.run(Module.java:72)

at java.security.AccessController.doPrivileged(Native Method)

at org.jboss.modules.Module.<clinit>(Module.java:72)

at org.jboss.modules.Main.main(Main.java:255)

Caused by: java.lang.NullPointerException

at __redirected.__RedirectedUtils.loadProvider(__RedirectedUtils.java:94)

at __redirected.__RedirectedUtils.loadProvider(__RedirectedUtils.java:87)

at __redirected.__SAXParserFactory.<init>(__SAXParserFactory.java:102)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

at java.lang.reflect.Constructor.newInstance(Constructor.java:526)

at java.lang.Class.newInstance(Class.java:383)

at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:179)

at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:147)

at javax.xml.parsers.FactoryFinder.find(FactoryFinder.java:219)

at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:126)

... 19 more

This question was also asked on Stack Overflow : https://stackoverflow.com/questions/48403832/javax-xml-parsers-factoryconfigurationerror-running-jboss-as-7-1-with-java-…

Comments

Karthick2003
945400 wrote:
create index ts_portfolio_dm.instrument_ref_dim_indx1 on ts_portfolio_dm.instrument_reference_dim(instrument_type_dvd, revenue_source_dvd, pricing_dt, instrument_dim_key);

when I execute this command the process is taking too long to create an index .is there any additional coding that can help create index fast.
The time taken to create an index depends largely on the the volume of data in the table and number of columns being indexed.
fjfranken
Hi

You could add the "NOLOGGING" option.
This might speed it up a bit, because no redo logging is written for the index-creation. But it is only a small improvement

Your statement would then look like: 
CREATE INDEX ts_portfolio_dm.instrument_ref_dim_indx1
   ON ts_portfolio_dm.instrument_reference_dim (instrument_type_dvd
,                                               revenue_source_dvd
,                                               pricing_dt
,                                               instrument_dim_key) nologging ;
Maybe also add the PARALLEL clause to force parallel execution. But for the remainder I agree with the other reply. It is simply the amount of data that makes the time here
948403
Hi ,

thanks for the reply .

could you please give me the statement that contains both

1.parllel creation 2.no logging.

Is there any further improvements that can be done on this .
The table is very huge and lot of procedures use this .Hence the reson we are not able to allow the statement to execute for more time .
cheers,
P
1 - 3

Post Details

Added on Jan 23 2018
#java-enterprise-edition
2 comments
36,587 views