June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3900) Bump the kernel management API version to 8.0.0 and the xsd to 8.0

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3900?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3900: -------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.0.0.Alpha1) > Bump the kernel management API version to 8.0.0 and the xsd to 8.0 > ------------------------------------------------------------------ > > Key: WFCORE-3900 > URL: https://issues.jboss.org/browse/WFCORE-3900 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Brian Stansberry > Assignee: Jeff Mesnil > Fix For: 6.0.0.Alpha1 > > > We know there are going to be API changes in WF Core 5, so we need to get the API version bumped so that when those changes happen appropriate transformers can be written to transform to the previous version. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3900) Bump the kernel management API version to 8.0.0 and the xsd to 8.0

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3900?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-3900: -------------------------------- Description: We know there are going to be API changes in WF Core 6, so we need to get the API version bumped so that when those changes happen appropriate transformers can be written to transform to the previous version. (was: We know there are going to be API changes in WF Core 5, so we need to get the API version bumped so that when those changes happen appropriate transformers can be written to transform to the previous version.) > Bump the kernel management API version to 8.0.0 and the xsd to 8.0 > ------------------------------------------------------------------ > > Key: WFCORE-3900 > URL: https://issues.jboss.org/browse/WFCORE-3900 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Brian Stansberry > Assignee: Jeff Mesnil > Fix For: 6.0.0.Alpha1 > > > We know there are going to be API changes in WF Core 6, so we need to get the API version bumped so that when those changes happen appropriate transformers can be written to transform to the previous version. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-618) Dead code in DEREncoder

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/ELY-618?page=com.atlassian.jira.plugin.sy... ] Ilia Vassilev reassigned ELY-618: --------------------------------- Assignee: Ilia Vassilev > Dead code in DEREncoder > ----------------------- > > Key: ELY-618 > URL: https://issues.jboss.org/browse/ELY-618 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta7 > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > Labels: static_analysis > > There is an unintentional dead code in writeTag method of org.wildfly.security.asn1.DEREncoder. Variable {{tagNumber}} can be assigned to 31 as its maximal value from {{int tagNumber = tag & TAG_NUMBER_MASK;}} (because {{TAG_NUMBER_MASK = 0x1f}}) on line 576 [1] which means that condition {{if (tagNumber < 128)}} on line 582 is always true. It causes that else branch is never executed. > [1] https://github.com/wildfly-security/wildfly-elytron/blob/4453ea40a7a617b6... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3830) JAVA_OPTS is not passed to PC and HC JVMs in domain.ps1

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3830?page=com.atlassian.jira.plugi... ] Marek Kopecký updated WFCORE-3830: ---------------------------------- Description: JAVA_OPTS is not passed to PC and HC JVMs in domain.ps1 Steps to reproduce: # start powershell # $env:JAVA_OPTS = "-Da=b" # ./domain.bat # WMIC PROCESS get Commandline | findstr java # check that "a" property is present in PC or HC # exit domain.bat # ./domain.ps1 # WMIC PROCESS get Commandline | findstr java # check that "a" property is *not* present in PC or HC cc: [~jamezp] was: JAVA_OPTS is not passed to DC and HC JVMs in domain.ps1 Steps to reproduce: # start powershell # $env:JAVA_OPTS = "-Da=b" # ./domain.bat # WMIC PROCESS get Commandline | findstr java # check that "a" property is present in DC or HC # exit domain.bat # ./domain.ps1 # WMIC PROCESS get Commandline | findstr java # check that "a" property is *not* present in DC or HC cc: [~jamezp] > JAVA_OPTS is not passed to PC and HC JVMs in domain.ps1 > ------------------------------------------------------- > > Key: WFCORE-3830 > URL: https://issues.jboss.org/browse/WFCORE-3830 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Marek Kopecký > Assignee: R Searls > Priority: Critical > > JAVA_OPTS is not passed to PC and HC JVMs in domain.ps1 > Steps to reproduce: > # start powershell > # $env:JAVA_OPTS = "-Da=b" > # ./domain.bat > # WMIC PROCESS get Commandline | findstr java > # check that "a" property is present in PC or HC > # exit domain.bat > # ./domain.ps1 > # WMIC PROCESS get Commandline | findstr java > # check that "a" property is *not* present in PC or HC > cc: [~jamezp] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3830) JAVA_OPTS is not passed to PC and HC JVMs in domain.ps1

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3830?page=com.atlassian.jira.plugi... ] Marek Kopecký commented on WFCORE-3830: --------------------------------------- [~brian.stansberry]: You are right, I updated description of this jira. Thank you for the explanation! > JAVA_OPTS is not passed to PC and HC JVMs in domain.ps1 > ------------------------------------------------------- > > Key: WFCORE-3830 > URL: https://issues.jboss.org/browse/WFCORE-3830 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Marek Kopecký > Assignee: R Searls > Priority: Critical > > JAVA_OPTS is not passed to PC and HC JVMs in domain.ps1 > Steps to reproduce: > # start powershell > # $env:JAVA_OPTS = "-Da=b" > # ./domain.bat > # WMIC PROCESS get Commandline | findstr java > # check that "a" property is present in PC or HC > # exit domain.bat > # ./domain.ps1 > # WMIC PROCESS get Commandline | findstr java > # check that "a" property is *not* present in PC or HC > cc: [~jamezp] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3830) JAVA_OPTS is not passed to PC and HC JVMs in domain.ps1

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3830?page=com.atlassian.jira.plugi... ] Marek Kopecký updated WFCORE-3830: ---------------------------------- Summary: JAVA_OPTS is not passed to PC and HC JVMs in domain.ps1 (was: JAVA_OPTS is not passed to DC and HC JVMs in domain.ps1) > JAVA_OPTS is not passed to PC and HC JVMs in domain.ps1 > ------------------------------------------------------- > > Key: WFCORE-3830 > URL: https://issues.jboss.org/browse/WFCORE-3830 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Marek Kopecký > Assignee: R Searls > Priority: Critical > > JAVA_OPTS is not passed to DC and HC JVMs in domain.ps1 > Steps to reproduce: > # start powershell > # $env:JAVA_OPTS = "-Da=b" > # ./domain.bat > # WMIC PROCESS get Commandline | findstr java > # check that "a" property is present in DC or HC > # exit domain.bat > # ./domain.ps1 > # WMIC PROCESS get Commandline | findstr java > # check that "a" property is *not* present in DC or HC > cc: [~jamezp] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2532: ------------------------------------- [~uxdlc] Hi, thanks for the wireframes. Just one question, I see 3 tabs in the right dock, however one tab is not shown in wireframes I think, could you please provide more details? - 1. tab: syntax cheetsheet - 2. tab: results of scenario run (looks pretty nice, thanks!) - 3. tab: ? > UX design for scenario simulation > --------------------------------- > > Key: DROOLS-2532 > URL: https://issues.jboss.org/browse/DROOLS-2532 > Project: Drools > Issue Type: Task > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: Appformer, UX, UXTeam > Attachments: roundE-scaled.pdf > > > As Aimee or Cameron I want to: > * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision. > * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT. > * Run a test scenario simulation so that I can verify the expected results against test simulation results. > Verification conditions: > Provide wireframe design and click-thru prototype which includes the following views: > * Overview (properties) > * Scenario Template > * Scenarios Input Screen > * Results > * Code View -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3830) JAVA_OPTS is not passed to DC and HC JVMs in domain.ps1

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3830?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3830: ------------------------------------------ N.B. The term DC is not meaningful in this context. A Host Controller is a kind of java process that exists in a WildFly managed domain. The term Domain Controller is used for an HC that has a few particular settings in its xml config that cause it to perform a particular role as the master controlling other slave HCs. But it's still an HC process. The scripts have nothing to do with whether a particular HC is a master or a slave. In discussions of scripts they are all HCs. There's another process type in a managed domain that is relevant to the scripts -- the Process Controller. The PC is the java process that is actually started by the scripts. The PC is actually the one that spawns the HC process, not the scripts. (The PC also spawns the 3rd type of managed domain process, the actual appserver processes.) Part of what you can to in the various .conf files is manipulate PROCESS_CONTROLLER_JAVA_OPTS and HOST_CONTROLLER_JAVA_OPTS, which allow you to have separate control over opts passed by the script directly to the PC JVM it launches vs those passed as strings to the PC and used by it internally when it launches the HC. The default value for both PROCESS_CONTROLLER_JAVA_OPTS and HOST_CONTROLLER_JAVA_OPTS is whatever the value of JAVA_OPTS is. (The primary reason we have PROCESS_CONTROLLER_JAVA_OPTS and HOST_CONTROLLER_JAVA_OPTS is to allow debugging to be turned on separately for the PC or HC.) > JAVA_OPTS is not passed to DC and HC JVMs in domain.ps1 > ------------------------------------------------------- > > Key: WFCORE-3830 > URL: https://issues.jboss.org/browse/WFCORE-3830 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Marek Kopecký > Assignee: R Searls > Priority: Critical > > JAVA_OPTS is not passed to DC and HC JVMs in domain.ps1 > Steps to reproduce: > # start powershell > # $env:JAVA_OPTS = "-Da=b" > # ./domain.bat > # WMIC PROCESS get Commandline | findstr java > # check that "a" property is present in DC or HC > # exit domain.bat > # ./domain.ps1 > # WMIC PROCESS get Commandline | findstr java > # check that "a" property is *not* present in DC or HC > cc: [~jamezp] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10482) Wildfly 12.0.0.Final sets response header server:Wildfly/11

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10482?page=com.atlassian.jira.plugin... ] Brian Stansberry resolved WFLY-10482. ------------------------------------- Fix Version/s: 13.0.0.Beta1 Resolution: Done This was fixed as part of the change for WFLY-9947. > Wildfly 12.0.0.Final sets response header server:Wildfly/11 > ----------------------------------------------------------- > > Key: WFLY-10482 > URL: https://issues.jboss.org/browse/WFLY-10482 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 12.0.0.Final > Environment: all > Reporter: Puzzle ITC > Assignee: Jason Greene > Priority: Minor > Fix For: 13.0.0.Beta1 > > > Wildfly 12.0.0.Final sets response header server:Wildfly/11 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3897) Host starts with server assigned to non-existent server group

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3897?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3897: ------------------------------------------ [~soul2zimate] Re: "The HC only check required server group existence in server start. In this case, servers are configured to auto-start="false", no error indicates any misconfiguration." What's odd to me is that the capability reference at https://github.com/wildfly/wildfly-core/blob/master/host-controller/src/m... is not being validated at the end of boot. Capability references should be validated regardless of whether a server is started. The logic that validates the model can't know and shouldn't care whether the server is configured to start. That capability reference is checked after boot, which is why write ops start to fail. So I think it's probably something in the logic during HC boot that disables some reference checks until both the host.xml model and domain.xml model are present. When only host.xml stuff is present (i.e. boot has parsed the host.xml file but the domain.xml part isn't ready yet) then some capability refs checks are turned off. But IRRC the idea was once the domain model was available the checks would be done. The "PartialModelIndicator" at https://github.com/wildfly/wildfly-core/blob/master/host-controller/src/m... is meant to control whether this check happens. > Host starts with server assigned to non-existent server group > ------------------------------------------------------------- > > Key: WFCORE-3897 > URL: https://issues.jboss.org/browse/WFCORE-3897 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 5.0.0.CR1 > Reporter: Chao Wang > Assignee: Chao Wang > > Configuring a host with: > <server name="server-one" group="main-server-group" auto-start="false"/> > <server name="server-two" group="main-server-group" auto-start="false"> > <socket-bindings port-offset="150"/> > </server> > And no server-goup with that name in the domain.xml, the host starts and all management operations fail. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 June 2018