January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4270) [GSS](7.2.z) Multiple <socket> elements inside an http-interface parsed wrongly

by Jörg Bäsner (Jira)

Jörg Bäsner created WFCORE-4270: ----------------------------------- Summary: [GSS](7.2.z) Multiple <socket> elements inside an http-interface parsed wrongly Key: WFCORE-4270 URL: https://issues.jboss.org/browse/WFCORE-4270 Project: WildFly Core Issue Type: Bug Components: Management Affects Versions: 8.0.0.Beta2 Reporter: Jörg Bäsner Assignee: Jeff Mesnil The definition of the _http-interface_ for the _management-interface_ in the {{wildfly-config_5_0.xsd}} is defined as: {code} <xs:complexType name="host-http-management-interfaceType"> <xs:annotation> <xs:documentation> Configuration of a host's exposed HTTP management interface. </xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="http-management-interfaceType"> <xs:sequence> <xs:element name="socket" type="host-http-management-socketType"/> </xs:sequence> <xs:attribute name="console-enabled" type="xs:boolean" use="optional" default="true"/> </xs:extension> </xs:complexContent> </xs:complexType> {code} Where _xs:sequence_ has a default definition of: * *maxOccurs* _Optional._ Specifies the maximum number of times the sequence element can occur in the parent element. The value can be any number >= 0, or if you want to set no limit on the maximum number, use the value "unbounded". Default value is 1 * *minOccurs* _Optional._ Specifies the minimum number of times the sequence element can occur in the parent element. The value can be any number >= 0. Default value is 1 But the parser allows to configure multiple sockets like this: {code} ... <security-realm name="ManagementRealm"> <server-identities> <ssl> <keystore path="server.keystore" relative-to="jboss.domain.config.dir" keystore-password="******" alias="server"/> </ssl> </server-identities> <authentication> <properties path="mgmt-users.properties" relative-to="jboss.domain.config.dir"/> </authentication> </security-realm> ... <http-interface security-realm="ManagementRealm"> <http-upgrade enabled="true"/> <socket interface="local" port="${jboss.management.local.http.port:9990}"/> <socket interface="management" secure-port="${jboss.management.https.port:9443}"/> </http-interface> ... <interfaces> <interface name="local"> <inet-address value="${jboss.bind.address.local.management:127.0.0.1}"/> </interface> <interface name="management"> <inet-address value="${jboss.bind.address.management:jbaesner.remote.csb}"/> </interface> </interfaces> ... {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4269) Multiple <socket> elements inside an http-interface parsed wrongly

by Jörg Bäsner (Jira)

Jörg Bäsner created WFCORE-4269: ----------------------------------- Summary: Multiple <socket> elements inside an http-interface parsed wrongly Key: WFCORE-4269 URL: https://issues.jboss.org/browse/WFCORE-4269 Project: WildFly Core Issue Type: Bug Components: Management Affects Versions: 8.0.0.Beta2 Reporter: Jörg Bäsner Assignee: Jeff Mesnil The definition of the _http-interface_ for the _management-interface_ in the wildfly-config_5_0.xsd is defined as: {code} <xs:complexType name="host-http-management-interfaceType"> <xs:annotation> <xs:documentation> Configuration of a host's exposed HTTP management interface. </xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="http-management-interfaceType"> <xs:sequence> <xs:element name="socket" type="host-http-management-socketType"/> </xs:sequence> <xs:attribute name="console-enabled" type="xs:boolean" use="optional" default="true"/> </xs:extension> </xs:complexContent> </xs:complexType> {code} Where _xs:sequence_ has a default definition of: * *maxOccurs* _Optional._ Specifies the maximum number of times the sequence element can occur in the parent element. The value can be any number >= 0, or if you want to set no limit on the maximum number, use the value "unbounded". Default value is 1 * *minOccurs* _Optional._ Specifies the minimum number of times the sequence element can occur in the parent element. The value can be any number >= 0. Default value is 1 But the parser allows to configure multiple sockets like this: {code} ... <security-realm name="ManagementRealm"> <server-identities> <ssl> <keystore path="server.keystore" relative-to="jboss.domain.config.dir" keystore-password="******" alias="server"/> </ssl> </server-identities> <authentication> <properties path="mgmt-users.properties" relative-to="jboss.domain.config.dir"/> </authentication> </security-realm> ... <http-interface security-realm="ManagementRealm"> <http-upgrade enabled="true"/> <socket interface="local" port="${jboss.management.local.http.port:9990}"/> <socket interface="management" secure-port="${jboss.management.https.port:9443}"/> </http-interface> ... <interfaces> <interface name="local"> <inet-address value="${jboss.bind.address.local.management:127.0.0.1}"/> </interface> <interface name="management"> <inet-address value="${jboss.bind.address.management:jbaesner.remote.csb}"/> </interface> </interfaces> ... {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-556) Jenkins messaging configuration is broken

by Filip Brychta (Jira)

Filip Brychta created SWSQE-556: ----------------------------------- Summary: Jenkins messaging configuration is broken Key: SWSQE-556 URL: https://issues.jboss.org/browse/SWSQE-556 Project: Kiali QE Issue Type: Bug Reporter: Filip Brychta Assignee: Matt Mahoney Following error is thrown periodically to jenkins log: Jan 10, 2019 5:12:04 AM com.redhat.jenkins.plugins.ci.messaging.ActiveMqMessagingWorker connect SEVERE: Unable to connect to ssl://messaging-devops-broker02.web.qa.ext.phx1.redhat.com:61616 Could not connect to broker URL: ssl://messaging-devops-broker02.web.qa.ext.phx1.redhat.com:61616. Reason: java.net.ConnectException: Connection refused (Connection refused) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3504) [DMN Designer] Move DragBoundsJSO to lienzo-tests

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3504?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3504: -------------------------------- Affects Version/s: 7.17.0.Final > [DMN Designer] Move DragBoundsJSO to lienzo-tests > ------------------------------------------------- > > Key: DROOLS-3504 > URL: https://issues.jboss.org/browse/DROOLS-3504 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.17.0.Final > Reporter: Michael Anstis > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > > JIRA DROOLS-3406 introduced {{DragBoundsJSO}} overrides the default settings of {{lienzo-tests}} in order for Unit Tests involving drag constraints to be written. [~roger600] requested that the change be added to {{lienzo-tests}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11082) ClassCastExceptions and unexpected ServletContainerInitializer executions

by Alexander Kudrevatykh (Jira)

[ https://issues.jboss.org/browse/WFLY-11082?page=com.atlassian.jira.plugin... ] Alexander Kudrevatykh commented on WFLY-11082: ---------------------------------------------- Managed container should be started by arquillian, my test does not start it or provide any configuration for that container. Can you run any arquillian test? > ClassCastExceptions and unexpected ServletContainerInitializer executions > ------------------------------------------------------------------------- > > Key: WFLY-11082 > URL: https://issues.jboss.org/browse/WFLY-11082 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 14.0.1.Final > Reporter: Alexander Kudrevatykh > Assignee: Bartosz Baranowski > Priority: Major > Attachments: dependencies.zip > > > I got unexpected ClassCastExceptions in setup as in attached test > ServiceLoader provide only one instance of SCI, but wildlfy executes it twice > More weird - wrong Set of classes passed to onStartup method - classes are not extends @HandlesTypes annotation (because they loaded with different classloaders) > sorry for complex description, look for attached test -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3504) [DMN Designer] Move DragBoundsJSO to lienzo-tests

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3504?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3504: -------------------------------- Sprint: 2019 Week 02-04 > [DMN Designer] Move DragBoundsJSO to lienzo-tests > ------------------------------------------------- > > Key: DROOLS-3504 > URL: https://issues.jboss.org/browse/DROOLS-3504 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > > JIRA DROOLS-3406 introduced {{DragBoundsJSO}} overrides the default settings of {{lienzo-tests}} in order for Unit Tests involving drag constraints to be written. [~roger600] requested that the change be added to {{lienzo-tests}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3504) [DMN Designer] Move DragBoundsJSO to lienzo-tests

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3504?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3504: ----------------------------------- Description: JIRA DROOLS-3406 introduced {{DragBoundsJSO}} overrides the default settings of {{lienzo-tests}} in order for Unit Tests involving drag constraints to be written. [~roger600] requested that the change be added to {{lienzo-tests}}. (was: JIRA DROOLS-3406 introduced {{DragBoundsJSO}} overrides the default settings of {{lienzo-tests}} in order for Unit Tests involving drag constraints to be written. [~roger600] requested that the change be added to {{lienzo-tests}}. This will require forking {{lienzo-tests}} to {{kie-group}} and adding it to our release cycle (along with possible version number changes to follow {{kie-group}}).) > [DMN Designer] Move DragBoundsJSO to lienzo-tests > ------------------------------------------------- > > Key: DROOLS-3504 > URL: https://issues.jboss.org/browse/DROOLS-3504 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > > JIRA DROOLS-3406 introduced {{DragBoundsJSO}} overrides the default settings of {{lienzo-tests}} in order for Unit Tests involving drag constraints to be written. [~roger600] requested that the change be added to {{lienzo-tests}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3504) [DMN Designer] Move DragBoundsJSO to lienzo-tests

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3504?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3504: ----------------------------------- Story Points: 3 (was: 5) > [DMN Designer] Move DragBoundsJSO to lienzo-tests > ------------------------------------------------- > > Key: DROOLS-3504 > URL: https://issues.jboss.org/browse/DROOLS-3504 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > > JIRA DROOLS-3406 introduced {{DragBoundsJSO}} overrides the default settings of {{lienzo-tests}} in order for Unit Tests involving drag constraints to be written. [~roger600] requested that the change be added to {{lienzo-tests}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3504) [DMN Designer] Move DragBoundsJSO to lienzo-tests

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3504?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3504: ----------------------------------- Labels: drools-tools (was: ) > [DMN Designer] Move DragBoundsJSO to lienzo-tests > ------------------------------------------------- > > Key: DROOLS-3504 > URL: https://issues.jboss.org/browse/DROOLS-3504 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > > JIRA DROOLS-3406 introduced {{DragBoundsJSO}} overrides the default settings of {{lienzo-tests}} in order for Unit Tests involving drag constraints to be written. [~roger600] requested that the change be added to {{lienzo-tests}}. This will require forking {{lienzo-tests}} to {{kie-group}} and adding it to our release cycle (along with possible version number changes to follow {{kie-group}}). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3504) [DMN Designer] Move DragBoundsJSO to lienzo-tests

by Michael Anstis (Jira)

Michael Anstis created DROOLS-3504: -------------------------------------- Summary: [DMN Designer] Move DragBoundsJSO to lienzo-tests Key: DROOLS-3504 URL: https://issues.jboss.org/browse/DROOLS-3504 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Michael Anstis Assignee: Jozef Marko JIRA DROOLS-3406 introduced {{DragBoundsJSO}} overrides the default settings of {{lienzo-tests}} in order for Unit Tests involving drag constraints to be written. [~roger600] requested that the change be added to {{lienzo-tests}}. This will require forking {{lienzo-tests}} to {{kie-group}} and adding it to our release cycle (along with possible version number changes to follow {{kie-group}}). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 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 January 2019