March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3715) JBOSS_HOME is unset in powershell scripts

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3715?page=com.atlassian.jira.plugi... ] Lin Gao moved JBEAP-14508 to WFCORE-3715: ----------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-3715 (was: JBEAP-14508) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Scripts (was: Scripts) Affects Version/s: (was: 7.0.9.GA) Fix Version/s: (was: 7.1.3.GA) > JBOSS_HOME is unset in powershell scripts > ----------------------------------------- > > Key: WFCORE-3715 > URL: https://issues.jboss.org/browse/WFCORE-3715 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Environment: Windows power-shell. > Reporter: Lin Gao > > When using ps1 (power-shell) scripts in a windows environment the JBOSS_HOME environment variable is always unset at the end. For example using the {{jboss-cli.ps1}} script. > That variable can be set by the user and this not be affected by the execution of the scripts. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-100) Install Kiali as Addon on Istio Ansible Pipeline

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-100?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo moved KIALI-409 to SWSQE-100: ----------------------------------------------------- Project: Swift Sunshine QE (was: Kiali) Key: SWSQE-100 (was: KIALI-409) Issue Type: Task (was: Dev Task) Workflow: GIT Pull Request workflow (was: SWS Workflow) > Install Kiali as Addon on Istio Ansible Pipeline > ------------------------------------------------ > > Key: SWSQE-100 > URL: https://issues.jboss.org/browse/SWSQE-100 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > > Jaeger, Zipkin are installed as part of Istio Official Ansible Pipeline > (https://github.com/istio/istio/blob/master/install/ansible/istio/tasks/in...) > I think Kiali would need to be part of this too -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9636) EJB lookup over HTTP times out connection after 60 seconds

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-9636?page=com.atlassian.jira.plugin.... ] Stuart Douglas resolved WFLY-9636. ---------------------------------- Fix Version/s: 13.0.0.Beta1 Resolution: Done > EJB lookup over HTTP times out connection after 60 seconds > ---------------------------------------------------------- > > Key: WFLY-9636 > URL: https://issues.jboss.org/browse/WFLY-9636 > Project: WildFly > Issue Type: Bug > Components: EJB, IO, Naming > Affects Versions: 11.0.0.Final > Environment: I work with https://developer.jboss.org/people/jaikiran on https://developer.jboss.org/thread/276635 so my Wildfly 11 environment has this fix in it. > Reporter: peter craddock > Assignee: Stuart Douglas > Fix For: 13.0.0.Beta1 > > > The code examples and trace logging can be found here https://developer.jboss.org/thread/276840 > I have work round the problem but was asked to raise it for further investigation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9895) HTTP Client 1.0.11.Final

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-9895?page=com.atlassian.jira.plugin.... ] Stuart Douglas resolved WFLY-9895. ---------------------------------- Fix Version/s: 13.0.0.Beta1 Resolution: Done > HTTP Client 1.0.11.Final > ------------------------ > > Key: WFLY-9895 > URL: https://issues.jboss.org/browse/WFLY-9895 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 13.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10135) Upgrade WildFly HTTP client 1.0.12.Final

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-10135: --------------------------------------- Summary: Upgrade WildFly HTTP client 1.0.12.Final Key: WFLY-10135 URL: https://issues.jboss.org/browse/WFLY-10135 Project: WildFly Issue Type: Component Upgrade Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 13.0.0.Beta1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10134) ee8.preview.mode property is racy

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10134?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-10134: ----------------------------------------- [~dmlloyd] Perhaps this non-extension module (i.e. kernel depends on it): https://github.com/wildfly/wildfly-core/blame/master/core-feature-pack/sr... which leads to this: https://github.com/wildfly/wildfly-core/blame/master/core-feature-pack/sr... This is nothing new though. And it doesn't match your traces, since ServerService Thread Pool shouldn't be loading the kernel-dependency modules, and the undertow extension wouldn't be in the mix. OTOH I don't see why this wouldn't have been a problem long ago, unless JBoss Modules defers loading optional=true modules until....<draws a blank/>. > ee8.preview.mode property is racy > --------------------------------- > > Key: WFLY-10134 > URL: https://issues.jboss.org/browse/WFLY-10134 > Project: WildFly > Issue Type: Bug > Components: EE > Reporter: David Lloyd > Priority: Critical > > The {{ee8-temp}} tests set the {{ee8.preview.mode}} property in the server management model, relying on system properties to get parsed and set before extensions which use Java EE 8 APIs are loaded. This assumption appears to be invalid. > System properties are installed by the boot controller thread, and extensions are loaded in server service threads. In testing with the latest jboss-modules, I've observed cases where the controller thread does not add system properties until after some extension loading has happened in the server service threads. I haven't untangled why this happens only with the most recent jboss-modules in play, but the race exists regardless. > Setting the {{ee8.preview.mode}} in {{arquillian.xml}} appears to work around the issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10134) ee8.preview.mode property is racy

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-10134?page=com.atlassian.jira.plugin... ] David Lloyd commented on WFLY-10134: ------------------------------------ >From my TRACE test output, it looks like {{javax.servlet.api}} is loaded by the Undertow extension (in this case by {{ServerService Thread Pool \-\- 65}}) chronologically ahead of the system property configuration being processed (which happens in {{Controller Boot Thread}}). > ee8.preview.mode property is racy > --------------------------------- > > Key: WFLY-10134 > URL: https://issues.jboss.org/browse/WFLY-10134 > Project: WildFly > Issue Type: Bug > Components: EE > Reporter: David Lloyd > Priority: Critical > > The {{ee8-temp}} tests set the {{ee8.preview.mode}} property in the server management model, relying on system properties to get parsed and set before extensions which use Java EE 8 APIs are loaded. This assumption appears to be invalid. > System properties are installed by the boot controller thread, and extensions are loaded in server service threads. In testing with the latest jboss-modules, I've observed cases where the controller thread does not add system properties until after some extension loading has happened in the server service threads. I haven't untangled why this happens only with the most recent jboss-modules in play, but the race exists regardless. > Setting the {{ee8.preview.mode}} in {{arquillian.xml}} appears to work around the issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10134) ee8.preview.mode property is racy

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10134?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-10134: ----------------------------------------- I have no idea how this could happen, unless the ExtensionXml is not being passed a DeferredExtensionContext in its constructor. And even then it shouldn't be racy, it should be a 100% case of the extension being loaded before the standalone.xml system property is set. (The extension loading is done by the server service threads but the controller boot thread blocks waiting for that parallel work to finish.) What modules are you seeing loaded that you don't expect? > ee8.preview.mode property is racy > --------------------------------- > > Key: WFLY-10134 > URL: https://issues.jboss.org/browse/WFLY-10134 > Project: WildFly > Issue Type: Bug > Components: EE > Reporter: David Lloyd > Priority: Critical > > The {{ee8-temp}} tests set the {{ee8.preview.mode}} property in the server management model, relying on system properties to get parsed and set before extensions which use Java EE 8 APIs are loaded. This assumption appears to be invalid. > System properties are installed by the boot controller thread, and extensions are loaded in server service threads. In testing with the latest jboss-modules, I've observed cases where the controller thread does not add system properties until after some extension loading has happened in the server service threads. I haven't untangled why this happens only with the most recent jboss-modules in play, but the race exists regardless. > Setting the {{ee8.preview.mode}} in {{arquillian.xml}} appears to work around the issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3705) Allow dependencies on JDK modules

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3705?page=com.atlassian.jira.plugi... ] David Lloyd updated WFCORE-3705: -------------------------------- Labels: Java9 (was: ) > Allow dependencies on JDK modules > --------------------------------- > > Key: WFCORE-3705 > URL: https://issues.jboss.org/browse/WFCORE-3705 > Project: WildFly Core > Issue Type: Feature Request > Components: Modules > Reporter: David Lloyd > Assignee: David Lloyd > Labels: Java9 > > Allow dependencies on JDK modules in Java 9 and higher. Emulate the set of Java 9 JDK modules on Java 8. > Deprecate old JDK aggregation modules such as {{javax.api}} and {{sun.jdk}}, and start moving towards their standard replacements. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-62) End to end test in parallel fashion - PoC

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-62?page=com.atlassian.jira.plugin.s... ] Filip Brychta resolved SWSQE-62. -------------------------------- Resolution: Done Demo was shown. Jenkins slaves on demand can be used for parallel execution of jobs. > End to end test in parallel fashion - PoC > ----------------------------------------- > > Key: SWSQE-62 > URL: https://issues.jboss.org/browse/SWSQE-62 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Filip Brychta > > Working on prototype of scenario where we will run several UI test groups parallelly using jenkins slaves in OS on demand -- This message was sent by Atlassian JIRA (v7.5.0#75005)

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