Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-178

Changing logging handler in standalone.xml only breaks startup of JBoss AS7

    XMLWordPrintable

Details

    Description

      Using an unmodified build of JBoss AS 8.0.0.Alpha1-SNAPSHOT as of today.
      Starting with --server-config=standalone-full.xml is fine.
      I made a copy of standalone-full.xml as standalone-langfr.xml and replaced the periodic-rotating-file-handler by a size-rotating-file-handler:
      <size-rotating-file-handler name="FILE" autoflush="false">
      <level name="DEBUG"/>
      <encoding value="UTF-8"/>
      <formatter>
      <pattern-formatter pattern="%d

      {HH:mm:ss,SSS}

      %-5p [%c] (%t) %s%E%n"/>
      </formatter>
      <file relative-to="jboss.server.log.dir" path="server.log"/>
      <rotate-size value="1g"/>
      <append value="true"/>
      </size-rotating-file-handler>

      jboss@sb2000:/jboss/8.0/standalone/configuration diff -bw standalone-full.xml standalone-langfr.xml
      68c68,70
      < <periodic-rotating-file-handler name="FILE" autoflush="true">

      > <size-rotating-file-handler name="FILE" autoflush="false">
      > <level name="DEBUG"/>
      > <encoding value="UTF-8"/>
      73c75
      < <suffix value=".yyyy-MM-dd"/>

      > <rotate-size value="1g"/>
      75c77
      < </periodic-rotating-file-handler>

      > </size-rotating-file-handler>

      Trying to start the server with this config fails:
      12:21:57,916 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.CR1
      12:21:58,458 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA
      12:21:58,752 INFO [org.jboss.as] (MSC service thread 1-3) JBAS015899: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" starting
      12:22:03,232 INFO [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.7.GA
      12:22:03,280 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
      12:22:03,285 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.7.GA
      12:22:03,359 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 3.2.14.GA
      12:22:03,486 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("add") failed - address: ([
      ("subsystem" => "logging"),
      ("size-rotating-file-handler" => "FILE")
      ]): java.lang.IllegalArgumentException: No property "maxBackupIndex" setter found for handler "FILE"
      at org.jboss.logmanager.config.AbstractPropertyConfiguration.setPropertyValueExpression(AbstractPropertyConfiguration.java:195) [jboss-logmanager-1.4.0.Final.jar:1.4.0.Final]
      at org.jboss.logmanager.config.AbstractPropertyConfiguration.setPropertyValueString(AbstractPropertyConfiguration.java:156) [jboss-logmanager-1.4.0.Final.jar:1.4.0.Final]
      at org.jboss.as.logging.PropertyAttributeDefinition.setPropertyValue(PropertyAttributeDefinition.java:62) [jboss-as-logging-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
      at org.jboss.as.logging.HandlerOperations.handleProperty(HandlerOperations.java:504) [jboss-as-logging-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
      at org.jboss.as.logging.HandlerOperations.handleProperty(HandlerOperations.java:433) [jboss-as-logging-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
      at org.jboss.as.logging.HandlerOperations.access$000(HandlerOperations.java:72) [jboss-as-logging-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
      at org.jboss.as.logging.HandlerOperations$HandlerAddOperationStepHandler.performRuntime(HandlerOperations.java:196) [jboss-as-logging-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
      at org.jboss.as.logging.LoggingOperations$LoggingAddOperationStepHandler$1.execute(LoggingOperations.java:204) [jboss-as-logging-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
      at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
      at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
      at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
      at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
      at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:191) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
      at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:225) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
      at org.jboss.as.server.ServerService.boot(ServerService.java:333) [jboss-as-server-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
      at org.jboss.as.server.ServerService.boot(ServerService.java:308) [jboss-as-server-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
      at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:188) [jboss-as-controller-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
      at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_39]

      This seem to be cause by the fact, that logging.properties is outdated and does not get updated on start.
      In logging.properties there still is the old config:
      handler.FILE=org.jboss.logmanager.handlers.PeriodicRotatingFileHandler
      handler.FILE.level=ALL
      handler.FILE.formatter=FILE
      handler.FILE.properties=autoFlush,append,fileName,suffix,enabled
      handler.FILE.constructorProperties=fileName,append
      handler.FILE.autoFlush=true
      handler.FILE.append=true
      handler.FILE.fileName=/mbi/tools/jboss/8.0/standalone/log/server.log
      handler.FILE.suffix=.yyyy-MM-dd
      handler.FILE.enabled=true

      An now the is some mixture in place which causes this failure.

      When changing the logging handler via web-console or possibly also when using jboss-cli both files are changed, standalone.xml and logging.properties.

      I think on startup logging.properties should be newly created by what's defined in the current config file.

      Attachments

        Activity

          People

            jperkins-rhn James Perkins
            franklangelage Frank Langelage (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: