August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10856) Hibernate51CompatibilityTransformer#transform should always return null if no class change is made

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-10856?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-10856: -------------------------------- Fix Version/s: 14.0.0.Beta2 > Hibernate51CompatibilityTransformer#transform should always return null if no class change is made > -------------------------------------------------------------------------------------------------- > > Key: WFLY-10856 > URL: https://issues.jboss.org/browse/WFLY-10856 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 14.0.0.Beta2 > > > Currently, Hibernate51CompatibilityTransformer#transform is not always returning null when no changes are made to the application class, which could slow application deployment. This only happens for Hibernate ORM native applications that extend/implement certain ORM classes but do not require class transforming. > We did not measure the performance impact, so not sure how important this change is. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-65) [Artemis 2.x upgrade] Artemis RA connections disconnected after failover

by Clebert Suconic (JIRA)

[ https://issues.jboss.org/browse/WFWIP-65?page=com.atlassian.jira.plugin.s... ] Clebert Suconic commented on WFWIP-65: -------------------------------------- Marked this as resolved since it didn't fail. Note: 1.x definitely has the issue with interrupts. I could replicate it on HornetQ... disclaimer: the issue never happened with trace logs on.. and it needed 10 hour runs to replicate it. This is definitely fixed in master. at least on the interrupt part. I will let you decide what to do with these changes on 1.x. > [Artemis 2.x upgrade] Artemis RA connections disconnected after failover > ------------------------------------------------------------------------- > > Key: WFWIP-65 > URL: https://issues.jboss.org/browse/WFWIP-65 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Clebert Suconic > Priority: Blocker > Labels: feature-branch-blocker > Attachments: DedicatedFailoverTestCaseWithMdb.testShutdownWithFailback.zip > > > There is regression againt Artemis 1.5.5.0012 in scenario with failover of Artemis RA from live to backup (shared store, dedicated topology). After backup activates after failover, connections of RA does not failover to backup (or are disconnected from backup just after failover) > Test scenario: > * There are three servers. Live server (Node 1) and backupserver (Node 2) are in dedicated HA topology. > * InQueue and OutQueue are deployed on live and backup. Send messages to InQueue on live server. > * When all messages are sent, deploy message driven bean on Node 3. > * MDB sends messages form InQueue to OutQueue. > * Shutdown live server. Wait for backup server to alive, then start live server again and stop backup. > * Receive messages from OutQueue from live server. > Results: > After live server is stopped and backup activates, no messages are processed by MDB. Looking at trace logs it seems that MDB does reconnect to backup but it's then disconnected. Then I don't see connector to backup server between tried connectors during reconnection. > Attaching reproduce and logs. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-65) [Artemis 2.x upgrade] Artemis RA connections disconnected after failover

by Clebert Suconic (JIRA)

[ https://issues.jboss.org/browse/WFWIP-65?page=com.atlassian.jira.plugin.s... ] Clebert Suconic edited comment on WFWIP-65 at 8/15/18 3:42 PM: --------------------------------------------------------------- Marked this as resolved since it didn't fail. Note: 1.x definitely has the issue with interrupts. I could replicate it on HornetQ... disclaimer: the issue never happened with trace logs on.. and it needed 10 hour runs to replicate it. This is definitely fixed in master. at least on the interrupt part. I will let you ([~mnovak]) decide what to do with these changes on 1.x. was (Author: clebert.suconic): Marked this as resolved since it didn't fail. Note: 1.x definitely has the issue with interrupts. I could replicate it on HornetQ... disclaimer: the issue never happened with trace logs on.. and it needed 10 hour runs to replicate it. This is definitely fixed in master. at least on the interrupt part. I will let you decide what to do with these changes on 1.x. > [Artemis 2.x upgrade] Artemis RA connections disconnected after failover > ------------------------------------------------------------------------- > > Key: WFWIP-65 > URL: https://issues.jboss.org/browse/WFWIP-65 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Clebert Suconic > Priority: Blocker > Labels: feature-branch-blocker > Attachments: DedicatedFailoverTestCaseWithMdb.testShutdownWithFailback.zip > > > There is regression againt Artemis 1.5.5.0012 in scenario with failover of Artemis RA from live to backup (shared store, dedicated topology). After backup activates after failover, connections of RA does not failover to backup (or are disconnected from backup just after failover) > Test scenario: > * There are three servers. Live server (Node 1) and backupserver (Node 2) are in dedicated HA topology. > * InQueue and OutQueue are deployed on live and backup. Send messages to InQueue on live server. > * When all messages are sent, deploy message driven bean on Node 3. > * MDB sends messages form InQueue to OutQueue. > * Shutdown live server. Wait for backup server to alive, then start live server again and stop backup. > * Receive messages from OutQueue from live server. > Results: > After live server is stopped and backup activates, no messages are processed by MDB. Looking at trace logs it seems that MDB does reconnect to backup but it's then disconnected. Then I don't see connector to backup server between tried connectors during reconnection. > Attaching reproduce and logs. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-65) [Artemis 2.x upgrade] Artemis RA connections disconnected after failover

by Clebert Suconic (JIRA)

[ https://issues.jboss.org/browse/WFWIP-65?page=com.atlassian.jira.plugin.s... ] Clebert Suconic resolved WFWIP-65. ---------------------------------- Resolution: Done > [Artemis 2.x upgrade] Artemis RA connections disconnected after failover > ------------------------------------------------------------------------- > > Key: WFWIP-65 > URL: https://issues.jboss.org/browse/WFWIP-65 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Clebert Suconic > Priority: Blocker > Labels: feature-branch-blocker > Attachments: DedicatedFailoverTestCaseWithMdb.testShutdownWithFailback.zip > > > There is regression againt Artemis 1.5.5.0012 in scenario with failover of Artemis RA from live to backup (shared store, dedicated topology). After backup activates after failover, connections of RA does not failover to backup (or are disconnected from backup just after failover) > Test scenario: > * There are three servers. Live server (Node 1) and backupserver (Node 2) are in dedicated HA topology. > * InQueue and OutQueue are deployed on live and backup. Send messages to InQueue on live server. > * When all messages are sent, deploy message driven bean on Node 3. > * MDB sends messages form InQueue to OutQueue. > * Shutdown live server. Wait for backup server to alive, then start live server again and stop backup. > * Receive messages from OutQueue from live server. > Results: > After live server is stopped and backup activates, no messages are processed by MDB. Looking at trace logs it seems that MDB does reconnect to backup but it's then disconnected. Then I don't see connector to backup server between tried connectors during reconnection. > Attaching reproduce and logs. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10856) Hibernate51CompatibilityTransformer#transform should always return null if no class change is made

by Scott Marlow (JIRA)

Scott Marlow created WFLY-10856: ----------------------------------- Summary: Hibernate51CompatibilityTransformer#transform should always return null if no class change is made Key: WFLY-10856 URL: https://issues.jboss.org/browse/WFLY-10856 Project: WildFly Issue Type: Task Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Currently, Hibernate51CompatibilityTransformer#transform is not always returning null when no changes are made to the application class, which could slow application deployment. This only happens for Hibernate ORM native applications that extend/implement certain ORM classes but do not require class transforming. We did not measure the performance impact, so not sure how important this change is. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1643) Increment WildFly Elytron schema version for client to 1.2

by Jan Kalina (JIRA)

Jan Kalina created ELY-1643: ------------------------------- Summary: Increment WildFly Elytron schema version for client to 1.2 Key: ELY-1643 URL: https://issues.jboss.org/browse/ELY-1643 Project: WildFly Elytron Issue Type: Task Components: XML Reporter: Jan Kalina Assignee: Jan Kalina -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1642) Compilation error on JDK 11: cannot find class sun.reflect.Reflection

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1642?page=com.atlassian.jira.plugin.s... ] Jan Kalina commented on ELY-1642: --------------------------------- For needs of running tests there is workaround to build in Java9 and to run tests in Java10: {code} JAVA_HOME=/opt/jdk-9/ PATH=$JAVA_HOME/bin/:$PATH mvn clean install JAVA_HOME=/opt/jdk-10/ PATH=$JAVA_HOME/bin/:$PATH mvn test {code} > Compilation error on JDK 11: cannot find class sun.reflect.Reflection > --------------------------------------------------------------------- > > Key: ELY-1642 > URL: https://issues.jboss.org/browse/ELY-1642 > Project: WildFly Elytron > Issue Type: Bug > Components: Security Manager > Affects Versions: 1.5.1.Final > Environment: openjdk version "11-ea" 2018-09-25 > OpenJDK Runtime Environment 18.9 (build 11-ea+25) > OpenJDK 64-Bit Server VM 18.9 (build 11-ea+25, mixed mode) > Reporter: Ondrej Kotek > Priority: Critical > > {{mvn test}} results in compilation error: > {noformat} > [ERROR] /home/okotek/git/wildfly-elytron/src/main/java/org/wildfly/security/manager/WildFlySecurityManager.java:[58,19] cannot find symbol > symbol: class Reflection > location: package sun.reflect > {noformat} > Blocks testing on JDK 11, setting to Critical. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1642) Compilation error on JDK 11: cannot find class sun.reflect.Reflection

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1642?page=com.atlassian.jira.plugin.s... ] Jan Kalina updated ELY-1642: ---------------------------- Component/s: Security Manager (was: Build) > Compilation error on JDK 11: cannot find class sun.reflect.Reflection > --------------------------------------------------------------------- > > Key: ELY-1642 > URL: https://issues.jboss.org/browse/ELY-1642 > Project: WildFly Elytron > Issue Type: Bug > Components: Security Manager > Affects Versions: 1.5.1.Final > Environment: openjdk version "11-ea" 2018-09-25 > OpenJDK Runtime Environment 18.9 (build 11-ea+25) > OpenJDK 64-Bit Server VM 18.9 (build 11-ea+25, mixed mode) > Reporter: Ondrej Kotek > Priority: Critical > > {{mvn test}} results in compilation error: > {noformat} > [ERROR] /home/okotek/git/wildfly-elytron/src/main/java/org/wildfly/security/manager/WildFlySecurityManager.java:[58,19] cannot find symbol > symbol: class Reflection > location: package sun.reflect > {noformat} > Blocks testing on JDK 11, setting to Critical. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1642) Compilation error on JDK 11: cannot find class sun.reflect.Reflection

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1642?page=com.atlassian.jira.plugin.s... ] Jan Kalina commented on ELY-1642: --------------------------------- The stack checking should be re-implemented using StackWalker, new API introduced in JDK9. See ELY-161 > Compilation error on JDK 11: cannot find class sun.reflect.Reflection > --------------------------------------------------------------------- > > Key: ELY-1642 > URL: https://issues.jboss.org/browse/ELY-1642 > Project: WildFly Elytron > Issue Type: Bug > Components: Build > Affects Versions: 1.5.1.Final > Environment: openjdk version "11-ea" 2018-09-25 > OpenJDK Runtime Environment 18.9 (build 11-ea+25) > OpenJDK 64-Bit Server VM 18.9 (build 11-ea+25, mixed mode) > Reporter: Ondrej Kotek > Priority: Critical > > {{mvn test}} results in compilation error: > {noformat} > [ERROR] /home/okotek/git/wildfly-elytron/src/main/java/org/wildfly/security/manager/WildFlySecurityManager.java:[58,19] cannot find symbol > symbol: class Reflection > location: package sun.reflect > {noformat} > Blocks testing on JDK 11, setting to Critical. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-65) [Artemis 2.x upgrade] Artemis RA connections disconnected after failover

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFWIP-65?page=com.atlassian.jira.plugin.s... ] Miroslav Novak commented on WFWIP-65: ------------------------------------- Run with WF master (Artemis 1.5.5.012): https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... > [Artemis 2.x upgrade] Artemis RA connections disconnected after failover > ------------------------------------------------------------------------- > > Key: WFWIP-65 > URL: https://issues.jboss.org/browse/WFWIP-65 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Clebert Suconic > Priority: Blocker > Labels: feature-branch-blocker > Attachments: DedicatedFailoverTestCaseWithMdb.testShutdownWithFailback.zip > > > There is regression againt Artemis 1.5.5.0012 in scenario with failover of Artemis RA from live to backup (shared store, dedicated topology). After backup activates after failover, connections of RA does not failover to backup (or are disconnected from backup just after failover) > Test scenario: > * There are three servers. Live server (Node 1) and backupserver (Node 2) are in dedicated HA topology. > * InQueue and OutQueue are deployed on live and backup. Send messages to InQueue on live server. > * When all messages are sent, deploy message driven bean on Node 3. > * MDB sends messages form InQueue to OutQueue. > * Shutdown live server. Wait for backup server to alive, then start live server again and stop backup. > * Receive messages from OutQueue from live server. > Results: > After live server is stopped and backup activates, no messages are processed by MDB. Looking at trace logs it seems that MDB does reconnect to backup but it's then disconnected. Then I don't see connector to backup server between tried connectors during reconnection. > Attaching reproduce and logs. -- 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 August 2018