[JBoss JIRA] (WFCORE-2558) If an op fails but isn't rolled back, the response doesn't report non-rollback
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-2558:
----------------------------------------
Summary: If an op fails but isn't rolled back, the response doesn't report non-rollback
Key: WFCORE-2558
URL: https://issues.jboss.org/browse/WFCORE-2558
Project: WildFly Core
Issue Type: Enhancement
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
If an op rolls back, the response includes "rolled-back"=>true. But if a failure occurs but the op doesn't roll back (because the rollback-on-runtime-failure operation header was set to false) there is no "rolled-back"=>false in the response. The effect of the operation is therefore unclear to the user.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ELY-1014) Elytron auth method misconfiguration not logged
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-1014?page=com.atlassian.jira.plugin.s... ]
Jan Kalina moved WFCORE-2432 to ELY-1014:
-----------------------------------------
Project: WildFly Elytron (was: WildFly Core)
Key: ELY-1014 (was: WFCORE-2432)
Component/s: Authentication Mechanisms
(was: Security)
> Elytron auth method misconfiguration not logged
> -----------------------------------------------
>
> Key: ELY-1014
> URL: https://issues.jboss.org/browse/ELY-1014
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Authentication Mechanisms
> Reporter: Martin Choma
> Assignee: Jan Kalina
> Priority: Blocker
> Labels: user_experience
>
> When deployment is configured to be secured with DIGEST, but {{http-authentication-factory}} does not list DIGEST mechanism, user is not informed about misconfiguration. Even when TRACE logging is turned on. When user tries to access app 403 http code is returned and Forbidden is shown in browser. I would expect browser dialog to appear to allow user provide credentials (401 http status code).
> {code:title=web.xml}
> <login-config>
> <auth-method>DIGEST</auth-method>
> <realm-name>ApplicaitonRealm</realm-name>
> </login-config>
> {code}
> {code:title=standalone-elytron.xml}
> <http-authentication-factory name="application-http-authentication" http-server-mechanism-factory="global" security-domain="ApplicationDomain">
> <mechanism-configuration>
> <mechanism mechanism-name="BASIC">
> <mechanism-realm realm-name="Application Realm"/>
> </mechanism>
> <mechanism mechanism-name="FORM"/>
> </mechanism-configuration>
> </http-authentication-factory>
> {code}
> This applies globally to all authentication mechanisms, not only DIGEST.
> Could elytron handle misconfiguration:
> * either fail during deploying application as deployment requirement can't be satisfy
> * or provide reasonable elytron defaults of missing mechanism configuration.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[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:
------------------------------------------
WFCORE-1762 relates to my most recent comment on WFCORE-2351 as the WFCORE-1762 change will ensure that an ERROR is logged if an op introduces MSC failures or missing services and none of the other op verification techniques detect that. One of the benefits of the current ContainerStateMonitor INFO level logging is it would at least produce some output in that kind of situation, but that benefit would now be covered in a better way by WFCORE-1762.
That makes me comfortable with having the ContainerStateMonitor INFO level logging only log the final status at the end of the op, after any rollback work. Which means in most cases no logging at all.
With that I also think the ContainerStateMonitor should be a WARN if the report shows any problems, and INFO otherwise. If the final result of the op is MSC is left with installed services that failed or having missing dependencies, that should be a WARN.
> 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
[JBoss JIRA] (WFCORE-1762) Missing dependency should be triggering rollback of the deployment operation
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1762?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFCORE-1762:
----------------------------------------
Assignee: Brian Stansberry
> Missing dependency should be triggering rollback of the deployment operation
> ----------------------------------------------------------------------------
>
> Key: WFCORE-1762
> URL: https://issues.jboss.org/browse/WFCORE-1762
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 3.0.0.Alpha7
> Reporter: Martin Stefanko
> Assignee: Brian Stansberry
>
> The removal of the deployment which is a dependency for other resources makes these dependent resources unusable. The deployment operation should not be completed in such conditions.
> The information about the missing dependencies is now currently logged after the removal by the ContainerStateMonitor class.
> Example:
> {code}INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment postgresql-9.4.1208.jar (runtime-name: postgresql-9.4.1208.jar) in 61ms
> INFO [org.jboss.as.server] (ServerService Thread Pool -- 65) WFLYSRV0009: Undeployed "postgresql-9.4.1208.jar" (runtime-name: "postgresql-9.4.1208.jar")
> INFO [org.jboss.as.repository] (ServerService Thread Pool -- 65) WFLYDR0002: Content removed from location /home/mjurc/testing/eap/7.0.0/jboss-eap-7.0/standalone/data/content/5c/7e80698b80a5045fe64daa67426051bbd16a56/content
> INFO [org.jboss.as.controller] (ServerService Thread Pool -- 65) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.jdbc-driver.postgresql-9_4_1208_jar (missing) dependents: [service jboss.driver-demander.java:/PostgresDS, service org.wildfly.data-source.PostgresDS]
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-1762) Missing dependency should be triggering rollback of the deployment operation
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1762?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-1762:
------------------------------------------
The specific problem here is the no-longer-available service is not one that was directly removed by the management op. Instead it's a child service of the one the op removed (a great-great-great grandchild really). The result of that is the OperationContext doesn't know how to associate the missing dependency with the step that caused the problem.
I don't know how to make that association. If the problem op is a step in a composite it's not possible to identify the specific step in the composite that broke things.
But it's possible to detect that the overall op has triggered a missing dependency and that no step has been reported as problematic. If that happens, a failure message can be associated with the main operation response. If its a composite the particular step won't get the failure description, but the overall op will and hopefully the user can figure out the problem step.
This kind of thing mostly can happen when something outside a deployment depends on a service created when the deployment is deployed. So, inter-deployment dependencies, or like here a container service depending on a deployment service. The management op knows about root deployment service. But it's a great-great-great grandchild of that root deployment service that becomes the missing dependency.
> Missing dependency should be triggering rollback of the deployment operation
> ----------------------------------------------------------------------------
>
> Key: WFCORE-1762
> URL: https://issues.jboss.org/browse/WFCORE-1762
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 3.0.0.Alpha7
> Reporter: Martin Stefanko
>
> The removal of the deployment which is a dependency for other resources makes these dependent resources unusable. The deployment operation should not be completed in such conditions.
> The information about the missing dependencies is now currently logged after the removal by the ContainerStateMonitor class.
> Example:
> {code}INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment postgresql-9.4.1208.jar (runtime-name: postgresql-9.4.1208.jar) in 61ms
> INFO [org.jboss.as.server] (ServerService Thread Pool -- 65) WFLYSRV0009: Undeployed "postgresql-9.4.1208.jar" (runtime-name: "postgresql-9.4.1208.jar")
> INFO [org.jboss.as.repository] (ServerService Thread Pool -- 65) WFLYDR0002: Content removed from location /home/mjurc/testing/eap/7.0.0/jboss-eap-7.0/standalone/data/content/5c/7e80698b80a5045fe64daa67426051bbd16a56/content
> INFO [org.jboss.as.controller] (ServerService Thread Pool -- 65) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.jdbc-driver.postgresql-9_4_1208_jar (missing) dependents: [service jboss.driver-demander.java:/PostgresDS, service org.wildfly.data-source.PostgresDS]
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-1762) Missing dependency should be triggering rollback of the deployment operation
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1762?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1762:
-------------------------------------
Component/s: Domain Management
> Missing dependency should be triggering rollback of the deployment operation
> ----------------------------------------------------------------------------
>
> Key: WFCORE-1762
> URL: https://issues.jboss.org/browse/WFCORE-1762
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 3.0.0.Alpha7
> Reporter: Martin Stefanko
>
> The removal of the deployment which is a dependency for other resources makes these dependent resources unusable. The deployment operation should not be completed in such conditions.
> The information about the missing dependencies is now currently logged after the removal by the ContainerStateMonitor class.
> Example:
> {code}INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment postgresql-9.4.1208.jar (runtime-name: postgresql-9.4.1208.jar) in 61ms
> INFO [org.jboss.as.server] (ServerService Thread Pool -- 65) WFLYSRV0009: Undeployed "postgresql-9.4.1208.jar" (runtime-name: "postgresql-9.4.1208.jar")
> INFO [org.jboss.as.repository] (ServerService Thread Pool -- 65) WFLYDR0002: Content removed from location /home/mjurc/testing/eap/7.0.0/jboss-eap-7.0/standalone/data/content/5c/7e80698b80a5045fe64daa67426051bbd16a56/content
> INFO [org.jboss.as.controller] (ServerService Thread Pool -- 65) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.jdbc-driver.postgresql-9_4_1208_jar (missing) dependents: [service jboss.driver-demander.java:/PostgresDS, service org.wildfly.data-source.PostgresDS]
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2535) ModuleResourceRootPathsTestCase fails with security manager in WF core
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2535?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-2535:
-------------------------------------
Component/s: CLI
> ModuleResourceRootPathsTestCase fails with security manager in WF core
> ----------------------------------------------------------------------
>
> Key: WFCORE-2535
> URL: https://issues.jboss.org/browse/WFCORE-2535
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Test Suite
> Reporter: Jan Tymel
>
> *org.jboss.as.test.integration.management.cli.modules.ModuleResourceRootPathsTestCase#testModules*
> {{cd testsuite/standalone/}}
> {{mvn test -Dtest=ModuleResourceRootPathsTestCase -Dsecurity.manager -DtestLogToFile=false}}
> {code}
> 13:26:00,583 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."test-archive.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."test-archive.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "test-archive.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.lang.Thread.run(Thread.java:785)
> Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.util.PropertyPermission" "jboss.bind.address" "read")" in code source "(vfs:/content/test-archive.war <no signer certificates>)" of "ModuleClassLoader for Module "deployment.test-archive.war" from Service Module Loader")
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:278)
> at org.wildfly.security.manager.WildFlySecurityManager.checkPropertyAccess(WildFlySecurityManager.java:469)
> at java.lang.System.getProperty(System.java:443)
> at java.lang.System.getProperty(System.java:427)
> at org.jboss.as.test.shared.TestSuiteEnvironment.getSystemProperty(TestSuiteEnvironment.java:50)
> at org.jboss.as.test.shared.TestSuiteEnvironment.getHttpAddress(TestSuiteEnvironment.java:173)
> at org.wildfly.test.undertow.UndertowServiceActivator.getAddress(UndertowServiceActivator.java:100)
> at org.wildfly.test.undertow.UndertowServiceActivator.activate(UndertowServiceActivator.java:66)
> at org.jboss.as.server.deployment.service.ServiceActivatorProcessor.deploy(ServiceActivatorProcessor.java:91)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
> ... 5 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2534) SlaveReconnectTestCase fails with security manager in WF core
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2534?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-2534:
-------------------------------------
Component/s: Domain Management
> SlaveReconnectTestCase fails with security manager in WF core
> -------------------------------------------------------------
>
> Key: WFCORE-2534
> URL: https://issues.jboss.org/browse/WFCORE-2534
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Test Suite
> Reporter: Jan Tymel
>
> *org.jboss.as.test.integration.domain.slavereconnect.SlaveReconnectTestCase#test01_OrderedExtensionsAndDeployments*
> *org.jboss.as.test.integration.domain.slavereconnect.SlaveReconnectTestCase#test02_DeploymentOverlays*
> {{cd testsuite/domain/}}
> {{mvn test -Dtest=SlaveReconnectTestCase -Dsecurity.manager -DtestLogToFile=false}}
> {code}
> [Server:server-affected] 13:16:12,425 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service test.deployment.one: org.jboss.msc.service.StartException in service test.deployment.one: Failed to start service
> [Server:server-affected] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978) [jboss-msc-1.2.7.SP1-redhat-1.jar:1.2.7.SP1-redhat-1]
> [Server:server-affected] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [rt.jar:1.8.0]
> [Server:server-affected] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [rt.jar:1.8.0]
> [Server:server-affected] at java.lang.Thread.run(Thread.java:785) [vm.jar:1.8.0]
> [Server:server-affected] Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.util.PropertyPermission" "test.deployment.prop.one" "write")" in code source "(vfs:/content/reconnect-slave-depone.jar <no signer certificates>)" of "ModuleClassLoader for Module "deployment.reconnect-slave-depone.jar" from Service Module Loader")
> [Server:server-affected] at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:278) [wildfly-elytron-1.1.0.Beta27-redhat-1.jar:1.1.0.Beta27-redhat-1]
> [Server:server-affected] at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175) [wildfly-elytron-1.1.0.Beta27-redhat-1.jar:1.1.0.Beta27-redhat-1]
> [Server:server-affected] at java.lang.System.setProperty(System.java:476) [vm.jar:1.8.0]
> [Server:server-affected] at org.jboss.as.test.integration.domain.slavereconnect.deployment.ServiceActivatorBaseDeployment.start(ServiceActivatorBaseDeployment.java:64)
> [Server:server-affected] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) [jboss-msc-1.2.7.SP1-redhat-1.jar:1.2.7.SP1-redhat-1]
> [Server:server-affected] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) [jboss-msc-1.2.7.SP1-redhat-1.jar:1.2.7.SP1-redhat-1]
> [Server:server-affected] ... 3 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2532) Some logging tests fail with security manager in WF core
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2532?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-2532:
-------------------------------------
Component/s: Logging
> Some logging tests fail with security manager in WF core
> --------------------------------------------------------
>
> Key: WFCORE-2532
> URL: https://issues.jboss.org/browse/WFCORE-2532
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging, Test Suite
> Reporter: Jan Tymel
>
> * *org.jboss.as.test.integration.logging.operations.CustomFormattersTestCase*
> * *org.jboss.as.test.integration.logging.operations.CustomHandlerOperationsTestCase*
> * *org.jboss.as.test.integration.logging.operations.CustomHandlerTestCase*
> * *org.jboss.as.test.integration.logging.operations.Log4jCustomHandlerTestCase*
> * *org.jboss.as.test.integration.logging.perdeploy.JBossLog4jXmlTestCase*
> * *org.jboss.as.test.integration.logging.perdeploy.JBossLoggingPropertiesTestCase*
> * *org.jboss.as.test.integration.logging.perdeploy.Log4jPropertiesTestCase*
> * *org.jboss.as.test.integration.logging.perdeploy.Log4jXmlTestCase*
> * *org.jboss.as.test.integration.logging.perdeploy.LoggingPropertiesTestCase*
> * *org.jboss.as.test.integration.logging.profiles.LoggingProfilesTestCase*
> * *org.jboss.as.test.integration.logging.profiles.NonExistingProfileTestCase*
> * *org.jboss.as.test.integration.logging.syslog.SyslogHandlerTestCase*
> {{cd testsuite/standalone/}}
> {{mvn test -Dtest=org.jboss.as.test.integration.logging.**.* -Dsecurity.manager}}
> {code}
> org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper$ServerDeploymentException: java.lang.Exception: {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"logging1.jar\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"logging1.jar\".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment \"logging1.jar\"
> Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission \"(\"java.util.PropertyPermission\" \"jboss.bind.address\" \"read\")\" in code source \"(vfs:/content/logging1.jar <no signer certificates>)\" of \"ModuleClassLoader for Module \"deployment.logging1.jar\" from Service Module Loader\")"},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"logging1.jar\".INSTALL"]
> }
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
> at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55)
> at org.jboss.as.test.integration.logging.AbstractLoggingTestCase.deploy(AbstractLoggingTestCase.java:168)
> at org.jboss.as.test.integration.logging.profiles.LoggingProfilesTestCase.deploy(LoggingProfilesTestCase.java:314)
> at org.jboss.as.test.integration.logging.profiles.LoggingProfilesTestCase.deploy(LoggingProfilesTestCase.java:304)
> at org.jboss.as.test.integration.logging.profiles.LoggingProfilesTestCase.testProfiles(LoggingProfilesTestCase.java:201
> {code}
> * *org.jboss.as.test.manualmode.logging.Log4jAppenderTestCase*
> * *org.jboss.as.test.manualmode.logging.LoggingPreferencesTestCase*
> * *org.jboss.as.test.manualmode.logging.PerDeployLoggingTestCase*
> * *org.jboss.as.test.manualmode.logging.ReconnectSyslogServerTestCase*
> * *org.jboss.as.test.manualmode.logging.SizeAppenderRestartTestCase*
> * *org.jboss.as.test.manualmode.logging.SyslogIsNotAvailableDuringServerBootTestCase*
> {{cd testsuite/manualmode/}}
> {{mvn test -Dtest=org.jboss.as.test.manualmode.logging.* -Dsecurity.manager}}
> {code}
> org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper$ServerDeploymentException: java.lang.Exception: {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"logging-test.jar\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"logging-test.jar\".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment \"logging-test.jar\"
> Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission \"(\"java.util.PropertyPermission\" \"jboss.bind.address\" \"read\")\" in code source \"(vfs:/content/logging-test.jar <no signer certificates>)\" of \"ModuleClassLoader for Module \"deployment.logging-test.jar\" from Service Module Loader\")"},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"logging-test.jar\".INSTALL"]
> }
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
> at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55)
> at org.wildfly.core.testrunner.ServerController.deploy(ServerController.java:92)
> at org.jboss.as.test.manualmode.logging.AbstractLoggingTestCase.deploy(AbstractLoggingTestCase.java:197)
> at org.jboss.as.test.manualmode.logging.Log4jAppenderTestCase.startContainer(Log4jAppenderTestCase.java:93)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month