August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4562) Update the pre-recorded messages in CertificateAuthoritiesTestCase and KeyStoresTestCase using the latest Boulder instance

by Marek Kopecky (Jira)

[ https://issues.jboss.org/browse/WFCORE-4562?page=com.atlassian.jira.plugi... ] Marek Kopecky commented on WFCORE-4562: --------------------------------------- [~fjuma]: What is the status of this task? Can be PR merged now? > Update the pre-recorded messages in CertificateAuthoritiesTestCase and KeyStoresTestCase using the latest Boulder instance > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4562 > URL: https://issues.jboss.org/browse/WFCORE-4562 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Farah Juma > Assignee: Ashley Abdel-Sayed > Priority: Major > > The tests in {{CertificateAuthoritiesTestCase}} and {{KeyStoresTestCase}} simulate a mock Let's Encrypt server by using messages that were actually sent from Boulder (Let's Encrypt's testing server) to our ACME client. Wireshark was used to record the messages. The use of these recorded messages prevents us from having to integrate the complex Boulder setup into the Core testsuite. > Since these messages were pre-recorded just before the ACME protocol became an RFC, it would be good to update the pre-recorded messages used in these tests using the latest Boulder instance. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4562) Update the pre-recorded messages in CertificateAuthoritiesTestCase and KeyStoresTestCase using the latest Boulder instance

by Marek Kopecky (Jira)

[ https://issues.jboss.org/browse/WFCORE-4562?page=com.atlassian.jira.plugi... ] Marek Kopecky edited comment on WFCORE-4562 at 8/21/19 2:57 AM: ---------------------------------------------------------------- [~fjuma]: What is the status of this task? Can PR be merged now? was (Author: mkopecky): [~fjuma]: What is the status of this task? Can be PR merged now? > Update the pre-recorded messages in CertificateAuthoritiesTestCase and KeyStoresTestCase using the latest Boulder instance > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4562 > URL: https://issues.jboss.org/browse/WFCORE-4562 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Farah Juma > Assignee: Ashley Abdel-Sayed > Priority: Major > > The tests in {{CertificateAuthoritiesTestCase}} and {{KeyStoresTestCase}} simulate a mock Let's Encrypt server by using messages that were actually sent from Boulder (Let's Encrypt's testing server) to our ACME client. Wireshark was used to record the messages. The use of these recorded messages prevents us from having to integrate the complex Boulder setup into the Core testsuite. > Since these messages were pre-recorded just before the ACME protocol became an RFC, it would be good to update the pre-recorded messages used in these tests using the latest Boulder instance. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-167) IllegalStateException: No standard field found for reverse order comparator!

by Andres Luuk (Jira)

[ https://issues.jboss.org/browse/REMJMX-167?page=com.atlassian.jira.plugin... ] Andres Luuk commented on REMJMX-167: ------------------------------------ I updated the error description, but because I got it a few months ago, I don't remember more details. I think I got the error on early startup and I think my fix was either not to upgrade to jdk 11 or fix the jboss-marshalling version. > IllegalStateException: No standard field found for reverse order comparator! > ---------------------------------------------------------------------------- > > Key: REMJMX-167 > URL: https://issues.jboss.org/browse/REMJMX-167 > Project: Remoting JMX > Issue Type: Bug > Affects Versions: 3.0.3.Final > Reporter: Andres Luuk > Priority: Major > > https://github.com/jbossas/remoting-jmx/issues/41 > You are also affected with: > https://developer.jboss.org/thread/279791 > https://209.132.182.82/browse/WFLY-11720?focusedCommentId=13697026&page=c... > jboss-marshalling should probably be updated. > I got the same error as on those cases when I upgraded to java 11. > java.lang.ExceptionInInitializerError > at org.jboss.marshalling.river.RiverMarshaller.<clinit>(RiverMarshaller.java:1335) > at org.jboss.marshalling.river.RiverMarshallerFactory.createMarshaller(RiverMarshallerFactory.java:54) > ... > Caused by: java.lang.IllegalStateException: No standard field found for reverse order comparator! > at org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:287) > ... 9 more > But because I got it a few months ago (I posted it to your github, but got no responce from there) I can't provide any details on how to reproduce it. > After a few days of debugging I tracked the cause down to the pre-JDK11 jboss-marshalling version you are depending on. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-167) IllegalStateException: No standard field found for reverse order comparator!

by Andres Luuk (Jira)

[ https://issues.jboss.org/browse/REMJMX-167?page=com.atlassian.jira.plugin... ] Andres Luuk updated REMJMX-167: ------------------------------- Description: https://github.com/jbossas/remoting-jmx/issues/41 You are also affected with: https://developer.jboss.org/thread/279791 https://209.132.182.82/browse/WFLY-11720?focusedCommentId=13697026&page=c... jboss-marshalling should probably be updated. I got the same error as on those cases when I upgraded to java 11. java.lang.ExceptionInInitializerError at org.jboss.marshalling.river.RiverMarshaller.<clinit>(RiverMarshaller.java:1335) at org.jboss.marshalling.river.RiverMarshallerFactory.createMarshaller(RiverMarshallerFactory.java:54) ... Caused by: java.lang.IllegalStateException: No standard field found for reverse order comparator! at org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:287) ... 9 more But because I got it a few months ago (I posted it to your github, but got no responce from there) I can't provide any details on how to reproduce it. After a few days of debugging I tracked the cause down to the pre-JDK11 jboss-marshalling version you are depending on. was: https://github.com/jbossas/remoting-jmx/issues/41 You are also affected with: https://developer.jboss.org/thread/279791 https://209.132.182.82/browse/WFLY-11720?focusedCommentId=13697026&page=c... jboss-marshalling should probably be updated. > IllegalStateException: No standard field found for reverse order comparator! > ---------------------------------------------------------------------------- > > Key: REMJMX-167 > URL: https://issues.jboss.org/browse/REMJMX-167 > Project: Remoting JMX > Issue Type: Bug > Affects Versions: 3.0.3.Final > Reporter: Andres Luuk > Priority: Major > > https://github.com/jbossas/remoting-jmx/issues/41 > You are also affected with: > https://developer.jboss.org/thread/279791 > https://209.132.182.82/browse/WFLY-11720?focusedCommentId=13697026&page=c... > jboss-marshalling should probably be updated. > I got the same error as on those cases when I upgraded to java 11. > java.lang.ExceptionInInitializerError > at org.jboss.marshalling.river.RiverMarshaller.<clinit>(RiverMarshaller.java:1335) > at org.jboss.marshalling.river.RiverMarshallerFactory.createMarshaller(RiverMarshallerFactory.java:54) > ... > Caused by: java.lang.IllegalStateException: No standard field found for reverse order comparator! > at org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:287) > ... 9 more > But because I got it a few months ago (I posted it to your github, but got no responce from there) I can't provide any details on how to reproduce it. > After a few days of debugging I tracked the cause down to the pre-JDK11 jboss-marshalling version you are depending on. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12402) Clean out unneeded test deployment dependencies on org.jboss.as.cli module once WFCORE-4614 is done

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12402: --------------------------------------- Summary: Clean out unneeded test deployment dependencies on org.jboss.as.cli module once WFCORE-4614 is done Key: WFLY-12402 URL: https://issues.jboss.org/browse/WFLY-12402 Project: WildFly Issue Type: Task Components: Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry Once WFCORE-4614 is done look for test deployments that are adding org.jboss.as.cli as a dependency and see if that can be removed. If that makes the test usable when run against a Galleon-slimmed installation (see WFLY-12394) then start testing it that way. To find such tests: git grep org.jboss.as.cli | grep Dependencies -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4614) Remove org.jboss.as.cli import from AbstractManagementTestBase

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4614?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-4614: ------------------------------------- Description: AbstractMgmtTestBase imports org.jboss.as.cli.operation.OperationFormatException because executeAndRollbackOperation declares it throws it. But the method doesn't actually throw that exception. As a result there are a bunch of in-vm arquillian tests in WildFly that base on AbstractMgmtTestBase that are adding to their deployments the org.jboss.as.cli module as a MANIFEST>MF dependency. Remove this import and they won't need to do that. Don't do that and some of those test can then be executed against a Galleon-slimmed installation, i.e one without the CLI installed. was: AbstractMgmtTestBase imports org.jboss.as.cli.operation.OperationFormatException because executeAndRollbackOperation declares it throws it. But the method doesn't actually throw that exception. As a result there are a bunch of in-vm arquillian tests in WildFly that base on AbstractMgmtTestBase that are adding to their deployments the org.jboss.as.cli module as a Class-Path dependency. Remove this import and they won't need to do that. Don't do that and some of those test can then be executed against a Galleon-slimmed installation, i.e one without the CLI installed. > Remove org.jboss.as.cli import from AbstractManagementTestBase > -------------------------------------------------------------- > > Key: WFCORE-4614 > URL: https://issues.jboss.org/browse/WFCORE-4614 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 10.0.0.Beta4 > > > AbstractMgmtTestBase imports org.jboss.as.cli.operation.OperationFormatException because executeAndRollbackOperation declares it throws it. But the method doesn't actually throw that exception. > As a result there are a bunch of in-vm arquillian tests in WildFly that base on AbstractMgmtTestBase that are adding to their deployments the org.jboss.as.cli module as a MANIFEST>MF dependency. Remove this import and they won't need to do that. Don't do that and some of those test can then be executed against a Galleon-slimmed installation, i.e one without the CLI installed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4614) Remove org.jboss.as.cli import from AbstractManagementTestBase

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4614?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-4614: ------------------------------------- Issue Type: Bug (was: Enhancement) > Remove org.jboss.as.cli import from AbstractManagementTestBase > -------------------------------------------------------------- > > Key: WFCORE-4614 > URL: https://issues.jboss.org/browse/WFCORE-4614 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 10.0.0.Beta4 > > > AbstractMgmtTestBase imports org.jboss.as.cli.operation.OperationFormatException because executeAndRollbackOperation declares it throws it. But the method doesn't actually throw that exception. > As a result there are a bunch of in-vm arquillian tests in WildFly that base on AbstractMgmtTestBase that are adding to their deployments the org.jboss.as.cli module as a Class-Path dependency. Remove this import and they won't need to do that. Don't do that and some of those test can then be executed against a Galleon-slimmed installation, i.e one without the CLI installed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4614) Remove org.jboss.as.cli import from AbstractManagementTestBase

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4614?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-4614: ------------------------------------- Priority: Minor (was: Major) > Remove org.jboss.as.cli import from AbstractManagementTestBase > -------------------------------------------------------------- > > Key: WFCORE-4614 > URL: https://issues.jboss.org/browse/WFCORE-4614 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 10.0.0.Beta4 > > > AbstractMgmtTestBase imports org.jboss.as.cli.operation.OperationFormatException because executeAndRollbackOperation declares it throws it. But the method doesn't actually throw that exception. > As a result there are a bunch of in-vm arquillian tests in WildFly that base on AbstractMgmtTestBase that are adding to their deployments the org.jboss.as.cli module as a Class-Path dependency. Remove this import and they won't need to do that. Don't do that and some of those test can then be executed against a Galleon-slimmed installation, i.e one without the CLI installed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4614) Remove org.jboss.as.cli import from AbstractManagementTestBase

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4614: ---------------------------------------- Summary: Remove org.jboss.as.cli import from AbstractManagementTestBase Key: WFCORE-4614 URL: https://issues.jboss.org/browse/WFCORE-4614 Project: WildFly Core Issue Type: Enhancement Components: Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 10.0.0.Beta4 AbstractMgmtTestBase imports org.jboss.as.cli.operation.OperationFormatException because executeAndRollbackOperation declares it throws it. But the method doesn't actually throw that exception. As a result there are a bunch of in-vm arquillian tests in WildFly that base on AbstractMgmtTestBase that are adding to their deployments the org.jboss.as.cli module as a Class-Path dependency. Remove this import and they won't need to do that. Don't do that and some of those test can then be executed against a Galleon-slimmed installation, i.e one without the CLI installed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12401) Timely topology changes can defer expiration of distributed SFSB

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-12401: ----------------------------------- Summary: Timely topology changes can defer expiration of distributed SFSB Key: WFLY-12401 URL: https://issues.jboss.org/browse/WFLY-12401 Project: WildFly Issue Type: Bug Components: Clustering, EJB Affects Versions: 17.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Currently, the expiration of a given SFSB is scheduled for the current time + the @StatefulTimeout duration. However, a topology change cause a change in ownership, expiration for newly owned SFSBs are scheduled on the local member. Because these are not scheduled using the last accessed time, it is possible that regular topology changes can defer SFSBs from expiring indefinitely. -- This message was sent by Atlassian Jira (v7.12.1#712002)

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