problem changing to size-rotating-file-handler

[lafr]

I'm using JBoss AS 8.0.0.Alpha1-SNAPSHOT, build from sources.

I created a standalone-langfr.xml based on standalone-full.xml which is used.

Instead of periodic-rotating-file-handler I'd like to use the size-rotating-file-handler.

So I replaced the part element periodic-rotating-file-handler with this:

<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#%M] %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>

But on startup I get

23:23:05,583 ERROR [org.jboss.as.controller.management-operation#executeStep] 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]

Adding the optional element

                <max-backup-index value="1"/>

does not change anything.

Then I removed the FILE handlers at all, only CONSOLE.

Startup, fine.

Then through the web console I add a new FILE handler and add it.

Shutdown, startup.

Everything is fine.

And standalone-langfr.xml ist the same as my original version now.

Why is this not working directly, starting with my file including the size-rotating-file-handler already?

Is there a cross-reference to some other file regarding the loggin handlers which is changed by web console?

[lafr]

I can answer myself this question in parts:

standalone/configuration/logging.properties is created out of the logging config when changed through console.

From logging.properties:

# Note this file has been generated and will be overwritten if a

# logging subsystem has been defined in the XML configuration.

But it's not generated on startup.

There JBoss AS seems to rely that files are in sync.

So I have to replace this also when using my logging setup in standalone-langfr.xml directly by editing the file.

A Bug?

Or at least worth a feature request?

[jaikiran]

Well, the exception stacktrace that you received for no obvious fault of your configuration does seem to indicate this is a bug. Could you please create a JIRA and add a sample standalone configuration file which reproduces this?

[jcrossley]

I'm seeing something similar on Openshift after having bumped both TorqueBox and Immutant to depend on a recent incremental release of AS 7.2. I see a "no property 'suffix' setter" error for the periodic-rotating-file-handler in the logs after following the instructions at either https://github.com/torquebox/openshift-quickstart or https://github.com/immutant/openshift-quickstart

I suspect it has to do with Openshift providing it's own logging.properties that doesn't necessarily agree with standalone.xml.

[jamezp]

Yes, essentially both the logging.properties and the logging subsystem configuration need to match. Or at least if handlers of the same name need to be the same type if handler. If you were to change the handler name to something else in either configuration it would work.

--

James R. Perkins