May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8335) User should be informed when switching between JDBC and journal store in transactions subsystem

by Romain Pelisse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8335?page=com.atlassian.jira.plugin.... ] Romain Pelisse commented on WFLY-8335: -------------------------------------- 1) Issues with alternatives is now fixed: {code:java} "use-hornetq-store" => { "type" => BOOLEAN, "description" => "Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file system file per transaction log.It's alternative to jdbc based store.", "expressions-allowed" => false, "required" => false, "nillable" => true, "default" => false, "alternatives" => [ "use-jdbc-store", "use-journal-store" ],... "use-jdbc-store" => { "type" => BOOLEAN, "description" => "Use the jdbc store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file file per transaction log. It's alternative to journal based store.", "expressions-allowed" => false, "required" => false, "nillable" => true, "default" => false, "alternatives" => [ "use-journal-store", "use-hornetq-store" ], "requires" => ["jdbc-store-datasource"], "access-type" => "read-write", "storage" => "configuration", "restart-required" => "jvm" }, ... "use-journal-store" => { "type" => BOOLEAN, "description" => "Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store creates normally one file system file per transaction log. The journal one consists from one file for all the transactions. It's alternative to jdbc based store.", "expressions-allowed" => false, "required" => false, "nillable" => true, "default" => false, "alternatives" => [ "use-jdbc-store", "use-hornetq-store" ], "access-type" => "read-write", "storage" => "configuration", "restart-required" => "jvm" } {code} 2) I could not reproduce the issue with batch in both standalone and domain mode: {code} [standalone@localhost:9990 /] batch [standalone@localhost:9990 / #] /subsystem=transactions:write-attribute(name=use-journal-store,value=true) [standalone@localhost:9990 / #] /subsystem=transactions:write-attribute(name=jdbc-store-datasource, value=java:jboss/datasources/ExampleDS) [standalone@localhost:9990 / #] /subsystem=transactions:write-attribute(name=use-jdbc-store,value=true) [standalone@localhost:9990 / #] run-batch The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed: Step: step-3 Operation: /subsystem=transactions:write-attribute(name=use-jdbc-store,value=true) Failure: WFLYCTL0105: use-journal-store is invalid in combination with use-jdbc-store {code} ----- {code} [domain@localhost:9990 /] batch [domain@localhost:9990 / #] /profile=default/subsystem=transactions:write-attribute(name=jdbc-store-datasource, value=java:jboss/datasources/ExampleDS) [domain@localhost:9990 / #] /profile=default/subsystem=transactions:write-attribute(name=use-journal-store,value=true) [domain@localhost:9990 / #] /profile=default/subsystem=transactions:write-attribute(name=use-jdbc-store,value=true) [domain@localhost:9990 / #] run-batch The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-3" => "WFLYCTL0105: use-journal-store is invalid in combination with use-jdbc-store"}} {code} Nevertheless I added a test for this use case in the testsuite. > User should be informed when switching between JDBC and journal store in transactions subsystem > ----------------------------------------------------------------------------------------------- > > Key: WFLY-8335 > URL: https://issues.jboss.org/browse/WFLY-8335 > Project: WildFly > Issue Type: Enhancement > Components: Transactions > Affects Versions: 10.1.0.Final > Reporter: Romain Pelisse > Assignee: Romain Pelisse > Priority: Minor > Fix For: 11.0.0.Beta1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Precondition: 'Use journal store' or 'Use JDBC store' was previously set to true. > When enabling other type of store, user is not informed about the fact, that only one of those can be set and the previously enabled store is disabled and the new store is enabled without notification. User should be definitely informed about this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2790) WildFly Elytron tool has to have own sh, bat, ps1 script

by Peter Skopek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2790?page=com.atlassian.jira.plugi... ] Peter Skopek reassigned WFCORE-2790: ------------------------------------ Assignee: Peter Skopek (was: Darran Lofthouse) > WildFly Elytron tool has to have own sh, bat, ps1 script > -------------------------------------------------------- > > Key: WFCORE-2790 > URL: https://issues.jboss.org/browse/WFCORE-2790 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Peter Skopek > > WildFly Elytron tool has to have own sh, bat, ps1 script -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2790) WildFly Elytron tool has to have own sh, bat, ps1 script

by Peter Skopek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2790?page=com.atlassian.jira.plugi... ] Peter Skopek moved WFLY-8545 to WFCORE-2790: -------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-2790 (was: WFLY-8545) Component/s: Security (was: Security) > WildFly Elytron tool has to have own sh, bat, ps1 script > -------------------------------------------------------- > > Key: WFCORE-2790 > URL: https://issues.jboss.org/browse/WFCORE-2790 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > > WildFly Elytron tool has to have own sh, bat, ps1 script -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7643) JAX-WS Webservice endpoint naming conflict between different virtual hosts

by István Tóth (JIRA)

[ https://issues.jboss.org/browse/WFLY-7643?page=com.atlassian.jira.plugin.... ] István Tóth commented on WFLY-7643: ----------------------------------- It seems that even vhost + context is not neccessarily unique, because multiple undertow servers can be defined that can have identical vhosts in them. So it is possible that server name should be added to the endpoint name as well. i.e. jboss.ws.endpoint.server="default-server".vhost="hosta".context=."helloservice.endpoint.Hello" > JAX-WS Webservice endpoint naming conflict between different virtual hosts > -------------------------------------------------------------------------- > > Key: WFLY-7643 > URL: https://issues.jboss.org/browse/WFLY-7643 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 10.1.0.Final, 11.0.0.Alpha1 > Reporter: István Tóth > Assignee: Alessio Soldano > Attachments: Hello.java, jboss-web.xml, vhost-config-fragment.xml > > > When deploying identically named POJO JAX-WS webservice endpoints into different virtualhosts with the same context, the ServiceName generated for the second deployment conflicts with the first one, and the deployment fails with org.jboss.msc.service.DuplicateServiceException. > This can be worked around by defining the endpoint as a servlet, and giving globally distinct <servlet-name> s to them. > I think the cause for the bug is that the ServiceName for the Endpoint is in a server instance namespace, but the the name is generated from only the endpoint name, and the context, which is not unique among deployments on different virtual hosts. > Adding the virtual host to the generated name would make the service name unique, and should also allow routing to it based on virtualhost info by web server. > In the test case the names could be for example *jboss.ws.endpoint.vhost="hosta".context=."helloservice.endpoint.Hello"* and *jboss.ws.endpoint.vhost="hostb".context=."helloservice.endpoint.Hello"* . -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2483) There is missing CS integration with core management

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2483?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2483: ------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2399, https://github.com/wildfly/wildfly-core/pull/2407 (was: https://github.com/wildfly/wildfly-core/pull/2399) > There is missing CS integration with core management > ---------------------------------------------------- > > Key: WFCORE-2483 > URL: https://issues.jboss.org/browse/WFCORE-2483 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: ehsavoie Hugonnet > Priority: Blocker > Fix For: 3.0.0.Beta20, 3.0.0.Beta21 > > > Priority is BLOCKER because this issue blocks RFE verification https://issues.jboss.org/browse/EAP7-538 > There must be credential store integration with core management as is mentioned in requirements of RFE. > *management/security-realm* > *management/security-realm/authentication/truststore* keystore-password > *management/security-realm/server-identity/ssl* key-password and keystore-password > *management/security-realm/server-identity/secret* > *management/security-realm/authentication/users* > But *security-realm* is deprecated, these resources have this description: > {code} > The security-realm configuration is deprecated and may be removed or moved in future versions. > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2483) There is missing CS integration with core management

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2483?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2483: ------------------------------- Fix Version/s: 3.0.0.Beta21 > There is missing CS integration with core management > ---------------------------------------------------- > > Key: WFCORE-2483 > URL: https://issues.jboss.org/browse/WFCORE-2483 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: ehsavoie Hugonnet > Priority: Blocker > Fix For: 3.0.0.Beta20, 3.0.0.Beta21 > > > Priority is BLOCKER because this issue blocks RFE verification https://issues.jboss.org/browse/EAP7-538 > There must be credential store integration with core management as is mentioned in requirements of RFE. > *management/security-realm* > *management/security-realm/authentication/truststore* keystore-password > *management/security-realm/server-identity/ssl* key-password and keystore-password > *management/security-realm/server-identity/secret* > *management/security-realm/authentication/users* > But *security-realm* is deprecated, these resources have this description: > {code} > The security-realm configuration is deprecated and may be removed or moved in future versions. > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8742) Elytron programmatic AuthenticationContext configuration doesn't work for naming client

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/WFLY-8742?page=com.atlassian.jira.plugin.... ] Josef Cacek moved JBEAP-10832 to WFLY-8742: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8742 (was: JBEAP-10832) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Naming Security (was: Naming) (was: Security) Affects Version/s: (was: 7.1.0.DR16) Affects Testing: (was: Blocks Testing) Fix Version/s: (was: 7.1.0.DR18) > Elytron programmatic AuthenticationContext configuration doesn't work for naming client > --------------------------------------------------------------------------------------- > > Key: WFLY-8742 > URL: https://issues.jboss.org/browse/WFLY-8742 > Project: WildFly > Issue Type: Bug > Components: Naming, Security > Reporter: Josef Cacek > Assignee: David Lloyd > Priority: Blocker > > Naming client doesn't handle correctly the Elytron AuthenticationContext API. > * if the API is used then authentication fails (SASL mech is not configured as expected) - it fails in both cases: wildfly-config.xml present or not. > {code:java} > AuthenticationContext.empty() > .with(MatchRule.ALL, AuthenticationConfiguration.EMPTY.useDefaultProviders().allowSaslMechanisms("ANONYMOUS")) > .run(() -> { > doLookup("http-remoting://127.0.0.1:8080"); > }); > {code} > * if the API is not used and wildfly-config.xml is present, then the client works correctly > {code:java} > doLookup("http-remoting://127.0.0.1:8080"); > {code} > {code:xml} > <configuration> > <authentication-client xmlns="urn:elytron:1.0"> > <authentication-rules> > <rule use-configuration="authn" /> > </authentication-rules> > <authentication-configurations> > <configuration name="authn"> > <allow-sasl-mechanisms names="ANONYMOUS"/> > <use-service-loader-providers /> > </configuration> > </authentication-configurations> > </authentication-client> > </configuration> > {code} > This blocks RFEs EAP7-567 and EAP7-284. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8741) Elytron credential-store should offer operations instead of alias resource

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-8741?page=com.atlassian.jira.plugin.... ] Jan Kalina moved WFCORE-2789 to WFLY-8741: ------------------------------------------ Project: WildFly (was: WildFly Core) Key: WFLY-8741 (was: WFCORE-2789) Component/s: Security (was: Security) Affects Version/s: 11.0.0.Alpha1 (was: 3.0.0.Beta18) > Elytron credential-store should offer operations instead of alias resource > -------------------------------------------------------------------------- > > Key: WFLY-8741 > URL: https://issues.jboss.org/browse/WFLY-8741 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Blocker > > Elytron credential-store resources should offer operations instead of alias resource, as for key-stores, as it can be based on any key-store too. > The reason is more described in WFCORE-2691 or related mailing thread on wildfly-dev. > Setting priority to blocker by WFCORE-2691 and WFCORE-2737. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2789) Elytron credential-store should offer operations instead of alias resource

by Jan Kalina (JIRA)

Jan Kalina created WFCORE-2789: ---------------------------------- Summary: Elytron credential-store should offer operations instead of alias resource Key: WFCORE-2789 URL: https://issues.jboss.org/browse/WFCORE-2789 Project: WildFly Core Issue Type: Bug Components: Security Affects Versions: 3.0.0.Beta18 Reporter: Jan Kalina Assignee: Jan Kalina Priority: Blocker Elytron credential-store resources should offer operations instead of alias resource, as for key-stores, as it can be based on any key-store too. The reason is more described in WFCORE-2691 or related mailing thread on wildfly-dev. Setting priority to blocker by WFCORE-2691 and WFCORE-2737. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2741) ManagedServerOperationsFactory is not propagating the 'module' attribute to the servers

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2741?page=com.atlassian.jira.plugi... ] Yeray Borges reassigned WFCORE-2741: ------------------------------------ Assignee: Yeray Borges > ManagedServerOperationsFactory is not propagating the 'module' attribute to the servers > --------------------------------------------------------------------------------------- > > Key: WFCORE-2741 > URL: https://issues.jboss.org/browse/WFCORE-2741 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Yeray Borges > Priority: Critical > > In a managed domain if you configure a vault with the 'module' attribute set, when the HC launches a server that attribute value is not passed to the server in the relevant operation in the boot operation list. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 May 2017