Getting java.lang.NoSuchFieldError: ALLOW_MULTIPLE_USERS while trying to start JBoss EAP 6.1.0 .

Solution Unverified - Updated -

Issue

  • We use standalone-ha.xml to start JBoss eap 6.1.0.When we try to start jboss eap we got this error :
[0m[31m11:24:25,400 ERROR [org.jboss.as.controller] (Controller Boot Thread) JBAS014601: Error booting the container: java.lang.NoSuchFieldError: ALLOW_MULTIPLE_USERS
    at org.jboss.as.connector.subsystems.datasources.Constants.<clinit>(Constants.java:289)
    at org.jboss.as.connector.subsystems.datasources.DsParser.parseDataSource(DsParser.java:565)
    at org.jboss.as.connector.subsystems.datasources.DsParser.parseDataSources(DsParser.java:196)
    at org.jboss.as.connector.subsystems.datasources.DsParser.parse(DsParser.java:167)
    at org.jboss.as.connector.subsystems.datasources.DataSourcesExtension$DataSourceSubsystemParser.readElement(DataSourcesExtension.java:568)
    at org.jboss.as.connector.subsystems.datasources.DataSourcesExtension$DataSourceSubsystemParser.readElement(DataSourcesExtension.java:182)
    at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
    at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
    at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:1028) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
    at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_4(StandaloneXml.java:449) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
    at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:136) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
    at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:103) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
    at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
    at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
    at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
    at org.jboss.as.server.ServerService.boot(ServerService.java:308) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
    at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:188) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
    at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_43
  • To narrow down the issue we commented the datasource temporarily ,after restarting the server we got below error.
Unable to set property pattern on class org.jboss.logmanager.formatters.PatternFormatter: java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.logmanager.PropertyConfigurator.configureProperties(PropertyConfigurator.java:187)
        at org.jboss.logmanager.PropertyConfigurator.configureFormatter(PropertyConfigurator.java:360)
        at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:305)
        at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:128)
        at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:86)
        at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:246)
        at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:231)
        at java.util.logging.LogManager$2.run(LogManager.java:267)
        at java.util.logging.LogManager$2.run(LogManager.java:265)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:265)
        at java.util.logging.LogManager.getLogManager(LogManager.java:248)
        at java.util.logging.Logger.<init>(Logger.java:225)
        at java.util.logging.LogManager$RootLogger.<init>(LogManager.java:1289)
        at java.util.logging.LogManager$RootLogger.<init>(LogManager.java:1287)
        at java.util.logging.LogManager$1.run(LogManager.java:179)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.util.logging.LogManager.<clinit>(LogManager.java:156)
        at org.jboss.modules.Main.main(Main.java:394)
Caused by: java.lang.IllegalArgumentException: Encountered an unknown format character
        at org.jboss.logmanager.formatters.FormatStringParser.getSteps(FormatStringParser.java:168)
        at org.jboss.logmanager.formatters.PatternFormatter.setPattern(PatternFormatter.java:63)
        ... 23 more

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.1.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content