[JBoss JIRA] (AS7-5315) It's not possible to regenerate SessionID preventing Session Fixation attack
by Jean-Frederic Clere (JIRA)
[ https://issues.jboss.org/browse/AS7-5315?page=com.atlassian.jira.plugin.s... ]
Jean-Frederic Clere commented on AS7-5315:
------------------------------------------
org.apache.catalina.authenticator.AuthenticatorBase.CHANGE_SESSIONID_ON_AUTH="true" will automatically change the SessionID on login (since EAP6).
> It's not possible to regenerate SessionID preventing Session Fixation attack
> ----------------------------------------------------------------------------
>
> Key: AS7-5315
> URL: https://issues.jboss.org/browse/AS7-5315
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Security, Web
> Affects Versions: 7.1.1.Final
> Environment: JBoss 7.1.1.Final, JAAS, Windows 7
> Reporter: Endrigo Antonini
> Assignee: Jean-Frederic Clere
> Labels: JAAS, Security, Session, SessionFixation, SessionHijack
>
> I tried to find a way so I can regenerate the Session ID.
> The server generate the "sessionId" when the user open the login page. After all the "authentication process" inside the secured system, the user still have the same "sessionId".
> This is a security problem. This allow a not good intended person to hijack the user session consequently giving all permission to this person that the hijacked session has.
> The link bellow show an possible way to fix that inside the program. The problem is that this code doesn't work on JBoss.
> https://www.owasp.org/index.php/Session_Fixation_in_Java
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (DROOLS-718) Reloading KJAR which contains DSL and RDSLR via KieScanner fails.
by Duncan Doyle (JIRA)
Duncan Doyle created DROOLS-718:
-----------------------------------
Summary: Reloading KJAR which contains DSL and RDSLR via KieScanner fails.
Key: DROOLS-718
URL: https://issues.jboss.org/browse/DROOLS-718
Project: Drools
Issue Type: Bug
Affects Versions: 6.2.0.CR4
Environment: Mac OS X 10.10.2, Oracle HotSpot 1.7.0_71
Reporter: Duncan Doyle
Assignee: Mark Proctor
When using the KieScanner to reload a KJAR with a DSL and RDSLR, reloading fails due to that the compiler is unable to find mappings for the language in the RDSLR.
This is the error I get in my reproducer:
2015-02-18 00:45:02,764 [ERROR] [main] [org.drools.compiler.kie.builder.impl.KieContainerImpl] ERROR Unable to update KieBase: KBase1 to release org.kie:scanner-test:1.0-SNAPSHOT
[7] No mapping entries for expanding: There is a SimpleFact
[7] Unable to expand: There is a SimpleFact
[8] No mapping entries for expanding: -with id "2"
[8] Unable to expand: -with id "2"
[10] No mapping entries for expanding: Print "Found a simple fact with id 2."
[10] Unable to expand: Print "Found a simple fact with id 2."
[7,7]: [ERR 102] Line 7:7 mismatched input 'is' in rule "bla"
Reproducer project can be found here: https://github.com/DuncanDoyle/brms-kjar-with-dsl-kiescanner
Just clone the repo and run 'mvn clean test'.
Note that the reproducer creates the first KJAR, runs test, and then creates the second KJAR. Compilation of the second KJAR fails. When you alter the test to only load the second KJAR, everything works fine.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (DROOLS-717) Create distribution zip for KIE Server
by Petr Široký (JIRA)
Petr Široký created DROOLS-717:
----------------------------------
Summary: Create distribution zip for KIE Server
Key: DROOLS-717
URL: https://issues.jboss.org/browse/DROOLS-717
Project: Drools
Issue Type: Enhancement
Affects Versions: 6.2.0.CR4
Reporter: Petr Široký
Assignee: Petr Široký
Fix For: 6.2.0.Final
Currently the only way for users to download the KIE Server wars is from the JBoss Nexus. We need to create a separate distribution zip with all the wars and link that from the downloads section of drools.org
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFCORE-548) Changing append on a file handler indicates a reload is required when a restart is required
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-548?page=com.atlassian.jira.plugin... ]
James Perkins commented on WFCORE-548:
--------------------------------------
That's a good point and probably makes the most sense. We'll just have to make sure to document as in a composite operation changing the append before a file would result in the previous file being cleared.
> Changing append on a file handler indicates a reload is required when a restart is required
> -------------------------------------------------------------------------------------------
>
> Key: WFCORE-548
> URL: https://issues.jboss.org/browse/WFCORE-548
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: James Perkins
> Assignee: James Perkins
>
> Changing the {{append}} attribute at runtime results in the following output:
> {code}
> [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=append,value=false)
> {
> "outcome" => "success",
> "response-headers" => {
> "operation-requires-reload" => true,
> "process-state" => "reload-required"
> }
> }
> {code}
> A {{reload}} operation does not stop a file from being appended to. Either the behavior needs to change or the {{process-state}} should be "restart-required".
> The issue is likely the file name is checked during boot and hasn't changed therefore the it's not set which would cause the stream to the file to be closed and reopened without the append.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFCORE-548) Changing append on a file handler indicates a reload is required when a restart is required
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFCORE-548?page=com.atlassian.jira.plugin... ]
David Lloyd commented on WFCORE-548:
------------------------------------
Maybe we should make this not require reload *or* restart? Changing the "append" setting shouldn't cause any immediate behavioral change since the file is already open. Turning off "append" shouldn't (for example) make the file suddenly disappear, and turning it on won't change anything either. It should be safe to just let the change happen IMO.
> Changing append on a file handler indicates a reload is required when a restart is required
> -------------------------------------------------------------------------------------------
>
> Key: WFCORE-548
> URL: https://issues.jboss.org/browse/WFCORE-548
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: James Perkins
> Assignee: James Perkins
>
> Changing the {{append}} attribute at runtime results in the following output:
> {code}
> [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=append,value=false)
> {
> "outcome" => "success",
> "response-headers" => {
> "operation-requires-reload" => true,
> "process-state" => "reload-required"
> }
> }
> {code}
> A {{reload}} operation does not stop a file from being appended to. Either the behavior needs to change or the {{process-state}} should be "restart-required".
> The issue is likely the file name is checked during boot and hasn't changed therefore the it's not set which would cause the stream to the file to be closed and reopened without the append.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFCORE-549) Issue with adding server-group and server-config in one composite operation
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-549?page=com.atlassian.jira.plugin... ]
Brian Stansberry reassigned WFCORE-549:
---------------------------------------
Assignee: (was: Jason Greene)
> Issue with adding server-group and server-config in one composite operation
> ---------------------------------------------------------------------------
>
> Key: WFCORE-549
> URL: https://issues.jboss.org/browse/WFCORE-549
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Environment: JBoss EAP 6.1.0 GA
> DC and two HC
> Reporter: Oleg Koropita
>
> I used such request to add two server-groups and four servers
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [
> {
> "operation" => "add",
> "socket-binding-port-offset" => 0,
> "status" => "STOPPED",
> "auto-start" => false,
> "group" => "primary-server-group",
> "socket-binding-group" => "standard-sockets",
> "address" => [
> ("host" => "node02"),
> ("server-config" => "system2-server1")
> ]
> },
> {
> "operation" => "stop",
> "name" => "server",
> "value" => "system2-server1",
> "address" => [
> ("host" => "node02"),
> ("server-config" => "system2-server1")
> ]
> },
> {
> "operation" => "add",
> "socket-binding-port-offset" => 150,
> "status" => "STOPPED",
> "auto-start" => false,
> "group" => "secondary-server-group",
> "socket-binding-group" => "standard-sockets",
> "address" => [
> ("host" => "node02"),
> ("server-config" => "system2-server2")
> ]
> },
> {
> "operation" => "stop",
> "name" => "server",
> "value" => "system2-server2",
> "address" => [
> ("host" => "node02"),
> ("server-config" => "system2-server2")
> ]
> },
> {
> "operation" => "add",
> "socket-binding-port-offset" => 0,
> "status" => "STOPPED",
> "auto-start" => false,
> "group" => "primary-server-group",
> "socket-binding-group" => "standard-sockets",
> "address" => [
> ("host" => "node01"),
> ("server-config" => "system1-server1")
> ]
> },
> {
> "operation" => "stop",
> "name" => "server",
> "value" => "system1-server1",
> "address" => [
> ("host" => "node01"),
> ("server-config" => "system1-server1")
> ]
> },
> {
> "operation" => "add",
> "socket-binding-port-offset" => 150,
> "status" => "STOPPED",
> "auto-start" => false,
> "group" => "secondary-server-group",
> "socket-binding-group" => "standard-sockets",
> "address" => [
> ("host" => "node01"),
> ("server-config" => "system1-server2")
> ]
> },
> {
> "operation" => "stop",
> "name" => "server",
> "value" => "system1-server2",
> "address" => [
> ("host" => "node01"),
> ("server-config" => "system1-server2")
> ]
> },
> {
> "operation" => "add",
> "socket-binding-group" => "standard-sockets",
> "profile" => "default",
> "address" => [("server-group" => "primary-server-group")]
> },
> {
> "operation" => "add",
> "socket-binding-group" => "standard-sockets",
> "profile" => "default",
> "address" => [("server-group" => "secondary-server-group")]
> }
> ]
> }
> And I received such result:
> {
> "outcome" => "success",
> "result" => {
> "step-1" => {"outcome" => "success"},
> "step-2" => {
> "outcome" => "success",
> "result" => "STOPPED"
> },
> "step-3" => {"outcome" => "success"},
> "step-4" => {
> "outcome" => "success",
> "result" => "STOPPED"
> },
> "step-5" => {"outcome" => "success"},
> "step-6" => {
> "outcome" => "success",
> "result" => "STOPPED"
> },
> "step-7" => {"outcome" => "success"},
> "step-8" => {
> "outcome" => "success",
> "result" => "STOPPED"
> },
> "step-9" => undefined,
> "step-10" => undefined
> },
> "server-groups" => undefined
> }
> But, when I checked admin console, there were no server-groups.
> The same with domain.xml on DC side.
> So server-groups wasn't addedd.
> But if I try to add server-groups one more time:
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [
> {
> "operation" => "add",
> "socket-binding-group" => "standard-sockets",
> "profile" => "default",
> "address" => [("server-group" => "primary-server-group")]
> },
> {
> "operation" => "add",
> "socket-binding-group" => "standard-sockets",
> "profile" => "default",
> "address" => [("server-group" => "secondary-server-group")]
> }
> ]
> }
> I will get such result:
> {
> "outcome" => "failed",
> "result" => {
> "step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> },
> "step-2" => {
> "outcome" => "failed",
> "rolled-back" => true
> }
> },
> "failure-description" => {"host-failure-descriptions" => {
> "node02" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014803: Duplicate resource [(\"server-group\" => \"primary-server-group\")]"}},
> "node01" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014803: Duplicate resource [(\"server-group\" => \"primary-server-group\")]"}}
> }},
> "rolled-back" => true
> }
> Then I need to restart DC to restore server. And after that, I can successuflly add server-groups.
> So, after first request, JBoss AS stuck on some uncommited state.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFCORE-549) Issue with adding server-group and server-config in one composite operation
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-549?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFCORE-549:
-----------------------------------------
This was originally reported against EAP 6.1 and 6.2, so the first step in addressing it should be validating whether it is a problem with the current WildFly Core.
> Issue with adding server-group and server-config in one composite operation
> ---------------------------------------------------------------------------
>
> Key: WFCORE-549
> URL: https://issues.jboss.org/browse/WFCORE-549
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Environment: JBoss EAP 6.1.0 GA
> DC and two HC
> Reporter: Oleg Koropita
> Assignee: Jason Greene
>
> I used such request to add two server-groups and four servers
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [
> {
> "operation" => "add",
> "socket-binding-port-offset" => 0,
> "status" => "STOPPED",
> "auto-start" => false,
> "group" => "primary-server-group",
> "socket-binding-group" => "standard-sockets",
> "address" => [
> ("host" => "node02"),
> ("server-config" => "system2-server1")
> ]
> },
> {
> "operation" => "stop",
> "name" => "server",
> "value" => "system2-server1",
> "address" => [
> ("host" => "node02"),
> ("server-config" => "system2-server1")
> ]
> },
> {
> "operation" => "add",
> "socket-binding-port-offset" => 150,
> "status" => "STOPPED",
> "auto-start" => false,
> "group" => "secondary-server-group",
> "socket-binding-group" => "standard-sockets",
> "address" => [
> ("host" => "node02"),
> ("server-config" => "system2-server2")
> ]
> },
> {
> "operation" => "stop",
> "name" => "server",
> "value" => "system2-server2",
> "address" => [
> ("host" => "node02"),
> ("server-config" => "system2-server2")
> ]
> },
> {
> "operation" => "add",
> "socket-binding-port-offset" => 0,
> "status" => "STOPPED",
> "auto-start" => false,
> "group" => "primary-server-group",
> "socket-binding-group" => "standard-sockets",
> "address" => [
> ("host" => "node01"),
> ("server-config" => "system1-server1")
> ]
> },
> {
> "operation" => "stop",
> "name" => "server",
> "value" => "system1-server1",
> "address" => [
> ("host" => "node01"),
> ("server-config" => "system1-server1")
> ]
> },
> {
> "operation" => "add",
> "socket-binding-port-offset" => 150,
> "status" => "STOPPED",
> "auto-start" => false,
> "group" => "secondary-server-group",
> "socket-binding-group" => "standard-sockets",
> "address" => [
> ("host" => "node01"),
> ("server-config" => "system1-server2")
> ]
> },
> {
> "operation" => "stop",
> "name" => "server",
> "value" => "system1-server2",
> "address" => [
> ("host" => "node01"),
> ("server-config" => "system1-server2")
> ]
> },
> {
> "operation" => "add",
> "socket-binding-group" => "standard-sockets",
> "profile" => "default",
> "address" => [("server-group" => "primary-server-group")]
> },
> {
> "operation" => "add",
> "socket-binding-group" => "standard-sockets",
> "profile" => "default",
> "address" => [("server-group" => "secondary-server-group")]
> }
> ]
> }
> And I received such result:
> {
> "outcome" => "success",
> "result" => {
> "step-1" => {"outcome" => "success"},
> "step-2" => {
> "outcome" => "success",
> "result" => "STOPPED"
> },
> "step-3" => {"outcome" => "success"},
> "step-4" => {
> "outcome" => "success",
> "result" => "STOPPED"
> },
> "step-5" => {"outcome" => "success"},
> "step-6" => {
> "outcome" => "success",
> "result" => "STOPPED"
> },
> "step-7" => {"outcome" => "success"},
> "step-8" => {
> "outcome" => "success",
> "result" => "STOPPED"
> },
> "step-9" => undefined,
> "step-10" => undefined
> },
> "server-groups" => undefined
> }
> But, when I checked admin console, there were no server-groups.
> The same with domain.xml on DC side.
> So server-groups wasn't addedd.
> But if I try to add server-groups one more time:
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [
> {
> "operation" => "add",
> "socket-binding-group" => "standard-sockets",
> "profile" => "default",
> "address" => [("server-group" => "primary-server-group")]
> },
> {
> "operation" => "add",
> "socket-binding-group" => "standard-sockets",
> "profile" => "default",
> "address" => [("server-group" => "secondary-server-group")]
> }
> ]
> }
> I will get such result:
> {
> "outcome" => "failed",
> "result" => {
> "step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> },
> "step-2" => {
> "outcome" => "failed",
> "rolled-back" => true
> }
> },
> "failure-description" => {"host-failure-descriptions" => {
> "node02" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014803: Duplicate resource [(\"server-group\" => \"primary-server-group\")]"}},
> "node01" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014803: Duplicate resource [(\"server-group\" => \"primary-server-group\")]"}}
> }},
> "rolled-back" => true
> }
> Then I need to restart DC to restore server. And after that, I can successuflly add server-groups.
> So, after first request, JBoss AS stuck on some uncommited state.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFCORE-549) Issue with adding server-group and server-config in one composite operation
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-549?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved JBEAP-100 to WFCORE-549:
-----------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-549 (was: JBEAP-100)
Workflow: GIT Pull Request workflow (was: CDW v1)
Affects Version/s: (was: EAP 6.1.0.GA)
(was: EAP 6.2.0.GA)
Component/s: Domain Management
(was: Domain Management)
Target Release: (was: EAP 6.4.0.GA)
> Issue with adding server-group and server-config in one composite operation
> ---------------------------------------------------------------------------
>
> Key: WFCORE-549
> URL: https://issues.jboss.org/browse/WFCORE-549
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Environment: JBoss EAP 6.1.0 GA
> DC and two HC
> Reporter: Oleg Koropita
> Assignee: Jason Greene
>
> I used such request to add two server-groups and four servers
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [
> {
> "operation" => "add",
> "socket-binding-port-offset" => 0,
> "status" => "STOPPED",
> "auto-start" => false,
> "group" => "primary-server-group",
> "socket-binding-group" => "standard-sockets",
> "address" => [
> ("host" => "node02"),
> ("server-config" => "system2-server1")
> ]
> },
> {
> "operation" => "stop",
> "name" => "server",
> "value" => "system2-server1",
> "address" => [
> ("host" => "node02"),
> ("server-config" => "system2-server1")
> ]
> },
> {
> "operation" => "add",
> "socket-binding-port-offset" => 150,
> "status" => "STOPPED",
> "auto-start" => false,
> "group" => "secondary-server-group",
> "socket-binding-group" => "standard-sockets",
> "address" => [
> ("host" => "node02"),
> ("server-config" => "system2-server2")
> ]
> },
> {
> "operation" => "stop",
> "name" => "server",
> "value" => "system2-server2",
> "address" => [
> ("host" => "node02"),
> ("server-config" => "system2-server2")
> ]
> },
> {
> "operation" => "add",
> "socket-binding-port-offset" => 0,
> "status" => "STOPPED",
> "auto-start" => false,
> "group" => "primary-server-group",
> "socket-binding-group" => "standard-sockets",
> "address" => [
> ("host" => "node01"),
> ("server-config" => "system1-server1")
> ]
> },
> {
> "operation" => "stop",
> "name" => "server",
> "value" => "system1-server1",
> "address" => [
> ("host" => "node01"),
> ("server-config" => "system1-server1")
> ]
> },
> {
> "operation" => "add",
> "socket-binding-port-offset" => 150,
> "status" => "STOPPED",
> "auto-start" => false,
> "group" => "secondary-server-group",
> "socket-binding-group" => "standard-sockets",
> "address" => [
> ("host" => "node01"),
> ("server-config" => "system1-server2")
> ]
> },
> {
> "operation" => "stop",
> "name" => "server",
> "value" => "system1-server2",
> "address" => [
> ("host" => "node01"),
> ("server-config" => "system1-server2")
> ]
> },
> {
> "operation" => "add",
> "socket-binding-group" => "standard-sockets",
> "profile" => "default",
> "address" => [("server-group" => "primary-server-group")]
> },
> {
> "operation" => "add",
> "socket-binding-group" => "standard-sockets",
> "profile" => "default",
> "address" => [("server-group" => "secondary-server-group")]
> }
> ]
> }
> And I received such result:
> {
> "outcome" => "success",
> "result" => {
> "step-1" => {"outcome" => "success"},
> "step-2" => {
> "outcome" => "success",
> "result" => "STOPPED"
> },
> "step-3" => {"outcome" => "success"},
> "step-4" => {
> "outcome" => "success",
> "result" => "STOPPED"
> },
> "step-5" => {"outcome" => "success"},
> "step-6" => {
> "outcome" => "success",
> "result" => "STOPPED"
> },
> "step-7" => {"outcome" => "success"},
> "step-8" => {
> "outcome" => "success",
> "result" => "STOPPED"
> },
> "step-9" => undefined,
> "step-10" => undefined
> },
> "server-groups" => undefined
> }
> But, when I checked admin console, there were no server-groups.
> The same with domain.xml on DC side.
> So server-groups wasn't addedd.
> But if I try to add server-groups one more time:
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [
> {
> "operation" => "add",
> "socket-binding-group" => "standard-sockets",
> "profile" => "default",
> "address" => [("server-group" => "primary-server-group")]
> },
> {
> "operation" => "add",
> "socket-binding-group" => "standard-sockets",
> "profile" => "default",
> "address" => [("server-group" => "secondary-server-group")]
> }
> ]
> }
> I will get such result:
> {
> "outcome" => "failed",
> "result" => {
> "step-1" => {
> "outcome" => "failed",
> "rolled-back" => true
> },
> "step-2" => {
> "outcome" => "failed",
> "rolled-back" => true
> }
> },
> "failure-description" => {"host-failure-descriptions" => {
> "node02" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014803: Duplicate resource [(\"server-group\" => \"primary-server-group\")]"}},
> "node01" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014803: Duplicate resource [(\"server-group\" => \"primary-server-group\")]"}}
> }},
> "rolled-back" => true
> }
> Then I need to restart DC to restore server. And after that, I can successuflly add server-groups.
> So, after first request, JBoss AS stuck on some uncommited state.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFCORE-548) Changing append on a file handler indicates a reload is required when a restart is required
by James Perkins (JIRA)
James Perkins created WFCORE-548:
------------------------------------
Summary: Changing append on a file handler indicates a reload is required when a restart is required
Key: WFCORE-548
URL: https://issues.jboss.org/browse/WFCORE-548
Project: WildFly Core
Issue Type: Bug
Components: Logging
Reporter: James Perkins
Assignee: James Perkins
Changing the {{append}} attribute at runtime results in the following output:
{code}
[standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=append,value=false)
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
{code}
A {{reload}} operation does not stop a file from being appended to. Either the behavior needs to change or the {{process-state}} should be "restart-required".
The issue is likely the file name is checked during boot and hasn't changed therefore the it's not set which would cause the stream to the file to be closed and reopened without the append.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months