July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11504) Some hibernate tests fail with security on IBM Java 8: HHH000142

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-11504?page=com.atlassian.jira.plugin... ] Scott Marlow closed WFLY-11504. ------------------------------- Fix Version/s: 17.0.0.Final Resolution: Done fixed when WildFly 17.0.0.Final included Hibernate ORM 5.3.10.Final, which included the Hibernate fixes for this issue. Thanks [~gbadner] + [~guillaume.smet] + [~okotek]! > Some hibernate tests fail with security on IBM Java 8: HHH000142 > ---------------------------------------------------------------- > > Key: WFLY-11504 > URL: https://issues.jboss.org/browse/WFLY-11504 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate, Test Suite > Affects Versions: 16.0.0.Beta1 > Environment: IBM Java 8, build 8.0.5.25 or 8.0.5.26 > Reporter: Ondrej Kotek > Assignee: Gail Badner > Priority: Major > Fix For: 17.0.0.Final > > Attachments: org.jboss.as.test.integration.jpa.hibernate.entitytest.EntityTestCase-output.txt > > > Seven hibernate tests fail with security on IBM Java 8, for example: > {noformat} > org.hibernate.HibernateException: HHH000142: Bytecode enhancement failed: org.jboss.as.test.integration.jpa.hibernate.Employee > {noformat} > Affected test cases: > * {{org.jboss.as.test.integration.jpa.hibernate.entitytest.EntityTestCase}} > * {{org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverOnetoManyJoinColumnTest}} > * {{org.jboss.as.test.integration.jpa.hibernate.envers.basicenverstest.BasicEnversTestCase}} > * {{org.jboss.as.test.integration.jpa.hibernate.envers.basicselectiveenverstest.BasicSelectiveEnversTestCase}} > * {{org.jboss.as.test.integration.jpa.hibernate.envers.implementvalidityauditstrategytest.ImplementValidityAuditStrategyTestCase}} > * {{org.jboss.as.test.integration.jpa.hibernate.envers.validityauditstrategyoninheritancetest.ValidityAuditStrategyonInheritanceTestCase}} > * {{org.jboss.as.test.integration.jpa.hibernate.sessionfactorytest.SessionFactoryTestCase}} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4162) Scenario Test: UX for background data

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-4162?page=com.atlassian.jira.plugi... ] Klara Kufova resolved DROOLS-4162. ---------------------------------- Resolution: Done > Scenario Test: UX for background data > ------------------------------------- > > Key: DROOLS-4162 > URL: https://issues.jboss.org/browse/DROOLS-4162 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screenshot from 2019-07-08 14-12-18.png, design1.png, design2.png, design3.png > > > As user I want to be able to specify a set of data shared by all the scenarios inside a simulation. All the data will be not editable. > Please refer to Cucumber background feature for details https://cucumber.io/docs/gherkin/reference/#background -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4162) Scenario Test: UX for background data

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-4162?page=com.atlassian.jira.plugi... ] Klara Kufova commented on DROOLS-4162: -------------------------------------- We will proceed with design number 2. > Scenario Test: UX for background data > ------------------------------------- > > Key: DROOLS-4162 > URL: https://issues.jboss.org/browse/DROOLS-4162 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screenshot from 2019-07-08 14-12-18.png, design1.png, design2.png, design3.png > > > As user I want to be able to specify a set of data shared by all the scenarios inside a simulation. All the data will be not editable. > Please refer to Cucumber background feature for details https://cucumber.io/docs/gherkin/reference/#background -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-3743) Implement Test scenario coverage report for RULE

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3743?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3743: --------------------------------- Story Points: 5 (was: 8) > Implement Test scenario coverage report for RULE > ------------------------------------------------ > > Key: DROOLS-3743 > URL: https://issues.jboss.org/browse/DROOLS-3743 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > > Use this ticket as specs > https://issues.jboss.org/browse/DROOLS-3516 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-11504) Some hibernate tests fail with security on IBM Java 8: HHH000142

by Ondrej Kotek (Jira)

[ https://issues.jboss.org/browse/WFLY-11504?page=com.atlassian.jira.plugin... ] Ondrej Kotek commented on WFLY-11504: ------------------------------------- [~gbadner] I do not see the failures in QE nightly testing, this can be resolved. Thanks for the fix. > Some hibernate tests fail with security on IBM Java 8: HHH000142 > ---------------------------------------------------------------- > > Key: WFLY-11504 > URL: https://issues.jboss.org/browse/WFLY-11504 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate, Test Suite > Affects Versions: 16.0.0.Beta1 > Environment: IBM Java 8, build 8.0.5.25 or 8.0.5.26 > Reporter: Ondrej Kotek > Assignee: Gail Badner > Priority: Major > Attachments: org.jboss.as.test.integration.jpa.hibernate.entitytest.EntityTestCase-output.txt > > > Seven hibernate tests fail with security on IBM Java 8, for example: > {noformat} > org.hibernate.HibernateException: HHH000142: Bytecode enhancement failed: org.jboss.as.test.integration.jpa.hibernate.Employee > {noformat} > Affected test cases: > * {{org.jboss.as.test.integration.jpa.hibernate.entitytest.EntityTestCase}} > * {{org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverOnetoManyJoinColumnTest}} > * {{org.jboss.as.test.integration.jpa.hibernate.envers.basicenverstest.BasicEnversTestCase}} > * {{org.jboss.as.test.integration.jpa.hibernate.envers.basicselectiveenverstest.BasicSelectiveEnversTestCase}} > * {{org.jboss.as.test.integration.jpa.hibernate.envers.implementvalidityauditstrategytest.ImplementValidityAuditStrategyTestCase}} > * {{org.jboss.as.test.integration.jpa.hibernate.envers.validityauditstrategyoninheritancetest.ValidityAuditStrategyonInheritanceTestCase}} > * {{org.jboss.as.test.integration.jpa.hibernate.sessionfactorytest.SessionFactoryTestCase}} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12293) Upgrade galleon and galleon-plugins to 4.0.2

by Jean Francois Denise (Jira)

Jean Francois Denise created WFLY-12293: ------------------------------------------- Summary: Upgrade galleon and galleon-plugins to 4.0.2 Key: WFLY-12293 URL: https://issues.jboss.org/browse/WFLY-12293 Project: WildFly Issue Type: Component Upgrade Components: Build System Reporter: Jean Francois Denise Assignee: Jean Francois Denise -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4567) Upgrade galleon and galleon-plugins to 4.0.2

by Jean Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFCORE-4567?page=com.atlassian.jira.plugi... ] Jean Francois Denise commented on WFCORE-4567: ---------------------------------------------- Ability to append content to file. > Upgrade galleon and galleon-plugins to 4.0.2 > -------------------------------------------- > > Key: WFCORE-4567 > URL: https://issues.jboss.org/browse/WFCORE-4567 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Jean Francois Denise > Assignee: Jean Francois Denise > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4567) Upgrade galleon and galleon-plugins to 4.0.2

by Jean Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFCORE-4567?page=com.atlassian.jira.plugi... ] Jean Francois Denise commented on WFCORE-4567: ---------------------------------------------- Needed when generating offliner file. > Upgrade galleon and galleon-plugins to 4.0.2 > -------------------------------------------- > > Key: WFCORE-4567 > URL: https://issues.jboss.org/browse/WFCORE-4567 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Jean Francois Denise > Assignee: Jean Francois Denise > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4568) Generate a log message if an OperationStepHandler rollbacks the context (in VERIFY stage)

by Jaikiran Pai (Jira)

Jaikiran Pai created WFCORE-4568: ------------------------------------ Summary: Generate a log message if an OperationStepHandler rollbacks the context (in VERIFY stage) Key: WFCORE-4568 URL: https://issues.jboss.org/browse/WFCORE-4568 Project: WildFly Core Issue Type: Enhancement Components: Server Affects Versions: 10.0.0.Beta1, 9.0.2.Final Reporter: Jaikiran Pai Assignee: Jeff Mesnil (In context of https://issues.jboss.org/browse/WFCORE-4560) Right now, if an OperationStepHandler in the VERIFY stage marks the context for rollback (through the use of context.setRollbackOnly()), the operation gets rolled back (as expected), but there's no error message or an exception or any kind of log message generated from it. As a result, it ends up being difficult to understand why a particular operation (which might be part of a larger operation) failed. Given that rollbacks are typically caused because there is some error/problem, I think the rollback we should perhaps prominently report in the logs an ERROR message and maybe even with an exception stacktrace which shows the originating call to the context.setRollbackOnly(). In terms of the implementation, the org.jboss.as.controller.AbstractOperationContext#canContinueProcessing() method is missing a check to see if the resultAction is already ROLLBACK and hence is not even logging trace log messages, unlike for some other cases handled in that method. A concrete example of this issue was demonstrated in https://issues.jboss.org/browse/WFCORE-4560 where the org.jboss.as.controller.management.ManagementInterfaceAddStepHandler$VerifyInstallationStep was rolling back the operation explicitly but there was no indication of that in the logs and the JVM would just exit. (Slightly unrelated - I don't understand why there's a separate VerifyInstallationStep class which is added by the LenientVerifyInstallationStep, instead of LenientVerifyInstallationStep itself doing the rollback) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4567) Upgrade galleon and galleon-plugins to 4.0.2

by Jean Francois Denise (Jira)

Jean Francois Denise created WFCORE-4567: -------------------------------------------- Summary: Upgrade galleon and galleon-plugins to 4.0.2 Key: WFCORE-4567 URL: https://issues.jboss.org/browse/WFCORE-4567 Project: WildFly Core Issue Type: Component Upgrade Components: Build System Reporter: Jean Francois Denise Assignee: Jean Francois Denise -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

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 July 2019