size-rotating-file-handler rotate-size doens't properly handle add/update with management API --------------------------------------------------------------------------------------------- Key: AS7-1367 URL: https://issues.jboss.org/browse/AS7-1367 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.0.0.Final Reporter: Stan Silvert Assignee: James Perkins Fix For: 7.1.0.Beta1 From the management API, rotate-size doesn't handle the one-character suffixes for (b)yte, (k)ilobyte, (m)egabyte, etc. So for instance, if you say: /subsystem=logging/size-rotating-file-handler=SIZE:update-properties(rotate-size=5m) You will get an error because it will try to convert that to a long. If you enter a valid long without a suffix, then the value will be corrupted when the server is restarted. The solution is to keep this attribute as a String in the management model and only parse out the suffix when you need to convert to a long for the runtime.

size-rotating-file-handler rotate-size doens't properly handle add/update with management API --------------------------------------------------------------------------------------------- Key: AS7-1367 URL: https://issues.jboss.org/browse/AS7-1367 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.0.0.Final Reporter: Stan Silvert Assignee: James Perkins Fix For: 7.1.0.CR1 From the management API, rotate-size doesn't handle the one-character suffixes for (b)yte, (k)ilobyte, (m)egabyte, etc. So for instance, if you say: /subsystem=logging/size-rotating-file-handler=SIZE:update-properties(rotate-size=5m) You will get an error because it will try to convert that to a long. If you enter a valid long without a suffix, then the value will be corrupted when the server is restarted. The solution is to keep this attribute as a String in the management model and only parse out the suffix when you need to convert to a long for the runtime.