March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2351) There stuck some required service after unsuccessful command for adding CredentialStore with wrong filled relative-to attribute.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2351?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-2351: ------------------------------------------ [~soul2zimate] I think the fix is something different, although you are on the right track regarding checking if a service controller is still installed. Here's what's going on: AbstractOperationContext.processStages() before going to Stage.VERIFY calls awaitServiceContainerStability() which eventually calls ContainerStateMonitor.createContainerStateChangeReport(false). *Nothing is logged at this point* (which is deliberate), but the internal fields in ContainerStateMonitor get populated with some data. The logging at 16:54:18,810 comes from ContainerStateMonitor.logContainerStateChangesAndReset() which indirectly is called by OperationContextImpl.Step.releaseStepLocks. This is called when the operation is completing. In this case the op has rolled back, and therefore there is no unsatisfied dependency any more! But the logging at 16:54:18,810 is as if the rollback hasn't occurred. Then the next op comes along, and when it completes and reaches OperationContextImpl.Step.releaseStepLocks, that's when another report is generated that reports the "correction" that actually occurred during the rollback of the previous op. The reason you get a report after the second op is ContainerStateMonitor is not left in the correct state after the first op completes. ContainerStateMonitor.previousMissingDepSet should be empty at that point. The cause of that not being empty is that when ContainerStateMonitor.createContainerStateChangeReport is called the 2nd time in the first op, the time that produces logging, it uses the 'failed' and 'problems' sets. But those sets can contain ServiceControllers that were added over the course of execution of the op, but which are no longer installed (because the op rolled back). If they are no longer installed, they are no longer "problems" or "failed" so they should be ignored when creating the report. https://github.com/wildfly/wildfly-core/compare/master...bstansberry:WFCO... does that (sorry; I kind of hide the key change behind some refactoring to use Collections.emptySet/Map where possible.) Doing that makes the bogus report after the 2nd op go away. A problem is it makes the first report at 16:54:18,810 go away as well. Perhaps that's good! Quite a few people dislike those messages; they can be quite noisy. And if the end result of the operation is that MSC has no failed services or missing dependencies, then there's nothing to report. But I'm a bit reluctant to just drop that first report. I could restore it by having the call from AbstractOperationContext.processStages() result in logging, and then the OperationContextImpl.Step.releaseStepLocks call also logs, but now reporting the "no longer missing" services. So basically the 2 log statements shown in the description, but now the 2nd one is at the right time. Having those 2 log messages right after one another is also kind of noisy, plus confusing. To reduce the confusion there would probably have to be some sort of INFO message in between saying the op is being rolled back, which helps explain the 2nd report. There would be other issue too with logging twice. For example what if a service is failed and rollback-on-runtime-failure=false is used so there's no rollback? We don't want log the same failed service twice for one op. I'll have to think whether I want that 16:54:18,810 logging even when the op rolls back. The basic point of the report is to report unusual MSC state at the end of an op, so really it's pointless to log it if the end state of the op has no unusual MSC state. The log already has ERROR messages for the missing / failed services that were detected while the op executed. > There stuck some required service after unsuccessful command for adding CredentialStore with wrong filled relative-to attribute. > -------------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2351 > URL: https://issues.jboss.org/browse/WFCORE-2351 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Hynek Švábek > Assignee: Brian Stansberry > > There stuck some required service after unsuccessful command for adding CredentialStore with wrong filled relative-to attribute. > *Command with wrong filled relative-to attribute* > {code} > /subsystem=elytron/credential-store=CredStore108:add(uri="cr-store://test/cs108.jceks?create.storage=true", credential-reference={clear-text=pass123}, relative-to=non.exist.path.resource) > {code} > *You can see this log.* > Especially information about New missing/unsatisfied dependencies:is important and it wouldn't be there. > {code} > 16:54:18,809 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 8) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("credential-store" => "CredStore108") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.server.path.\"non.exist.path.resource\""], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.credential-store.CredStore108 is missing [jboss.server.path.\"non.exist.path.resource\"]"] > } > 16:54:18,810 INFO [org.jboss.as.controller] (management-handler-thread - 8) WFLYCTL0183: Service status report > WFLYCTL0184: New missing/unsatisfied dependencies: > service jboss.server.path."non.exist.path.resource" (missing) dependents: [service org.wildfly.security.credential-store.CredStore108] > {code} > *Now we try process same command without relative-to attribute* > {code} > /subsystem=elytron/credential-store=CredStore108:add(uri="cr-store://test/cs108.jceks?create.storage=true", credential-reference={clear-text=pass123}) > {code} > *Result is success but we can notice this in log:* > {code} > 16:55:33,093 INFO [org.jboss.as.controller] (management-handler-thread - 10) WFLYCTL0183: Service status report > WFLYCTL0185: Newly corrected services: > service jboss.server.path."non.exist.path.resource" (no longer required) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7337) Introduce an authorization SPI

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-7337?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-7337: ----------------------------------- We can close this now I think, as the container can manage all these authorization checks and we are doing so presently by way of a permission check on access to the remote JTA service. > Introduce an authorization SPI > ------------------------------ > > Key: WFLY-7337 > URL: https://issues.jboss.org/browse/WFLY-7337 > Project: WildFly > Issue Type: Enhancement > Components: Transactions > Reporter: David Lloyd > Assignee: Amos Feng > > We need an SPI that can be invoked to authorize state changes in a transaction. The method(s) should make it clear in some way which operation is being authorized, and it must run from the same thread as the thread which instigates the state change. > It must be possible to register an implementation of the SPI when the container starts up or acquires the transaction manager. > The operations that should provide authorization checks include, but are not limited to: > * begin > * rollback > * prepare > * forget > * commit (one or two phase) > * recover > Thanks! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1485) Add a string( mask, p... ) function to format strings according to the mask

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1485?page=com.atlassian.jira.plugi... ] Edson Tirelli resolved DROOLS-1485. ----------------------------------- Resolution: Done > Add a string( mask, p... ) function to format strings according to the mask > --------------------------------------------------------------------------- > > Key: DROOLS-1485 > URL: https://issues.jboss.org/browse/DROOLS-1485 > Project: Drools > Issue Type: Feature Request > Components: dmn engine > Affects Versions: 7.0.0.Beta7 > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Fix For: 7.0.0.Final > > > Add a second signature to the string() function that works like the java String.format() method and allows the user to format strings in arbitrary ways. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2254) InterdependentDeploymentTestCase fails with security manager

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2254?page=com.atlassian.jira.plugi... ] Ingo Weiss updated WFCORE-2254: ------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2174, https://github.com/wildfly/wildfly-core/pull/2264 (was: https://github.com/wildfly/wildfly-core/pull/2174) > InterdependentDeploymentTestCase fails with security manager > ------------------------------------------------------------ > > Key: WFCORE-2254 > URL: https://issues.jboss.org/browse/WFCORE-2254 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Jan Tymel > Assignee: Ingo Weiss > Fix For: 3.0.0.Alpha25 > > > *org.jboss.as.test.manualmode.deployment.InterdependentDeploymentTestCase#test* > {{cd testsuite/manualmode/}} > {{mvn test -DtestLogToFile=false -Dtest=InterdependentDeploymentTestCase -Dsecurity.manager}} > {code} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service ServiceActivatorDeployment.c: org.jboss.msc.service.StartException in service ServiceActivatorDeployment.c: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978) > at org.jboss.msc.service.MSCExecutor$1.run(MSCExecutor.java:77) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.util.PropertyPermission" "interrelated-c.jar" "write")" in code source "(vfs:/content/interrelated-a.jar <no signer certificates>)" of "ModuleClassLoader for Module "deployment.interrelated-a.jar" from Service Module Loader") > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:278) > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175) > at java.lang.System.setProperty(System.java:792) > at org.jboss.as.test.deployment.trivial.ServiceActivatorDeployment.start(ServiceActivatorDeployment.java:91) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) > ... 4 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2546) Typo in description of Elytron aggregate-principal-transformer

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2546?page=com.atlassian.jira.plugi... ] Ilia Vassilev reassigned WFCORE-2546: ------------------------------------- Assignee: Ilia Vassilev (was: Darran Lofthouse) > Typo in description of Elytron aggregate-principal-transformer > -------------------------------------------------------------- > > Key: WFCORE-2546 > URL: https://issues.jboss.org/browse/WFCORE-2546 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > > There is typo in description of Elytron aggregate-principal-transformer in CLI. There is {{principa}} instead of {{principal}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8402) DescriptorScheduleTestCase fails when upgrading to jboss metadata 10.0.1.Final

by Panagiotis Sotiropoulos (JIRA)

Panagiotis Sotiropoulos created WFLY-8402: --------------------------------------------- Summary: DescriptorScheduleTestCase fails when upgrading to jboss metadata 10.0.1.Final Key: WFLY-8402 URL: https://issues.jboss.org/browse/WFLY-8402 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Panagiotis Sotiropoulos Assignee: Panagiotis Sotiropoulos DescriptorScheduleTestCase fails when upgrading to jboss metadata 10.0.1.Final because of https://github.com/jboss/metadata/blob/master/ejb/src/main/java/org/jboss... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1485) Add a string( mask, p... ) function to format strings according to the mask

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-1485: ------------------------------------- Summary: Add a string( mask, p... ) function to format strings according to the mask Key: DROOLS-1485 URL: https://issues.jboss.org/browse/DROOLS-1485 Project: Drools Issue Type: Feature Request Components: dmn engine Affects Versions: 7.0.0.Beta7 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 7.0.0.Final Add a second signature to the string() function that works like the java String.format() method and allows the user to format strings in arbitrary ways. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1484) Move SessionPseudoClock to public kie-api

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1484?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-1484. --------------------------------- Fix Version/s: 7.0.0.Beta8 Resolution: Done Implemented by https://github.com/kiegroup/droolsjbpm-knowledge/commit/563c5271fe054fd0c... https://github.com/kiegroup/drools/commit/66ef7b36a3bb72f976643a9c5107dcb... https://github.com/kiegroup/jbpm/commit/a2d34131bd3ae7e1d0657cdc2c216019c... > Move SessionPseudoClock to public kie-api > ----------------------------------------- > > Key: DROOLS-1484 > URL: https://issues.jboss.org/browse/DROOLS-1484 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 7.0.0.Beta8 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1473) Create a camel component to integrate the kie-server

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1473?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-1473: ------------------------------------- Implemented by https://github.com/kiegroup/droolsjbpm-build-bootstrap/commit/1d8166b484f... and https://github.com/kiegroup/droolsjbpm-integration/commit/e2ba2d3ed2fc559... I'm not resolving this jira yet because it is still necessary to find an automatic mechanism to know if a given parameter should be read by the header or the body of the camel's exchange. > Create a camel component to integrate the kie-server > ---------------------------------------------------- > > Key: DROOLS-1473 > URL: https://issues.jboss.org/browse/DROOLS-1473 > Project: Drools > Issue Type: Bug > Components: integration > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-30) [QE] - Upgrade CFME from Tech Preview release to CFME 4.5 release

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-30?page=com.atlassian.jira.plu... ] Hayk Hovsepyan resolved HAWKULARQE-30. -------------------------------------- Release Notes Text: Upgrade is tested, no regression or Bug was found. Resolution: Done > [QE] - Upgrade CFME from Tech Preview release to CFME 4.5 release > ----------------------------------------------------------------- > > Key: HAWKULARQE-30 > URL: https://issues.jboss.org/browse/HAWKULARQE-30 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Critical > > This task supposes to have setup Tech Preview CFME containers , including CFME, Hawkular Services, Cassandra and EAP7 containers. > The task is to upgrade all these Containers into CFME 4.5 release images. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 March 2017