October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11178) WSTrustTestCase failing on IBM

by David Lloyd (Jira)

[ https://issues.jboss.org/browse/WFLY-11178?page=com.atlassian.jira.plugin... ] David Lloyd commented on WFLY-11178: ------------------------------------ I believe there is no fix in JBoss Modules that will solve this. The property simply must not be set; setting the property results in undefined and unsupported behavior. > WSTrustTestCase failing on IBM > ------------------------------ > > Key: WFLY-11178 > URL: https://issues.jboss.org/browse/WFLY-11178 > Project: WildFly > Issue Type: Bug > Components: MSC > Affects Versions: 14.0.0.Final > Reporter: Jan Blizňák > Assignee: Alessio Soldano > Priority: Major > Attachments: log.txt > > > As discovered during investigation in WFLY-10336, we are now getting test failures in WSTrustTestCase when IBM JDK is used. The relevant part of the exception is: > {code:java} > Caused by: java.lang.IllegalArgumentException: Provider org.apache.xerces.jaxp.validation.XMLSchemaFactory not found > at javax.xml.validation.SchemaFactory.newInstance(Unknown Source) > at org.opensaml.core.xml.config.XMLConfigurator.<init>(XMLConfigurator.java:94) > at org.apache.wss4j.common.saml.OpenSAMLBootstrap.bootstrap(OpenSAMLBootstrap.java:85) > at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:91) > at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:75) > at org.apache.wss4j.common.saml.SamlAssertionWrapper.<init>(SamlAssertionWrapper.java:184) > at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createSamlToken(SAMLTokenProvider.java:308) > at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createToken(SAMLTokenProvider.java:120) > ... 102 more > {code} > It turned out the issue is in wildfly for some time, the breaking change was identified as https://github.com/wildfly/wildfly-core/pull/3201/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11178) WSTrustTestCase failing on IBM

by Martin Švehla (Jira)

[ https://issues.jboss.org/browse/WFLY-11178?page=com.atlassian.jira.plugin... ] Martin Švehla updated WFLY-11178: --------------------------------- Tester: Michal Jurc > WSTrustTestCase failing on IBM > ------------------------------ > > Key: WFLY-11178 > URL: https://issues.jboss.org/browse/WFLY-11178 > Project: WildFly > Issue Type: Bug > Components: MSC > Affects Versions: 14.0.0.Final > Reporter: Jan Blizňák > Assignee: Alessio Soldano > Priority: Major > Attachments: log.txt > > > As discovered during investigation in WFLY-10336, we are now getting test failures in WSTrustTestCase when IBM JDK is used. The relevant part of the exception is: > {code:java} > Caused by: java.lang.IllegalArgumentException: Provider org.apache.xerces.jaxp.validation.XMLSchemaFactory not found > at javax.xml.validation.SchemaFactory.newInstance(Unknown Source) > at org.opensaml.core.xml.config.XMLConfigurator.<init>(XMLConfigurator.java:94) > at org.apache.wss4j.common.saml.OpenSAMLBootstrap.bootstrap(OpenSAMLBootstrap.java:85) > at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:91) > at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:75) > at org.apache.wss4j.common.saml.SamlAssertionWrapper.<init>(SamlAssertionWrapper.java:184) > at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createSamlToken(SAMLTokenProvider.java:308) > at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createToken(SAMLTokenProvider.java:120) > ... 102 more > {code} > It turned out the issue is in wildfly for some time, the breaking change was identified as https://github.com/wildfly/wildfly-core/pull/3201/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11178) WSTrustTestCase failing on IBM

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/WFLY-11178?page=com.atlassian.jira.plugin... ] Jan Blizňák updated WFLY-11178: ------------------------------- Component/s: MSC (was: Web Services) Steps to Reproduce: {code:java} #build wildfly mvn clean install -DskipTests #run tests mvn verify -pl testsuite/integration/ws -Dts.basic -Dtest=WSTrustTestCase -DtestLogToFile=false {code} was: {code:java} #build wildfly mvn clean install -DskipTests #run tests mvn verify -pl testsuite/integration/ws -Dts.basic -Dtest=WSTrustTestCase -DtestLogToFile=false {code} As shown by reproducer, the root problem isn't in Webservices, changing component to modules. > WSTrustTestCase failing on IBM > ------------------------------ > > Key: WFLY-11178 > URL: https://issues.jboss.org/browse/WFLY-11178 > Project: WildFly > Issue Type: Bug > Components: MSC > Affects Versions: 14.0.0.Final > Reporter: Jan Blizňák > Assignee: Alessio Soldano > Priority: Major > Attachments: log.txt > > > As discovered during investigation in WFLY-10336, we are now getting test failures in WSTrustTestCase when IBM JDK is used. The relevant part of the exception is: > {code:java} > Caused by: java.lang.IllegalArgumentException: Provider org.apache.xerces.jaxp.validation.XMLSchemaFactory not found > at javax.xml.validation.SchemaFactory.newInstance(Unknown Source) > at org.opensaml.core.xml.config.XMLConfigurator.<init>(XMLConfigurator.java:94) > at org.apache.wss4j.common.saml.OpenSAMLBootstrap.bootstrap(OpenSAMLBootstrap.java:85) > at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:91) > at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:75) > at org.apache.wss4j.common.saml.SamlAssertionWrapper.<init>(SamlAssertionWrapper.java:184) > at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createSamlToken(SAMLTokenProvider.java:308) > at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createToken(SAMLTokenProvider.java:120) > ... 102 more > {code} > It turned out the issue is in wildfly for some time, the breaking change was identified as https://github.com/wildfly/wildfly-core/pull/3201/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3193) UX to support selection of multiple data/domain object instances

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-3193?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-3193: --------------------------------------- {quote}Regarding the last image you posted, in the current implementation, it is not possible to achieve it (all columns whose instance type is Dispute would get merged together, so there would be only one header row called Dispute and the header row below would be divided into six columns as in the image). You need to introduce an alias to create this structure (such as First dispute, Second dispute, Third dispute). But otherwise, it is a valid grid.{quote} This limitation is fine for now, but we should plan to remove it in the future. From a semantic perspective, it is fine to have multiple anonymous instances of the same type. > UX to support selection of multiple data/domain object instances > ---------------------------------------------------------------- > > Key: DROOLS-3193 > URL: https://issues.jboss.org/browse/DROOLS-3193 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screen Shot 2018-10-30 at 10.50.55 AM.png > > > As user I want to use multiple instances of the same data object in my test scenarios (multiple instances support) (i.e. scenario with more than one instance of “Person”...), so that I can create a test scenario. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-476) PRT Output Improve

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-476: ------------------------------------ Summary: PRT Output Improve Key: SWSQE-476 URL: https://issues.jboss.org/browse/SWSQE-476 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan Feedback from developers. When PRT fails because of some internal reason, e.g. bookinfo install fails, devs are confused. Or if e2e tests fail for some other reason. What we need to do, when PRT fails due to other reason that e2e tests broken by PR, then the bot should comment in PR that "PRT is broken, contact to QE". -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3193) UX to support selection of multiple data/domain object instances

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3193?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3193: ------------------------------------- [~kkufova] Thanks for the information. * I'm working on designs for potential future implementations. So trying to scope out things like reordering columns/rows and etc. * Regarding the spanning header, that gets to the point of one of my questions - how do we distinguish different instances for the user (by name/nickname, ID, column position, etc.) > UX to support selection of multiple data/domain object instances > ---------------------------------------------------------------- > > Key: DROOLS-3193 > URL: https://issues.jboss.org/browse/DROOLS-3193 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screen Shot 2018-10-30 at 10.50.55 AM.png > > > As user I want to use multiple instances of the same data object in my test scenarios (multiple instances support) (i.e. scenario with more than one instance of “Person”...), so that I can create a test scenario. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-475) Bookinfo installation fails on B12

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-475?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo commented on SWSQE-475: ----------------------------------------------- It is caused because of version problem on Istio 1.0.3 Roll back to 1.0.2 will solve the problem for now. I am waiting for https://github.com/kiali/kiali/pull/609 to be merged to solve this issue. > Bookinfo installation fails on B12 > ---------------------------------- > > Key: SWSQE-475 > URL: https://issues.jboss.org/browse/SWSQE-475 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Guilherme Baufaker Rêgo > Priority: Blocker > > Hi Guilherme, > Could you please take a look into this failure: > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/install-bookinfo... > Thanks, > Hayk -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3111) [DMN Designer] Decision table generation fails if custom input data connected

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3111?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3111: -------------------------------- Description: The decision table generation according to connected input data nodes fails if some custom input data is connected. h2. Manual acceptance test Check when connected input data is of type: - Built in data type (/) - Custom data type, just alias for Built in type (?) -- Defined data type as -- !Screenshot from 2018-10-31 13-13-54.png|thumbnail! -- In decision table shown the built in type -- !Screenshot from 2018-10-31 13-14-19.png|thumbnail! - Custom data type, structure (/) - Custom data type, structure containing another anonymous structure (/) - Custom data type, structure containing another top level structure (?) -- Defined data type as: -- !Screenshot from 2018-10-31 13-29-03.png|thumbnail! -- Generated columns: -- !Screenshot from 2018-10-31 13-28-43.png|thumbnail! - Custom data type, just alias for structure (/) was: The decision table generation according to connected input data nodes fails if some custom input data is connected. h2. Manual acceptance test Check when connected input data is of type: - Built in data type (/) - Custom data type, just alias for Built in type (?) -- Defined data type as -- !Screenshot from 2018-10-31 13-13-54.png|thumbnail! -- In decision table shown the built in type -- !Screenshot from 2018-10-31 13-14-19.png|thumbnail! - Custom data type, structure (/) - Custom data type, structure containing another anonymous structure (/) - Custom data type, structure containing another top level structure (?) -- Defined data type as: -- !Screenshot from 2018-10-31 13-29-03.png|thumbnail! -- Generated columns: -- !Screenshot from 2018-10-31 13-28-43.png|thumbnail! - Custom data type, just alias for structure > [DMN Designer] Decision table generation fails if custom input data connected > ----------------------------------------------------------------------------- > > Key: DROOLS-3111 > URL: https://issues.jboss.org/browse/DROOLS-3111 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2018-10-31 13-13-54.png, Screenshot from 2018-10-31 13-14-19.png, Screenshot from 2018-10-31 13-28-43.png, Screenshot from 2018-10-31 13-29-03.png, a1.dmn, aaa.dmn > > > The decision table generation according to connected input data nodes fails if some custom input data is connected. > h2. Manual acceptance test > Check when connected input data is of type: > - Built in data type (/) > - Custom data type, just alias for Built in type (?) > -- Defined data type as > -- !Screenshot from 2018-10-31 13-13-54.png|thumbnail! > -- In decision table shown the built in type > -- !Screenshot from 2018-10-31 13-14-19.png|thumbnail! > - Custom data type, structure (/) > - Custom data type, structure containing another anonymous structure (/) > - Custom data type, structure containing another top level structure (?) > -- Defined data type as: > -- !Screenshot from 2018-10-31 13-29-03.png|thumbnail! > -- Generated columns: > -- !Screenshot from 2018-10-31 13-28-43.png|thumbnail! > - Custom data type, just alias for structure (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-475) Bookinfo installation fails on B12

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-475?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-475. ------------------------------------------- Resolution: Duplicate Issue > Bookinfo installation fails on B12 > ---------------------------------- > > Key: SWSQE-475 > URL: https://issues.jboss.org/browse/SWSQE-475 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Guilherme Baufaker Rêgo > Priority: Blocker > > Hi Guilherme, > Could you please take a look into this failure: > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/install-bookinfo... > Thanks, > Hayk -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-475) Bookinfo installation fails on B12

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-475?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo commented on SWSQE-475: ----------------------------------------------- This is duplicated from SWSQE-474 and KIALI-1846 > Bookinfo installation fails on B12 > ---------------------------------- > > Key: SWSQE-475 > URL: https://issues.jboss.org/browse/SWSQE-475 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Guilherme Baufaker Rêgo > Priority: Blocker > > Hi Guilherme, > Could you please take a look into this failure: > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/install-bookinfo... > Thanks, > Hayk -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2018