[JBoss JIRA] (WFCORE-2533) DeploymentRolloutFailureTestCase fails with security manager in WF core
by Jan Tymel (JIRA)
Jan Tymel created WFCORE-2533:
---------------------------------
Summary: DeploymentRolloutFailureTestCase fails with security manager in WF core
Key: WFCORE-2533
URL: https://issues.jboss.org/browse/WFCORE-2533
Project: WildFly Core
Issue Type: Bug
Components: Test Suite
Reporter: Jan Tymel
Assignee: Tomaz Cerar
*org.jboss.as.test.integration.domain.suites.DeploymentRolloutFailureTestCase#test*
{{cd testsuite/domain/}}
{{mvn test -Dtest=DeploymentRolloutFailureTestCase -Dsecurity.manager -DtestLogToFile=false}}
{code}
[Server:main-three] 13:08:06,210 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "broken.jar" (runtime-name: "broken.jar")
[Server:main-three] 13:08:06,318 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service test.deployment.broken: org.jboss.msc.service.StartException in service test.deployment.broken: Failed to start service
[Server:main-three] 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:main-three] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [rt.jar:1.8.0]
[Server:main-three] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [rt.jar:1.8.0]
[Server:main-three] at java.lang.Thread.run(Thread.java:785) [vm.jar:1.8.0]
[Server:main-three] Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.util.PropertyPermission" "test.deployment.broken.fail" "read")" in code source "(vfs:/content/broken.jar <no signer certificates>)" of "ModuleClassLoader for Module "deployment.broken.jar" from Service Module Loader")
[Server:main-three] 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:main-three] at org.wildfly.security.manager.WildFlySecurityManager.checkPropertyAccess(WildFlySecurityManager.java:469) [wildfly-elytron-1.1.0.Beta27-redhat-1.jar:1.1.0.Beta27-redhat-1]
[Server:main-three] at java.lang.System.getProperty(System.java:443) [vm.jar:1.8.0]
[Server:main-three] at java.lang.System.getProperty(System.java:427) [vm.jar:1.8.0]
[Server:main-three] at java.lang.Boolean.getBoolean(Boolean.java:265) [rt.jar:1.8.0]
[Server:main-three] at org.jboss.as.test.integration.domain.deployment.broken.ServiceActivatorDeployment.start(ServiceActivatorDeployment.java:54)
[Server:main-three] 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:main-three] 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:main-three] ... 3 more
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2533) DeploymentRolloutFailureTestCase fails with security manager in WF core
by Jan Tymel (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2533?page=com.atlassian.jira.plugi... ]
Jan Tymel reassigned WFCORE-2533:
---------------------------------
Assignee: (was: Tomaz Cerar)
> DeploymentRolloutFailureTestCase fails with security manager in WF core
> -----------------------------------------------------------------------
>
> Key: WFCORE-2533
> URL: https://issues.jboss.org/browse/WFCORE-2533
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Reporter: Jan Tymel
>
> *org.jboss.as.test.integration.domain.suites.DeploymentRolloutFailureTestCase#test*
> {{cd testsuite/domain/}}
> {{mvn test -Dtest=DeploymentRolloutFailureTestCase -Dsecurity.manager -DtestLogToFile=false}}
> {code}
> [Server:main-three] 13:08:06,210 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "broken.jar" (runtime-name: "broken.jar")
> [Server:main-three] 13:08:06,318 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service test.deployment.broken: org.jboss.msc.service.StartException in service test.deployment.broken: Failed to start service
> [Server:main-three] 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:main-three] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [rt.jar:1.8.0]
> [Server:main-three] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [rt.jar:1.8.0]
> [Server:main-three] at java.lang.Thread.run(Thread.java:785) [vm.jar:1.8.0]
> [Server:main-three] Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.util.PropertyPermission" "test.deployment.broken.fail" "read")" in code source "(vfs:/content/broken.jar <no signer certificates>)" of "ModuleClassLoader for Module "deployment.broken.jar" from Service Module Loader")
> [Server:main-three] 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:main-three] at org.wildfly.security.manager.WildFlySecurityManager.checkPropertyAccess(WildFlySecurityManager.java:469) [wildfly-elytron-1.1.0.Beta27-redhat-1.jar:1.1.0.Beta27-redhat-1]
> [Server:main-three] at java.lang.System.getProperty(System.java:443) [vm.jar:1.8.0]
> [Server:main-three] at java.lang.System.getProperty(System.java:427) [vm.jar:1.8.0]
> [Server:main-three] at java.lang.Boolean.getBoolean(Boolean.java:265) [rt.jar:1.8.0]
> [Server:main-three] at org.jboss.as.test.integration.domain.deployment.broken.ServiceActivatorDeployment.start(ServiceActivatorDeployment.java:54)
> [Server:main-three] 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:main-three] 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:main-three] ... 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 Jan Tymel (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2532?page=com.atlassian.jira.plugi... ]
Jan Tymel reassigned WFCORE-2532:
---------------------------------
Assignee: (was: Tomaz Cerar)
> 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: 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
[JBoss JIRA] (WFCORE-2532) Some logging tests fail with security manager in WF core
by Jan Tymel (JIRA)
Jan Tymel created WFCORE-2532:
---------------------------------
Summary: 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: Test Suite
Reporter: Jan Tymel
Assignee: Tomaz Cerar
* *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
[JBoss JIRA] (WFCORE-2530) :read-boot-errors() operation does not follow its operation description
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2530?page=com.atlassian.jira.plugi... ]
ehsavoie Hugonnet reassigned WFCORE-2530:
-----------------------------------------
Assignee: ehsavoie Hugonnet
> :read-boot-errors() operation does not follow its operation description
> -----------------------------------------------------------------------
>
> Key: WFCORE-2530
> URL: https://issues.jboss.org/browse/WFCORE-2530
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 3.0.0.Beta7
> Reporter: Harald Pehl
> Assignee: ehsavoie Hugonnet
>
> The reply properties of the {{:read-boot-errors()}} operation lists the attribute {{missing-transitive-dependency-problems}} which is defined as
> {code}
> "missing-transitive-dependency-problems" => {
> "type" => OBJECT,
> "description" => "Missing transitive dependency issues found during execution of the operation.",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "value-type" => {
> "services-missing-transitive-dependencies" => {
> "type" => LIST,
> "description" => "Services that had a missing transitive dependency.",
> "expressions-allowed" => false,
> "required" => true,
> "nillable" => false,
> "value-type" => STRING
> },
> "possible-causes" => {
> "type" => LIST,
> "description" => "Services that are missing and may be the cause of the missing transitive dependency.",
> "expressions-allowed" => false,
> "required" => true,
> "nillable" => false,
> "value-type" => STRING
> }
> }
> }
> {code}
> However the result uses the strings "Services that were unable to start:" and "Services that may be the cause:" instead of {{services-missing-transitive-dependencies}} and {{possible-causes}}:
> {code}
> ...
> "missing-transitive-dependency-problems" => {
> "Services that were unable to start:" => ["jboss.messaging-activemq.default.jms.manager"],
> "Services that may be the cause:" => [
> "jboss.http-upgrade-registry.default",
> "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
> ]
> }
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2530) :read-boot-errors() operation does not follow its operation description
by Harald Pehl (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2530?page=com.atlassian.jira.plugi... ]
Harald Pehl updated WFCORE-2530:
--------------------------------
Affects Version/s: 3.0.0.Beta7
> :read-boot-errors() operation does not follow its operation description
> -----------------------------------------------------------------------
>
> Key: WFCORE-2530
> URL: https://issues.jboss.org/browse/WFCORE-2530
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 3.0.0.Beta7
> Reporter: Harald Pehl
>
> The reply properties of the {{:read-boot-errors()}} operation lists the attribute {{missing-transitive-dependency-problems}} which is defined as
> {code}
> "missing-transitive-dependency-problems" => {
> "type" => OBJECT,
> "description" => "Missing transitive dependency issues found during execution of the operation.",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "value-type" => {
> "services-missing-transitive-dependencies" => {
> "type" => LIST,
> "description" => "Services that had a missing transitive dependency.",
> "expressions-allowed" => false,
> "required" => true,
> "nillable" => false,
> "value-type" => STRING
> },
> "possible-causes" => {
> "type" => LIST,
> "description" => "Services that are missing and may be the cause of the missing transitive dependency.",
> "expressions-allowed" => false,
> "required" => true,
> "nillable" => false,
> "value-type" => STRING
> }
> }
> }
> {code}
> However the result uses the strings "Services that were unable to start:" and "Services that may be the cause:" instead of {{services-missing-transitive-dependencies}} and {{possible-causes}}:
> {code}
> ...
> "missing-transitive-dependency-problems" => {
> "Services that were unable to start:" => ["jboss.messaging-activemq.default.jms.manager"],
> "Services that may be the cause:" => [
> "jboss.http-upgrade-registry.default",
> "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
> ]
> }
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-1802) Ensure OpenSSL Registration is first.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1802?page=com.atlassian.jira.plugi... ]
Darran Lofthouse reopened WFCORE-1802:
--------------------------------------
> Ensure OpenSSL Registration is first.
> -------------------------------------
>
> Key: WFCORE-1802
> URL: https://issues.jboss.org/browse/WFCORE-1802
> Project: WildFly Core
> Issue Type: Task
> Components: Security
> Reporter: Stuart Douglas
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 3.0.0.Beta8
>
>
> The following in SecurityRealmResourceDefinition registers the provider: -
> {code}
> static {
> //register the Openssl Provider, if possible
> //not really sure if this is the best place for it
> try {
> OpenSSLProvider.register();
> DomainManagementLogger.ROOT_LOGGER.registeredOpenSSLProvider();
> } catch (Throwable t){
> DomainManagementLogger.ROOT_LOGGER.debugf(t, "Failed to register OpenSSL provider");
> }
> }
> {code}
> It would be good to remove this however for now we can't guarantee Elytron is enabled so register it globally.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2530) :read-boot-errors() operation does not follow its operation description
by Harald Pehl (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2530?page=com.atlassian.jira.plugi... ]
Harald Pehl updated WFCORE-2530:
--------------------------------
Description:
The reply properties of the {{:read-boot-errors()}} operation lists the attribute {{missing-transitive-dependency-problems}} which is defined as
{code}
"missing-transitive-dependency-problems" => {
"type" => OBJECT,
"description" => "Missing transitive dependency issues found during execution of the operation.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"value-type" => {
"services-missing-transitive-dependencies" => {
"type" => LIST,
"description" => "Services that had a missing transitive dependency.",
"expressions-allowed" => false,
"required" => true,
"nillable" => false,
"value-type" => STRING
},
"possible-causes" => {
"type" => LIST,
"description" => "Services that are missing and may be the cause of the missing transitive dependency.",
"expressions-allowed" => false,
"required" => true,
"nillable" => false,
"value-type" => STRING
}
}
}
{code}
However the result uses the strings "Services that were unable to start:" and "Services that may be the cause:" instead of {{services-missing-transitive-dependencies}} and {{possible-causes}}:
{code}
...
"missing-transitive-dependency-problems" => {
"Services that were unable to start:" => ["jboss.messaging-activemq.default.jms.manager"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
]
}
...
{code}
was:
The reply properties of the {{:read-boot-errors()}} operation lists the attribute {{missing-transitive-dependency-problems}} which is defined as
{code}
"missing-transitive-dependency-problems" => {
"type" => OBJECT,
"description" => "Missing transitive dependency issues found during execution of the operation.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"value-type" => {
"services-missing-transitive-dependencies" => {
"type" => LIST,
"description" => "Services that had a missing transitive dependency.",
"expressions-allowed" => false,
"required" => true,
"nillable" => false,
"value-type" => STRING
},
"possible-causes" => {
"type" => LIST,
"description" => "Services that are missing and may be the cause of the missing transitive dependency.",
"expressions-allowed" => false,
"required" => true,
"nillable" => false,
"value-type" => STRING
}
}
}
{code}
However the result uses the string "Services that were unable to start:" and "Services that may be the cause:" instead of {{services-missing-transitive-dependencies}} and {{possible-causes}}:
{code}
...
"missing-transitive-dependency-problems" => {
"Services that were unable to start:" => ["jboss.messaging-activemq.default.jms.manager"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
]
}
...
{code}
> :read-boot-errors() operation does not follow its operation description
> -----------------------------------------------------------------------
>
> Key: WFCORE-2530
> URL: https://issues.jboss.org/browse/WFCORE-2530
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Harald Pehl
>
> The reply properties of the {{:read-boot-errors()}} operation lists the attribute {{missing-transitive-dependency-problems}} which is defined as
> {code}
> "missing-transitive-dependency-problems" => {
> "type" => OBJECT,
> "description" => "Missing transitive dependency issues found during execution of the operation.",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "value-type" => {
> "services-missing-transitive-dependencies" => {
> "type" => LIST,
> "description" => "Services that had a missing transitive dependency.",
> "expressions-allowed" => false,
> "required" => true,
> "nillable" => false,
> "value-type" => STRING
> },
> "possible-causes" => {
> "type" => LIST,
> "description" => "Services that are missing and may be the cause of the missing transitive dependency.",
> "expressions-allowed" => false,
> "required" => true,
> "nillable" => false,
> "value-type" => STRING
> }
> }
> }
> {code}
> However the result uses the strings "Services that were unable to start:" and "Services that may be the cause:" instead of {{services-missing-transitive-dependencies}} and {{possible-causes}}:
> {code}
> ...
> "missing-transitive-dependency-problems" => {
> "Services that were unable to start:" => ["jboss.messaging-activemq.default.jms.manager"],
> "Services that may be the cause:" => [
> "jboss.http-upgrade-registry.default",
> "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
> ]
> }
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month