April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2668) Explode content with DeploymentPlan doesn't work properly

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created WFCORE-2668: ----------------------------------------- Summary: Explode content with DeploymentPlan doesn't work properly Key: WFCORE-2668 URL: https://issues.jboss.org/browse/WFCORE-2668 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 3.0.0.Beta14 Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet The explode content of deployment plan doesn't work -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6191) ExpressionSubstitutionInContainerTestCase fails due to AccessControlException with security manager enabled

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-6191?page=com.atlassian.jira.plugin.... ] Ivo Studensky reopened WFLY-6191: --------------------------------- Reopening due to a downstream issue reported by QE. > ExpressionSubstitutionInContainerTestCase fails due to AccessControlException with security manager enabled > ----------------------------------------------------------------------------------------------------------- > > Key: WFLY-6191 > URL: https://issues.jboss.org/browse/WFLY-6191 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Hynek Švábek > Assignee: Ivo Studensky > > *org.jboss.as.test.integration.management.api.expression.ExpressionSubstitutionInContainerTestCase* > {{./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.management.api.expression.ExpressionSubstitutionInContainerTestCase}} > {code} > Failed to start service jboss.deployment.unit."expression-substitution-test.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."expression-substitution-test.jar".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "expression-substitution-test.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > 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.lang.RuntimePermission" "getClassLoader")" in code source "(vfs:/content/expression-substitution-test.jar <no signer certificates>)" of "null") > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:273) > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175) > at java.lang.ClassLoader.checkClassLoaderPermission(ClassLoader.java:1525) > at java.lang.Class.getClassLoader(Class.java:683) > at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1529) > at org.jboss.msc.service.ServiceControllerImpl.access$2800(ServiceControllerImpl.java:51) > at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:2099) > at org.jboss.msc.service.ServiceControllerImpl.commitInstallation(ServiceControllerImpl.java:265) > at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:771) > at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) > at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) > at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) > at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) > at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) > at org.jboss.as.test.integration.management.api.expression.ExpressionTestManagementService.activate(ExpressionTestManagementService.java:69) > at org.jboss.as.server.deployment.service.ServiceActivatorProcessor.deploy(ServiceActivatorProcessor.java:74) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) > ... 5 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8567) Enable Messaging SecurityTestCase fails with Elytron profile in AS TS

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8567?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-8567: ----------------------------------- Summary: Enable Messaging SecurityTestCase fails with Elytron profile in AS TS (was: Messaging SecurityTestCase fails with Elytron profile in AS TS) > Enable Messaging SecurityTestCase fails with Elytron profile in AS TS > --------------------------------------------------------------------- > > Key: WFLY-8567 > URL: https://issues.jboss.org/browse/WFLY-8567 > Project: WildFly > Issue Type: Bug > Components: JMS, Security, Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 11.0.0.Beta1 > > > The {{SecurityTestCase#testFailedAuthenticationBlankUserPass()}} test fails when executed with Elytron profile ({{-Delytron}}). > {code} > cd testsuite/integration/basic > mvn clean test -Dtest=SecurityTestCase -Delytron -Dwildfly.tmp.enable.elytron.profile.tests=true > ... > Failed tests: > SecurityTestCase.testFailedAuthenticationBlankUserPass:84 must not allow to create a session without any authentication > Tests run: 6, Failures: 1, Errors: 0, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8567) Messaging SecurityTestCase fails with Elytron profile in AS TS

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8567?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-8567: ----------------------------------- Fix Version/s: 11.0.0.Beta1 > Messaging SecurityTestCase fails with Elytron profile in AS TS > -------------------------------------------------------------- > > Key: WFLY-8567 > URL: https://issues.jboss.org/browse/WFLY-8567 > Project: WildFly > Issue Type: Bug > Components: JMS, Security, Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 11.0.0.Beta1 > > > The {{SecurityTestCase#testFailedAuthenticationBlankUserPass()}} test fails when executed with Elytron profile ({{-Delytron}}). > {code} > cd testsuite/integration/basic > mvn clean test -Dtest=SecurityTestCase -Delytron -Dwildfly.tmp.enable.elytron.profile.tests=true > ... > Failed tests: > SecurityTestCase.testFailedAuthenticationBlankUserPass:84 must not allow to create a session without any authentication > Tests run: 6, Failures: 1, Errors: 0, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8567) Messaging SecurityTestCase fails with Elytron profile in AS TS

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8567?page=com.atlassian.jira.plugin.... ] Darran Lofthouse moved JBEAP-10318 to WFLY-8567: ------------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8567 (was: JBEAP-10318) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS Security Test Suite (was: JMS) (was: Security) (was: Test Suite) Affects Version/s: (was: 7.1.0.DR12) > Messaging SecurityTestCase fails with Elytron profile in AS TS > -------------------------------------------------------------- > > Key: WFLY-8567 > URL: https://issues.jboss.org/browse/WFLY-8567 > Project: WildFly > Issue Type: Bug > Components: JMS, Security, Test Suite > Reporter: Darran Lofthouse > > The {{SecurityTestCase#testFailedAuthenticationBlankUserPass()}} test fails when executed with Elytron profile ({{-Delytron}}). > {code} > cd testsuite/integration/basic > mvn clean test -Dtest=SecurityTestCase -Delytron -Dwildfly.tmp.enable.elytron.profile.tests=true > ... > Failed tests: > SecurityTestCase.testFailedAuthenticationBlankUserPass:84 must not allow to create a session without any authentication > Tests run: 6, Failures: 1, Errors: 0, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8567) Messaging SecurityTestCase fails with Elytron profile in AS TS

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8567?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-8567: -------------------------------------- Assignee: Darran Lofthouse > Messaging SecurityTestCase fails with Elytron profile in AS TS > -------------------------------------------------------------- > > Key: WFLY-8567 > URL: https://issues.jboss.org/browse/WFLY-8567 > Project: WildFly > Issue Type: Bug > Components: JMS, Security, Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > > The {{SecurityTestCase#testFailedAuthenticationBlankUserPass()}} test fails when executed with Elytron profile ({{-Delytron}}). > {code} > cd testsuite/integration/basic > mvn clean test -Dtest=SecurityTestCase -Delytron -Dwildfly.tmp.enable.elytron.profile.tests=true > ... > Failed tests: > SecurityTestCase.testFailedAuthenticationBlankUserPass:84 must not allow to create a session without any authentication > Tests run: 6, Failures: 1, Errors: 0, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8565) org.wildfly.undertow.http-invoker.host capability violates its own contract

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8565?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-8565: ----------------------------------- fixed to not expose anything as the service itself doesn't expose itself as well. updated docs https://github.com/wildfly/wildfly-capabilities/pull/17 > org.wildfly.undertow.http-invoker.host capability violates its own contract > --------------------------------------------------------------------------- > > Key: WFLY-8565 > URL: https://issues.jboss.org/browse/WFLY-8565 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Priority: Critical > > According to the definition of the "org.wildfly.undertow.http-invoker.host" capability, it provides a PathHandler service[1], but the installed service[2] exposes the HttpInvokerHostService instance itself[3]. > [1] https://github.com/jbossas/jboss-eap7/blob/7.x/undertow/src/main/java/org... > [2] https://github.com/jbossas/jboss-eap7/blob/7.x/undertow/src/main/java/org... > [3] https://github.com/jbossas/jboss-eap7/blob/7.x/undertow/src/main/java/org... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8565) org.wildfly.undertow.http-invoker.host capability violates its own contract

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8565?page=com.atlassian.jira.plugin.... ] Tomaz Cerar moved JBEAP-10317 to WFLY-8565: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8565 (was: JBEAP-10317) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Web (Undertow) (was: Web (Undertow)) > org.wildfly.undertow.http-invoker.host capability violates its own contract > --------------------------------------------------------------------------- > > Key: WFLY-8565 > URL: https://issues.jboss.org/browse/WFLY-8565 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Priority: Critical > > According to the definition of the "org.wildfly.undertow.http-invoker.host" capability, it provides a PathHandler service[1], but the installed service[2] exposes the HttpInvokerHostService instance itself[3]. > [1] https://github.com/jbossas/jboss-eap7/blob/7.x/undertow/src/main/java/org... > [2] https://github.com/jbossas/jboss-eap7/blob/7.x/undertow/src/main/java/org... > [3] https://github.com/jbossas/jboss-eap7/blob/7.x/undertow/src/main/java/org... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8566) Welcome page gives 404 if JBOSS_HOME contains lower case drive letter (Windows)

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8566?page=com.atlassian.jira.plugin.... ] Tomaz Cerar moved JBEAP-10316 to WFLY-8566: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8566 (was: JBEAP-10316) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Server Web (Undertow) (was: Server) (was: Web (Undertow)) Affects Version/s: (was: 7.1.0.DR16) Affects Testing: (was: Regression) > Welcome page gives 404 if JBOSS_HOME contains lower case drive letter (Windows) > ------------------------------------------------------------------------------- > > Key: WFLY-8566 > URL: https://issues.jboss.org/browse/WFLY-8566 > Project: WildFly > Issue Type: Bug > Components: Server, Web (Undertow) > Environment: Windows > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Priority: Blocker > > *Description of problem:* > EAP server welcome page (aka http://localhost:8080/ ) returns "404 - Not Found" once the JBOSS_HOME contains lower case drive letter on Windows. > This is regression against 6.4.0, 7.0.0, 7.1.0.DR15, so priority of this jira is blocker > Similar jira from 7.0: JBEAP-2054 > *Steps to Reproduce:* > # start the EAP using absolute path with lower case drive letter: {{C:\Users\Administrator>c:\Users\Administrator\playground\7.1.0.DR16\jboss-eap-7.1\bin\standalone.bat}} > # get the response from welcome page{noformat} > C:\Users\Administrator>wget64.exe --server-response --spider http://localhost:8080 > Spider mode enabled. Check if remote file exists. > --2017-04-10 10:34:21-- http://localhost:8080/ > Resolving localhost (localhost)... ::1, 127.0.0.1 > Connecting to localhost (localhost)|::1|:8080... failed: Bad file descriptor. > Connecting to localhost (localhost)|127.0.0.1|:8080... connected. > HTTP request sent, awaiting response... > HTTP/1.1 404 Not Found > Connection: keep-alive > X-Powered-By: Undertow/1 > Server: JBoss-EAP/7 > Content-Length: 74 > Content-Type: text/html > Date: Mon, 10 Apr 2017 08:34:22 GMT > Remote file does not exist -- broken link!!! > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2667) CLI returns always "0" if CLI is started with "cmd /c " on Windows

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2667?page=com.atlassian.jira.plugi... ] Jean-Francois Denise moved JBEAP-10314 to WFCORE-2667: ------------------------------------------------------ Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2667 (was: JBEAP-10314) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: CLI Scripts (was: CLI) (was: Scripts) Affects Version/s: (was: 7.1.0.DR16) Affects Testing: (was: Regression) > CLI returns always "0" if CLI is started with "cmd /c " on Windows > ------------------------------------------------------------------ > > Key: WFCORE-2667 > URL: https://issues.jboss.org/browse/WFCORE-2667 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Scripts > Environment: Windows > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > Priority: Critical > > *Description of problem:* > CLI returns always "0" if CLI is started with "cmd /c " on Windows > This issue is regression against EAP 7.0.0, but priority of this jira is not blocker, because this issue is corner case. > *Steps to Reproduce:* > # jboss-cli.bat --command=version_error > # echo Exit Code is %errorlevel% > # REM verify correct return value: 1 > # cmd /c jboss-cli.bat --command=version_error > # echo Exit Code is %errorlevel% > # REM return value is 0 in EAP 7.1.0.DR16. Correct return value should be 1 > *Actual results:* > {noformat} > C:\Users\Administrator\playground\7.1.0.DR16\jboss-eap-7.1\bin>jboss-cli.bat --command=version_error > Unexpected command 'version_error'. Type 'help --commands' for the list of supported commands. > C:\Users\Administrator\playground\7.1.0.DR16\jboss-eap-7.1\bin>echo Exit Code is %errorlevel% > Exit Code is 1 > C:\Users\Administrator\playground\7.1.0.DR16\jboss-eap-7.1\bin> > C:\Users\Administrator\playground\7.1.0.DR16\jboss-eap-7.1\bin>cmd /c jboss-cli.bat --command=version_error > Unexpected command 'version_error'. Type 'help --commands' for the list of supported commands. > C:\Users\Administrator\playground\7.1.0.DR16\jboss-eap-7.1\bin>echo Exit Code is %errorlevel% > Exit Code is 0 > C:\Users\Administrator\playground\7.1.0.DR16\jboss-eap-7.1\bin> > {noformat} > *Expected results:* > {noformat} > C:\Users\Administrator\playground\7.0.0\jboss-eap-7.0\bin>jboss-cli.bat --command=version_error > Unexpected command 'version_error'. Type 'help --commands' for the list of supported commands. > C:\Users\Administrator\playground\7.0.0\jboss-eap-7.0\bin>echo Exit Code is %errorlevel% > Exit Code is 1 > C:\Users\Administrator\playground\7.0.0\jboss-eap-7.0\bin> > C:\Users\Administrator\playground\7.0.0\jboss-eap-7.0\bin>cmd /c jboss-cli.bat --command=version_error > Unexpected command 'version_error'. Type 'help --commands' for the list of supported commands. > C:\Users\Administrator\playground\7.0.0\jboss-eap-7.0\bin>echo Exit Code is %errorlevel% > Exit Code is 1 > C:\Users\Administrator\playground\7.0.0\jboss-eap-7.0\bin> > {noformat} > *Additional info:* > We see this issue also if jboss-cli.bat script is called from groovy or java -- 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 April 2017