September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7103) In elytron security domain add operation the realms attribute is not marked as required even though it is not nillable and has no default value with no default value

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7103?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-7103: ---------------------------------------- In a rare twist of engineering asking for a bug report to have a higher priority than QE ask for I am going to raise this one back to major ;-) The reason being is the security-domain resource is one of the most central resources that will be used with Elytron so accuracy of the model description from the outset is going to be important. [~honza889] Can you please double check this one? I think the approach changed a bit on this one whilst deciding how to handle the default realm which you already have an issue for. > In elytron security domain add operation the realms attribute is not marked as required even though it is not nillable and has no default value with no default value > --------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7103 > URL: https://issues.jboss.org/browse/WFLY-7103 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Security > Reporter: Radim Hatlapatka > Assignee: Jan Kalina > > When reading description of the {{add}} operation for elytron security domain => {{/subsystem=elytron/security-domain=test-domain:read-operation-description(name=add)}}, the realms attribute has set required to false. Still it needs to be defined as part of {{add}} operation as it is not nillable. > If it is really mandatory, it should be marked as required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7103) In elytron security domain add operation the realms attribute is not marked as required even though it is not nillable and has no default value with no default value

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7103?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7103: ----------------------------------- Priority: Major (was: Minor) > In elytron security domain add operation the realms attribute is not marked as required even though it is not nillable and has no default value with no default value > --------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7103 > URL: https://issues.jboss.org/browse/WFLY-7103 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Security > Reporter: Radim Hatlapatka > Assignee: Jan Kalina > > When reading description of the {{add}} operation for elytron security domain => {{/subsystem=elytron/security-domain=test-domain:read-operation-description(name=add)}}, the realms attribute has set required to false. Still it needs to be defined as part of {{add}} operation as it is not nillable. > If it is really mandatory, it should be marked as required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7103) In elytron security domain add operation the realms attribute is not marked as required even though it is not nillable and has no default value with no default value

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7103?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-7103: -------------------------------------- Assignee: Jan Kalina (was: Darran Lofthouse) > In elytron security domain add operation the realms attribute is not marked as required even though it is not nillable and has no default value with no default value > --------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7103 > URL: https://issues.jboss.org/browse/WFLY-7103 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Security > Reporter: Radim Hatlapatka > Assignee: Jan Kalina > Priority: Minor > > When reading description of the {{add}} operation for elytron security domain => {{/subsystem=elytron/security-domain=test-domain:read-operation-description(name=add)}}, the realms attribute has set required to false. Still it needs to be defined as part of {{add}} operation as it is not nillable. > If it is really mandatory, it should be marked as required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7103) In elytron security domain add operation the realms attribute is not marked as required even though it is not nillable and has no default value with no default value

by Radim Hatlapatka (JIRA)

Radim Hatlapatka created WFLY-7103: -------------------------------------- Summary: In elytron security domain add operation the realms attribute is not marked as required even though it is not nillable and has no default value with no default value Key: WFLY-7103 URL: https://issues.jboss.org/browse/WFLY-7103 Project: WildFly Issue Type: Bug Components: Domain Management, Security Reporter: Radim Hatlapatka Assignee: Brian Stansberry Priority: Minor When reading description of the {{add}} operation for elytron security domain => {{/subsystem=elytron/security-domain=test-domain:read-operation-description(name=add)}}, the realms attribute has set required to false. Still it needs to be defined as part of {{add}} operation as it is not nillable. If it is really mandatory, it should be marked as required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7103) In elytron security domain add operation the realms attribute is not marked as required even though it is not nillable and has no default value with no default value

by Radim Hatlapatka (JIRA)

[ https://issues.jboss.org/browse/WFLY-7103?page=com.atlassian.jira.plugin.... ] Radim Hatlapatka reassigned WFLY-7103: -------------------------------------- Assignee: Darran Lofthouse (was: Brian Stansberry) > In elytron security domain add operation the realms attribute is not marked as required even though it is not nillable and has no default value with no default value > --------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7103 > URL: https://issues.jboss.org/browse/WFLY-7103 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Security > Reporter: Radim Hatlapatka > Assignee: Darran Lofthouse > Priority: Minor > > When reading description of the {{add}} operation for elytron security domain => {{/subsystem=elytron/security-domain=test-domain:read-operation-description(name=add)}}, the realms attribute has set required to false. Still it needs to be defined as part of {{add}} operation as it is not nillable. > If it is really mandatory, it should be marked as required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7102) Allow subsystems to register their context handlers to the management endpoint

by Tristan Tarrant (JIRA)

Tristan Tarrant created WFLY-7102: ------------------------------------- Summary: Allow subsystems to register their context handlers to the management endpoint Key: WFLY-7102 URL: https://issues.jboss.org/browse/WFLY-7102 Project: WildFly Issue Type: Feature Request Components: Domain Management Reporter: Tristan Tarrant Assignee: Brian Stansberry For layered products, we would like to be able to register custom handlers to the management endpoint (e.g. for exposing health-check URLs) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1793) add-content operation fails to overwrite existing content with overwrite=true set when passing content by file path

by Michal Jurc (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1793?page=com.atlassian.jira.plugi... ] Michal Jurc updated WFCORE-1793: -------------------------------- Description: Upon overwriting content in managed exploded deployments on wildfly-core, the following errors are produced: {{CLI}} {code}[standalone@localhost:9990 /] deploy /home/mjurc/testing/eap7-204/jboss-kitchensink-ear.ear [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:undeploy {"outcome" => "success"} [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:explode {"outcome" => "success"} [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:deploy {"outcome" => "success"} [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:add-content(content=[{path=/home/mjurc/testing/eap7-204/test.txt, target-path=test.txt}], overwrite=true) { "outcome" => "failed", "failure-description" => "org.jboss.as.repository.ExplodedContentException: WFLYDR0021: Error updating content of exploded deployment", "rolled-back" => true } [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:add-content(content=[{path=/home/mjurc/testing/eap7-204/test.txt, target-path=test.txt}], overwrite=false) { "outcome" => "failed", "failure-description" => "org.jboss.as.repository.ExplodedContentException: WFLYDR0021: Error updating content of exploded deployment", "rolled-back" => true } [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:add-content(content=[{path=/home/mjurc/testing/eap7-204/test.txt, target-path=test.txt}]) { "outcome" => "failed", "failure-description" => "org.jboss.as.repository.ExplodedContentException: WFLYDR0021: Error updating content of exploded deployment", "rolled-back" => true }{code} {{Server}} {code}09:41:36,029 WARN [org.jboss.as.repository] (management-handler-thread - 5) java.nio.file.FileAlreadyExistsException: /home/mjurc/testing/wildfly-core/build/target/wildfly-core-3.0.0.Alpha8-SNAPSHOT/standalone/data/content/content7797527203290314566/content/test.txt 09:45:27,505 WARN [org.jboss.as.repository] (management-handler-thread - 12) java.nio.file.FileAlreadyExistsException: /home/mjurc/testing/wildfly-core/build/target/wildfly-core-3.0.0.Alpha8-SNAPSHOT/standalone/data/content/content721393778736298367/content/test.txt 09:45:36,352 WARN [org.jboss.as.repository] (management-handler-thread - 10) java.nio.file.FileAlreadyExistsException: /home/mjurc/testing/wildfly-core/build/target/wildfly-core-3.0.0.Alpha8-SNAPSHOT/standalone/data/content/content344811471223714239/content/test.txt{code} This issue does not seem to arise when the content is passed to the server by input stream index. was: Upon overwriting content in managed exploded deployments on wildfly-core, the following errors are produced: {{CLI}} {code}[standalone@localhost:9990 /] deploy /home/mjurc/testing/eap7-204/jboss-kitchensink-ear.ear [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:undeploy {"outcome" => "success"} [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:explode {"outcome" => "success"} [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:deploy {"outcome" => "success"} [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:add-content(content=[{path=/home/mjurc/testing/eap7-204/test.txt, target-path=test.txt}], overwrite=true) { "outcome" => "failed", "failure-description" => "org.jboss.as.repository.ExplodedContentException: WFLYDR0021: Error updating content of exploded deployment", "rolled-back" => true } [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:add-content(content=[{path=/home/mjurc/testing/eap7-204/test.txt, target-path=test.txt}], overwrite=false) { "outcome" => "failed", "failure-description" => "org.jboss.as.repository.ExplodedContentException: WFLYDR0021: Error updating content of exploded deployment", "rolled-back" => true } [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:add-content(content=[{path=/home/mjurc/testing/eap7-204/test.txt, target-path=test.txt}]) { "outcome" => "failed", "failure-description" => "org.jboss.as.repository.ExplodedContentException: WFLYDR0021: Error updating content of exploded deployment", "rolled-back" => true }{code} {{Server}} {code}09:41:36,029 WARN [org.jboss.as.repository] (management-handler-thread - 5) java.nio.file.FileAlreadyExistsException: /home/mjurc/testing/wildfly-core/build/target/wildfly-core-3.0.0.Alpha8-SNAPSHOT/standalone/data/content/content7797527203290314566/content/test.txt 09:45:27,505 WARN [org.jboss.as.repository] (management-handler-thread - 12) java.nio.file.FileAlreadyExistsException: /home/mjurc/testing/wildfly-core/build/target/wildfly-core-3.0.0.Alpha8-SNAPSHOT/standalone/data/content/content721393778736298367/content/test.txt 09:45:36,352 WARN [org.jboss.as.repository] (management-handler-thread - 10) java.nio.file.FileAlreadyExistsException: /home/mjurc/testing/wildfly-core/build/target/wildfly-core-3.0.0.Alpha8-SNAPSHOT/standalone/data/content/content344811471223714239/content/test.txt{code} > add-content operation fails to overwrite existing content with overwrite=true set when passing content by file path > ------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1793 > URL: https://issues.jboss.org/browse/WFCORE-1793 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.0.Alpha8 > Reporter: Michal Jurc > Assignee: ehsavoie Hugonnet > > Upon overwriting content in managed exploded deployments on wildfly-core, the following errors are produced: > {{CLI}} > {code}[standalone@localhost:9990 /] deploy /home/mjurc/testing/eap7-204/jboss-kitchensink-ear.ear > [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:undeploy > {"outcome" => "success"} > [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:explode > {"outcome" => "success"} > [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:deploy > {"outcome" => "success"} > [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:add-content(content=[{path=/home/mjurc/testing/eap7-204/test.txt, target-path=test.txt}], overwrite=true) > { > "outcome" => "failed", > "failure-description" => "org.jboss.as.repository.ExplodedContentException: WFLYDR0021: Error updating content of exploded deployment", > "rolled-back" => true > } > [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:add-content(content=[{path=/home/mjurc/testing/eap7-204/test.txt, target-path=test.txt}], overwrite=false) > { > "outcome" => "failed", > "failure-description" => "org.jboss.as.repository.ExplodedContentException: WFLYDR0021: Error updating content of exploded deployment", > "rolled-back" => true > } > [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:add-content(content=[{path=/home/mjurc/testing/eap7-204/test.txt, target-path=test.txt}]) > { > "outcome" => "failed", > "failure-description" => "org.jboss.as.repository.ExplodedContentException: WFLYDR0021: Error updating content of exploded deployment", > "rolled-back" => true > }{code} > {{Server}} > {code}09:41:36,029 WARN [org.jboss.as.repository] (management-handler-thread - 5) java.nio.file.FileAlreadyExistsException: /home/mjurc/testing/wildfly-core/build/target/wildfly-core-3.0.0.Alpha8-SNAPSHOT/standalone/data/content/content7797527203290314566/content/test.txt > 09:45:27,505 WARN [org.jboss.as.repository] (management-handler-thread - 12) java.nio.file.FileAlreadyExistsException: /home/mjurc/testing/wildfly-core/build/target/wildfly-core-3.0.0.Alpha8-SNAPSHOT/standalone/data/content/content721393778736298367/content/test.txt > 09:45:36,352 WARN [org.jboss.as.repository] (management-handler-thread - 10) java.nio.file.FileAlreadyExistsException: /home/mjurc/testing/wildfly-core/build/target/wildfly-core-3.0.0.Alpha8-SNAPSHOT/standalone/data/content/content344811471223714239/content/test.txt{code} > This issue does not seem to arise when the content is passed to the server by input stream index. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1793) add-content operation fails to overwrite existing content with overwrite=true set when passing content by file path

by Michal Jurc (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1793?page=com.atlassian.jira.plugi... ] Michal Jurc updated WFCORE-1793: -------------------------------- Summary: add-content operation fails to overwrite existing content with overwrite=true set when passing content by file path (was: add-content operation fails to overwrite existing content with overwrite=true set) > add-content operation fails to overwrite existing content with overwrite=true set when passing content by file path > ------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1793 > URL: https://issues.jboss.org/browse/WFCORE-1793 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.0.Alpha8 > Reporter: Michal Jurc > Assignee: ehsavoie Hugonnet > > Upon overwriting content in managed exploded deployments on wildfly-core, the following errors are produced: > {{CLI}} > {code}[standalone@localhost:9990 /] deploy /home/mjurc/testing/eap7-204/jboss-kitchensink-ear.ear > [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:undeploy > {"outcome" => "success"} > [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:explode > {"outcome" => "success"} > [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:deploy > {"outcome" => "success"} > [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:add-content(content=[{path=/home/mjurc/testing/eap7-204/test.txt, target-path=test.txt}], overwrite=true) > { > "outcome" => "failed", > "failure-description" => "org.jboss.as.repository.ExplodedContentException: WFLYDR0021: Error updating content of exploded deployment", > "rolled-back" => true > } > [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:add-content(content=[{path=/home/mjurc/testing/eap7-204/test.txt, target-path=test.txt}], overwrite=false) > { > "outcome" => "failed", > "failure-description" => "org.jboss.as.repository.ExplodedContentException: WFLYDR0021: Error updating content of exploded deployment", > "rolled-back" => true > } > [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:add-content(content=[{path=/home/mjurc/testing/eap7-204/test.txt, target-path=test.txt}]) > { > "outcome" => "failed", > "failure-description" => "org.jboss.as.repository.ExplodedContentException: WFLYDR0021: Error updating content of exploded deployment", > "rolled-back" => true > }{code} > {{Server}} > {code}09:41:36,029 WARN [org.jboss.as.repository] (management-handler-thread - 5) java.nio.file.FileAlreadyExistsException: /home/mjurc/testing/wildfly-core/build/target/wildfly-core-3.0.0.Alpha8-SNAPSHOT/standalone/data/content/content7797527203290314566/content/test.txt > 09:45:27,505 WARN [org.jboss.as.repository] (management-handler-thread - 12) java.nio.file.FileAlreadyExistsException: /home/mjurc/testing/wildfly-core/build/target/wildfly-core-3.0.0.Alpha8-SNAPSHOT/standalone/data/content/content721393778736298367/content/test.txt > 09:45:36,352 WARN [org.jboss.as.repository] (management-handler-thread - 10) java.nio.file.FileAlreadyExistsException: /home/mjurc/testing/wildfly-core/build/target/wildfly-core-3.0.0.Alpha8-SNAPSHOT/standalone/data/content/content344811471223714239/content/test.txt{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1793) add-content operation fails to overwrite existing content with overwrite=true set

by Michal Jurc (JIRA)

Michal Jurc created WFCORE-1793: ----------------------------------- Summary: add-content operation fails to overwrite existing content with overwrite=true set Key: WFCORE-1793 URL: https://issues.jboss.org/browse/WFCORE-1793 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 3.0.0.Alpha8 Reporter: Michal Jurc Assignee: ehsavoie Hugonnet Upon overwriting content in managed exploded deployments on wildfly-core, the following errors are produced: {{CLI}} {code}[standalone@localhost:9990 /] deploy /home/mjurc/testing/eap7-204/jboss-kitchensink-ear.ear [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:undeploy {"outcome" => "success"} [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:explode {"outcome" => "success"} [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:deploy {"outcome" => "success"} [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:add-content(content=[{path=/home/mjurc/testing/eap7-204/test.txt, target-path=test.txt}], overwrite=true) { "outcome" => "failed", "failure-description" => "org.jboss.as.repository.ExplodedContentException: WFLYDR0021: Error updating content of exploded deployment", "rolled-back" => true } [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:add-content(content=[{path=/home/mjurc/testing/eap7-204/test.txt, target-path=test.txt}], overwrite=false) { "outcome" => "failed", "failure-description" => "org.jboss.as.repository.ExplodedContentException: WFLYDR0021: Error updating content of exploded deployment", "rolled-back" => true } [standalone@localhost:9990 /] /deployment=jboss-kitchensink-ear.ear:add-content(content=[{path=/home/mjurc/testing/eap7-204/test.txt, target-path=test.txt}]) { "outcome" => "failed", "failure-description" => "org.jboss.as.repository.ExplodedContentException: WFLYDR0021: Error updating content of exploded deployment", "rolled-back" => true }{code} {{Server}} {code}09:41:36,029 WARN [org.jboss.as.repository] (management-handler-thread - 5) java.nio.file.FileAlreadyExistsException: /home/mjurc/testing/wildfly-core/build/target/wildfly-core-3.0.0.Alpha8-SNAPSHOT/standalone/data/content/content7797527203290314566/content/test.txt 09:45:27,505 WARN [org.jboss.as.repository] (management-handler-thread - 12) java.nio.file.FileAlreadyExistsException: /home/mjurc/testing/wildfly-core/build/target/wildfly-core-3.0.0.Alpha8-SNAPSHOT/standalone/data/content/content721393778736298367/content/test.txt 09:45:36,352 WARN [org.jboss.as.repository] (management-handler-thread - 10) java.nio.file.FileAlreadyExistsException: /home/mjurc/testing/wildfly-core/build/target/wildfly-core-3.0.0.Alpha8-SNAPSHOT/standalone/data/content/content344811471223714239/content/test.txt{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1283) Memory leak using KieBuilder.build() method.

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1283?page=com.atlassian.jira.plugi... ] Matteo Mortari reassigned DROOLS-1283: -------------------------------------- Assignee: Matteo Mortari (was: Mario Fusco) > Memory leak using KieBuilder.build() method. > --------------------------------------------- > > Key: DROOLS-1283 > URL: https://issues.jboss.org/browse/DROOLS-1283 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.CR1 > Reporter: Tibor Zimányi > Assignee: Matteo Mortari > Labels: regression, reported-by-qe > > There is a memory leak when building KieBase using KieBuilder.build() method. When continuously calling kieBuilder.build() (also with no resources), the OOM exception occurs. > I will make PR with a reproducer for this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2016