[jboss-jira] [JBoss JIRA] (WFLY-1562) IllegalArgumentException: className is null when starting WildFly

James Perkins (JIRA) jira-events at lists.jboss.org
Wed Jun 19 12:29:20 EDT 2013


    [ https://issues.jboss.org/browse/WFLY-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783021#comment-12783021 ] 

James Perkins commented on WFLY-1562:
-------------------------------------

Yeah, I'm finding it very odd it causes ARQ to not start. Using the same logging.properties in a standalone instance I see the same stack trace, but the server does start.
                
> IllegalArgumentException: className is null when starting WildFly
> -----------------------------------------------------------------
>
>                 Key: WFLY-1562
>                 URL: https://issues.jboss.org/browse/WFLY-1562
>             Project: WildFly
>          Issue Type: Bug
>         Environment: Latest WildFly upstream June 18 2013
>            Reporter: jaikiran pai
>            Assignee: David Lloyd
>         Attachments: logging.properties
>
>
> This stacktrace was noticed on TeamCity when the server is booting:
> {code}
> 08:24:47,542 INFO  [org.jboss.as.arquillian.container.managed.ManagedDeployableContainer] (main) Starting container with: [C:\opt\Java\jdk1.7.0_15\bin\java, -Xmx512m, -XX:MaxPermSize=256m, -Djboss.dist=C:\BuildAgent\work\b145776b46e82d98\testsuite\integration\basic/../../../build/target/wildfly-8.0.0.Alpha2-SNAPSHOT, -Djava.net.preferIPv4Stack=true, -Djava.net.preferIPv6Addresses=false, -server, -Dts.timeout.factor=100, -Dnode0=127.0.0.1, -Dnode1=127.0.0.1, -Dmcast=230.0.0.4, -Djbossas.ts.submodule.dir=C:\BuildAgent\work\b145776b46e82d98\testsuite\integration\basic, -Djbossas.ts.integ.dir=C:\BuildAgent\work\b145776b46e82d98\testsuite\integration\basic/.., -Djbossas.ts.dir=C:\BuildAgent\work\b145776b46e82d98\testsuite\integration\basic/../.., -Djbossas.project.dir=C:\BuildAgent\work\b145776b46e82d98\testsuite\integration\basic/../../.., -Djboss.dist=C:\BuildAgent\work\b145776b46e82d98\testsuite\integration\basic/../../../build/target/wildfly-8.0.0.Alpha2-SNAPSHOT, -Djboss.inst=C:\BuildAgent\work\b145776b46e82d98\testsuite\integration\basic/target/jbossas, -Dtest.bind.address=127.0.0.1, -ea, -Djboss.home.dir=C:\BuildAgent\work\b145776b46e82d98\testsuite\integration\basic/target/jbossas, -Dorg.jboss.boot.log.file=C:\BuildAgent\work\b145776b46e82d98\testsuite\integration\basic\target\jbossas\standalone\log\boot.log, -Dlogging.configuration=file:/C:/BuildAgent/work/b145776b46e82d98/testsuite/integration/basic/target/jbossas/standalone/configuration/logging.properties, -Djboss.bundles.dir=C:\BuildAgent\work\b145776b46e82d98\testsuite\integration\basic/../../../build/target/wildfly-8.0.0.Alpha2-SNAPSHOT/bundles, -jar, C:\BuildAgent\work\b145776b46e82d98\testsuite\integration\basic\target\jbossas\jboss-modules.jar, -mp, C:\BuildAgent\work\b145776b46e82d98\testsuite\integration\basic/../../../build/target/wildfly-8.0.0.Alpha2-SNAPSHOT/modules;C:\BuildAgent\work\b145776b46e82d98\testsuite\integration\basic/target/modules, org.jboss.as.standalone, -server-config, standalone.xml]
> 08:24:47,617 INFO  [org.xnio] (main) XNIO Version 3.1.0.CR3
> 08:24:47,627 INFO  [org.xnio.nio] (main) XNIO NIO Implementation Version 3.1.0.CR3
> 08:24:47,879 INFO  [org.jboss.remoting] (main) JBoss Remoting version 4.0.0.Beta1
> java.lang.IllegalArgumentException: className is null
>     at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:59)
>     at org.jboss.logmanager.config.HandlerConfigurationImpl.<init>(HandlerConfigurationImpl.java:54)
>     at org.jboss.logmanager.config.LogContextConfigurationImpl.addHandlerConfiguration(LogContextConfigurationImpl.java:144)
>     at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:606)
>     at org.jboss.logmanager.PropertyConfigurator.configureLogger(PropertyConfigurator.java:541)
>     at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:480)
>     at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:96)
>     at org.jboss.as.logging.logmanager.ConfigurationPersistence.configure(ConfigurationPersistence.java:148)
>     at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:300)
>     at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:262)
>     at java.util.logging.LogManager$2.run(LogManager.java:288)
>     at java.util.logging.LogManager$2.run(LogManager.java:286)
>     at java.security.AccessController.doPrivileged(Native Method)
>     at java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:286)
>     at java.util.logging.LogManager.getLogManager(LogManager.java:268)
>     at java.util.logging.Logger.<init>(Logger.java:252)
>     at java.util.logging.LogManager$RootLogger.<init>(LogManager.java:1311)
>     at java.util.logging.LogManager$RootLogger.<init>(LogManager.java:1309)
>     at java.util.logging.LogManager$1.run(LogManager.java:199)
>     at java.security.AccessController.doPrivileged(Native Method)
>     at java.util.logging.LogManager.<clinit>(LogManager.java:176)
>     at org.jboss.modules.Main.main(Main.java:394)
> {code}
> This caused the boot to fail. The test(s) affected are here http://teamcity.cafe-babe.org/viewLog.html?buildId=5343&tab=buildResultsDiv&buildTypeId=bt25#testNameId7900515312705391200

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the jboss-jira mailing list