February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3409) embed-server doesn't honor "module.path" system property

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3409?page=com.atlassian.jira.plugi... ] Ken Wills commented on WFCORE-3409: ----------------------------------- [~ctomc] Emmanuel is supposed to have these issues ATM, I'm doing cloud stuff. I approve of this change though! :) > embed-server doesn't honor "module.path" system property > -------------------------------------------------------- > > Key: WFCORE-3409 > URL: https://issues.jboss.org/browse/WFCORE-3409 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 4.0.0.Alpha2 > Reporter: Tomaz Cerar > Assignee: Ken Wills > > Every other parts of server and launchers (including embed-host-controller) honor the "module.path" system property for setting modules path. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3409) embed-server doesn't honor "module.path" system property

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3409?page=com.atlassian.jira.plugi... ] Ken Wills reassigned WFCORE-3409: --------------------------------- Assignee: ehsavoie Hugonnet (was: Ken Wills) > embed-server doesn't honor "module.path" system property > -------------------------------------------------------- > > Key: WFCORE-3409 > URL: https://issues.jboss.org/browse/WFCORE-3409 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 4.0.0.Alpha2 > Reporter: Tomaz Cerar > Assignee: ehsavoie Hugonnet > > Every other parts of server and launchers (including embed-host-controller) honor the "module.path" system property for setting modules path. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3576) deployment is not accessible in runtime when deployed with runtime-name not using .war extension

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3576?page=com.atlassian.jira.plugi... ] Chao Wang commented on WFCORE-3576: ----------------------------------- mentioned discussion on wildfly-dev http://lists.jboss.org/pipermail/wildfly-dev/2018-January/006299.html > deployment is not accessible in runtime when deployed with runtime-name not using .war extension > ------------------------------------------------------------------------------------------------ > > Key: WFCORE-3576 > URL: https://issues.jboss.org/browse/WFCORE-3576 > Project: WildFly Core > Issue Type: Enhancement > Components: Deployment Scanner, Domain Management > Affects Versions: 4.0.0.Alpha9 > Reporter: Jan Stourac > Assignee: Chao Wang > > According to the folowing [blog-post|https://developer.jboss.org/thread/221251], when using custom --name or --runtime-name for deployment, the file extension (.war, .jar, .ear,...) need to be included so server can distinguish type of deployment somehow. > Currently there is no such check - when I try to deploy any .war app using either web-console or CLI with my custom '\-\-runtime-name' and/or '\-\-name' without .war suffix, server does not complain anyhow: > {code} > deploy --runtime-name=alice --name=bob /tmp/eve.war > {code} > Message in server log: > {code} > 17:30:48,469 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "bob" (runtime-name: "alice") > 17:30:48,499 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0010: Deployed "bob" (runtime-name : "alice") > {code} > Although, when I try to access content of the war app via URL, I get only {{404 Not found}} HTTP response. Also I cannot see any deployment content when browsing via CLI: > {code} > /deployment=bob/subsystem=undertow/... > {code} > Even when I raise logging level to DEBUG, I can see no suspicious messages that deployed app has not been completely deployed. > If such suffix is required, we need to inform user about it. We need to update description text for '\-\-name' and '\-\-runtime-name' atributes of deploy command in CLI (see {{deploy --help}}). Also when no such suffix is provided (and/or we fail to distinguish type of deployment in a different way) we need to print error message that deploy operation was not completely successful so customer is aware of it right-away. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3579) ERROR log occurs during CLI reload operation on server

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3579?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3579: ------------------------------------------ I think the fix is probably in ModelControllerClientFactoryImpl.LocalClient. The executeAsync method is using AccessAuditContext.doAs but executeOperation is not. ModelControllerImpl checks for the presence of an AccessAuditContext to detect user calls. OTOH I'm not sure executeAsync should be using AccessAuditContext.doAs if forUserCalls is false. See also WFCORE-13. > ERROR log occurs during CLI reload operation on server > ------------------------------------------------------ > > Key: WFCORE-3579 > URL: https://issues.jboss.org/browse/WFCORE-3579 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Domain Management > Affects Versions: 4.0.0.Alpha9 > Reporter: Marek Kopecký > Assignee: Brian Stansberry > Priority: Blocker > Attachments: cli.script.txt > > > *Description of the issue:* > ERROR log occurs during CLI reload operation on server: > {{ERROR \[org.jboss.as.controller.management-operation\] (pool-3-thread-2) WFLYCTL0013: Operation ("read-attribute") failed - address: (\[("host" => "master")\]) - failure description: "WFLYCTL0201: Unknown attribute 'host-state'"}} > This issue is regression against WF11 > Reload handler and its "host-state" code is [here|https://github.com/wildfly/wildfly-core/blob/master/cli/src/main/jav...], but this issue is probably caused by some "debug -> error" logging change ... > I'm able to reproduce this only on embedded server. Non-embedded server is probably too slow to hit this issue > *How reproducible:* > I see this intermittently on fast virtual machines > *Steps to Reproduce:* > # ./jboss-cli.sh --file=cli.script.txt > *Content of cli.script.txt file* > This file is attached to this jira, beginning of this file: > {noformat} > embed-host-controller --std-out=echo > reload --host=master --admin-only=true > reload --host=master --admin-only=true > reload --host=master --admin-only=true > reload --host=master --admin-only=true > reload --host=master --admin-only=true > reload --host=master --admin-only=true > reload --host=master --admin-only=true > {noformat} > *Actual results:* > Standard output: > {noformat} > ... > [0m[0m01:36:06,021 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 12.0.0.Alpha1-SNAPSHOT (WildFly Core 4.0.0.Alpha9) starting > [0m[31m01:36:06,061 ERROR [org.jboss.as.controller.management-operation] (CLI command executor) WFLYCTL0013: Operation ("read-attribute") failed - address: ([("host" => "master")]) - failure description: "WFLYCTL0201: Unknown attribute 'host-state'" > [0m[0m01:36:06,072 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=native-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [0m[0m01:36:06,073 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/host=master/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [0m[0m01:36:06,097 INFO [org.jboss.as.patching] (MSC service thread 1-3) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none > [0m[33m01:36:06,102 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-1) WFLYDM0111: Keystore /home/hudson/hudson_workspace/workspace/early-testing-cli-embedded-manual/4b767fc2/wildfly/domain/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost > [0m[0m01:36:06,185 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=default/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [0m[0m01:36:06,196 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=ha/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [0m[0m01:36:06,204 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [0m[0m01:36:06,217 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/profile=full-ha/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > [0m[0m01:36:06,287 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 12.0.0.Alpha1-SNAPSHOT (WildFly Core 4.0.0.Alpha9) (Host Controller) started in 266ms - Started 54 of 59 services (18 services are lazy, passive or on-demand) > ... > {noformat} > *Expected results:* > No errors in logs -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3576) deployment is not accessible in runtime when deployed with runtime-name not using .war extension

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3576?page=com.atlassian.jira.plugi... ] Chao Wang updated WFCORE-3576: ------------------------------ Git Pull Request: (was: https://github.com/wildfly/wildfly-core/pull/3084) > deployment is not accessible in runtime when deployed with runtime-name not using .war extension > ------------------------------------------------------------------------------------------------ > > Key: WFCORE-3576 > URL: https://issues.jboss.org/browse/WFCORE-3576 > Project: WildFly Core > Issue Type: Enhancement > Components: Deployment Scanner, Domain Management > Affects Versions: 4.0.0.Alpha9 > Reporter: Jan Stourac > Assignee: Chao Wang > > According to the folowing [blog-post|https://developer.jboss.org/thread/221251], when using custom --name or --runtime-name for deployment, the file extension (.war, .jar, .ear,...) need to be included so server can distinguish type of deployment somehow. > Currently there is no such check - when I try to deploy any .war app using either web-console or CLI with my custom '\-\-runtime-name' and/or '\-\-name' without .war suffix, server does not complain anyhow: > {code} > deploy --runtime-name=alice --name=bob /tmp/eve.war > {code} > Message in server log: > {code} > 17:30:48,469 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "bob" (runtime-name: "alice") > 17:30:48,499 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0010: Deployed "bob" (runtime-name : "alice") > {code} > Although, when I try to access content of the war app via URL, I get only {{404 Not found}} HTTP response. Also I cannot see any deployment content when browsing via CLI: > {code} > /deployment=bob/subsystem=undertow/... > {code} > Even when I raise logging level to DEBUG, I can see no suspicious messages that deployed app has not been completely deployed. > If such suffix is required, we need to inform user about it. We need to update description text for '\-\-name' and '\-\-runtime-name' atributes of deploy command in CLI (see {{deploy --help}}). Also when no such suffix is provided (and/or we fail to distinguish type of deployment in a different way) we need to print error message that deploy operation was not completely successful so customer is aware of it right-away. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3589) WildFly Elytron Tool is regressed vs 3.x

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3589?page=com.atlassian.jira.plugi... ] Darran Lofthouse commented on WFCORE-3589: ------------------------------------------ I would not worry about an intermediate PR for this, when I tag Elytron 1.2.0.Final it should come in with a corresponding Elytron Tool update otherwise we will have two different elytron tool versions in a single release. > WildFly Elytron Tool is regressed vs 3.x > ---------------------------------------- > > Key: WFCORE-3589 > URL: https://issues.jboss.org/browse/WFCORE-3589 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > The WildFly Elytron Tool version in the pom is 1.0.0.Final vs 1.0.5.Final in 3.x. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3589) WildFly Elytron Tool is regressed vs 3.x

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3589: ---------------------------------------- Summary: WildFly Elytron Tool is regressed vs 3.x Key: WFCORE-3589 URL: https://issues.jboss.org/browse/WFCORE-3589 Project: WildFly Core Issue Type: Bug Components: Security Reporter: Brian Stansberry Assignee: Brian Stansberry The WildFly Elytron Tool version in the pom is 1.0.0.Final vs 1.0.5.Final in 3.x. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9615) Upgrade to Bean Validation 2.0 and Hibernate Validator 6.0 in ee8.preview.mode

by Guillaume Smet (JIRA)

[ https://issues.jboss.org/browse/WFLY-9615?page=com.atlassian.jira.plugin.... ] Guillaume Smet updated WFLY-9615: --------------------------------- Summary: Upgrade to Bean Validation 2.0 and Hibernate Validator 6.0 in ee8.preview.mode (was: Upgrade to Bean Validation 2.0 and Hibernate Validator 6.0) > Upgrade to Bean Validation 2.0 and Hibernate Validator 6.0 in ee8.preview.mode > ------------------------------------------------------------------------------ > > Key: WFLY-9615 > URL: https://issues.jboss.org/browse/WFLY-9615 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Guillaume Smet > Assignee: Jason Greene > Fix For: 12.0.0.Alpha1 > > > We would like to upgrade Hibernate Validator to 6.0.7.Final in WildFly 12. > Here is our migration guide: > https://developer.jboss.org/wiki/HibernateValidatorMigrationGuide#jive_co... > You'll notice that in 6.0.6, we have reintroduced a few APIs that we had removed in the previous versions of 6 for this WF upgrade: we had them deprecated in 5.4 then removed in 6 but as WF is still using 5.3, WF users didn't have any notice of that. That's why we decided to reintroduce them before proposing an upgrade in WildFly. > The other APIs removed were marked as experimental and have been superseded by standard features in Bean Validation 2.0 (which is part of Java EE 8). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9615) Upgrade to Bean Validation 2.0 and Hibernate Validator 6.0 in ee8.preview.mode

by Guillaume Smet (JIRA)

[ https://issues.jboss.org/browse/WFLY-9615?page=com.atlassian.jira.plugin.... ] Guillaume Smet updated WFLY-9615: --------------------------------- Fix Version/s: 12.0.0.Alpha1 > Upgrade to Bean Validation 2.0 and Hibernate Validator 6.0 in ee8.preview.mode > ------------------------------------------------------------------------------ > > Key: WFLY-9615 > URL: https://issues.jboss.org/browse/WFLY-9615 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Guillaume Smet > Assignee: Jason Greene > Fix For: 12.0.0.Alpha1 > > > We would like to upgrade Hibernate Validator to 6.0.7.Final in WildFly 12. > Here is our migration guide: > https://developer.jboss.org/wiki/HibernateValidatorMigrationGuide#jive_co... > You'll notice that in 6.0.6, we have reintroduced a few APIs that we had removed in the previous versions of 6 for this WF upgrade: we had them deprecated in 5.4 then removed in 6 but as WF is still using 5.3, WF users didn't have any notice of that. That's why we decided to reintroduce them before proposing an upgrade in WildFly. > The other APIs removed were marked as experimental and have been superseded by standard features in Bean Validation 2.0 (which is part of Java EE 8). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9783) Upgrade WildFly Build Tools to 1.2.8.Final

by Guillaume Smet (JIRA)

Guillaume Smet created WFLY-9783: ------------------------------------ Summary: Upgrade WildFly Build Tools to 1.2.8.Final Key: WFLY-9783 URL: https://issues.jboss.org/browse/WFLY-9783 Project: WildFly Issue Type: Component Upgrade Components: Build System Reporter: Guillaume Smet Assignee: Guillaume Smet Fix For: 12.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 February 2018