June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4878) Upgrade WildFly OpenSSL to 1.0.10.Final

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4878?page=com.atlassian.jira.plug... ] Brian Stansberry resolved WFCORE-4878. -------------------------------------- Resolution: Done > Upgrade WildFly OpenSSL to 1.0.10.Final > --------------------------------------- > > Key: WFCORE-4878 > URL: https://issues.redhat.com/browse/WFCORE-4878 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 12.0.0.Beta1, 11.1.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4878) Upgrade WildFly OpenSSL to 1.0.10.Final

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4878?page=com.atlassian.jira.plug... ] Brian Stansberry reopened WFCORE-4878: -------------------------------------- > Upgrade WildFly OpenSSL to 1.0.10.Final > --------------------------------------- > > Key: WFCORE-4878 > URL: https://issues.redhat.com/browse/WFCORE-4878 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 11.1.0.Final, 12.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10173) EjbInvocationStatisticsTestCase fails on Windows: wait-time=0

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-10173?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-10173: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > EjbInvocationStatisticsTestCase fails on Windows: wait-time=0 > ------------------------------------------------------------- > > Key: WFLY-10173 > URL: https://issues.redhat.com/browse/WFLY-10173 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 12.0.0.Final > Reporter: Jan Kalina > Assignee: Cheng Fang > Priority: Major > Fix For: 21.0.0.Beta1 > > > Sometime, when running EjbInvocationStatisticsTestCase on Windows, assertion fails, as wait-time is 0 (verified it is 0 by adding debug message). > For me it fails allTests in most of cases, but when running test standalone, it fails only in 1 of 4 cases. > I suppose it is because of too short sleep in AbstractManagedBean. (in test is called 4 times, each invocation include 50ms sleep, so I consider probable the wait-time is 0 - need to use longer sleeps to fulfill the test) > {code} > [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.078 s <<< FAILURE! - in org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase > [ERROR] testSingletonWaitTime(org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase) Time elapsed: 0.438 s <<< FAILURE! > java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase.validateWaitTimeStatistic(EjbInvocationStatisticsTestCase.java:179) > at org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase.testSingletonWaitTime(EjbInvocationStatisticsTestCase.java:148) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:564) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.jboss.arquillian.junit.Arquillian$8$1.invoke(Arquillian.java:379) > ... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13499) WildFly 20 Release Graphic

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13499?page=com.atlassian.jira.plugi... ] Brian Stansberry resolved WFLY-13499. ------------------------------------- Resolution: Done Task is done; we have the graphic: https://github.com/wildfly/wildfly.org/pull/175 > WildFly 20 Release Graphic > -------------------------- > > Key: WFLY-13499 > URL: https://issues.redhat.com/browse/WFLY-13499 > Project: WildFly > Issue Type: Task > Components: Documentation > Reporter: Brian Stansberry > Assignee: James Perkins > Priority: Blocker > Fix For: 20.0.0.Final > > > Get a graphic for wildfly.org for the WF 20 release. > This won't be needed if we will have cut over to the new site by the release date, but I think there's a good chance that will not be done. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13568) SSLEJBRemoteClientTestCase shouldn't deal with dirs out of the codebase or java.io.tmpdir

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-13568?page=com.atlassian.jira.plugi... ] Cheng Fang commented on WFLY-13568: ----------------------------------- this test alway passes for me locally. {code} testsuite/integration/manualmode > mvn clean test -Dtest=org.jboss.as.test.manualmode.ejb.ssl.SSLEJBRemoteClientTestCase {code} [The test|https://github.com/wildfly/wildfly/blob/master/testsuite/integration...] uses the code source of the test class (usually resolves to {{target/test-classes/}}) as the parent dir for the temp keystore files. In my testing, the keystore files ({{target/test-classes/ejb3/ssl/jbossServer.keystore}}) are always under the local test target directory. The fact that it complained about /Library/Java/Extensions/engines/, seems to suggest you have some libs under there which might have affected classloading. This directory in my machine is empty. > SSLEJBRemoteClientTestCase shouldn't deal with dirs out of the codebase or java.io.tmpdir > ----------------------------------------------------------------------------------------- > > Key: WFLY-13568 > URL: https://issues.redhat.com/browse/WFLY-13568 > Project: WildFly > Issue Type: Task > Components: EJB, Security > Reporter: Brian Stansberry > Assignee: Cheng Fang > Priority: Major > > When I run org.jboss.as.test.manualmode.ejb.ssl.SSLEJBRemoteClientTestCase locally it fails. Looking in the logs I see: > {code} > [31m10:02:07,579 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service org.wildfly.core.management.security.realm.SSLRealm.key-manager: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.SSLRealm.key-manager: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.IllegalStateException: org.jboss.msc.service.StartException in anonymous service: WFLYDM0086: The KeyStore can not be found at /Library/Java/Extensions/engines/ejb3/ssl/jbossServer.keystore > at org.jboss.as.domain.management.security.FileKeyManagerService.loadKeyStore(FileKeyManagerService.java:179) > at org.jboss.as.domain.management.security.AbstractKeyManagerService.createKeyManagers(AbstractKeyManagerService.java:128) > at org.jboss.as.domain.management.security.AbstractKeyManagerService.start(AbstractKeyManagerService.java:93) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701) > ... 6 more > Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYDM0086: The KeyStore can not be found at /Library/Java/Extensions/engines/ejb3/ssl/jbossServer.keystore > at org.jboss.as.domain.management.security.FileKeystore.load(FileKeystore.java:114) > at org.jboss.as.domain.management.security.FileKeyManagerService.loadKeyStore(FileKeyManagerService.java:175) > ... 10 more > {code} > I haven't analyzed what's going on but I don't think a test should be expected to find content created by the test in /Library/Java/Extensions/engines/. > I don't know how long this has been an issue but I suspect it's not at all recent. I generally use ci.wildfly.org for running testsuite/integration/manualmode or I'm doing something focused and don't pay deep attention to issues not related to that focus. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13568) SSLEJBRemoteClientTestCase shouldn't deal with dirs out of the codebase or java.io.tmpdir

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-13568: --------------------------------------- Summary: SSLEJBRemoteClientTestCase shouldn't deal with dirs out of the codebase or java.io.tmpdir Key: WFLY-13568 URL: https://issues.redhat.com/browse/WFLY-13568 Project: WildFly Issue Type: Task Components: EJB, Security Reporter: Brian Stansberry Assignee: Cheng Fang When I run org.jboss.as.test.manualmode.ejb.ssl.SSLEJBRemoteClientTestCase locally it fails. Looking in the logs I see: {code} [31m10:02:07,579 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service org.wildfly.core.management.security.realm.SSLRealm.key-manager: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.SSLRealm.key-manager: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.IllegalStateException: org.jboss.msc.service.StartException in anonymous service: WFLYDM0086: The KeyStore can not be found at /Library/Java/Extensions/engines/ejb3/ssl/jbossServer.keystore at org.jboss.as.domain.management.security.FileKeyManagerService.loadKeyStore(FileKeyManagerService.java:179) at org.jboss.as.domain.management.security.AbstractKeyManagerService.createKeyManagers(AbstractKeyManagerService.java:128) at org.jboss.as.domain.management.security.AbstractKeyManagerService.start(AbstractKeyManagerService.java:93) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701) ... 6 more Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYDM0086: The KeyStore can not be found at /Library/Java/Extensions/engines/ejb3/ssl/jbossServer.keystore at org.jboss.as.domain.management.security.FileKeystore.load(FileKeystore.java:114) at org.jboss.as.domain.management.security.FileKeyManagerService.loadKeyStore(FileKeyManagerService.java:175) ... 10 more {code} I haven't analyzed what's going on but I don't think a test should be expected to find content created by the test in /Library/Java/Extensions/engines/. I don't know how long this has been an issue but I suspect it's not at all recent. I generally use ci.wildfly.org for running testsuite/integration/manualmode or I'm doing something focused and don't pay deep attention to issues not related to that focus. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4993) Organize feature pack code to facilitate separate EE 8 and EE 9 variants

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4993?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-4993: ------------------------------------- Description: Separate feature pack code for EE 8 API modules and other modules we may not want in a EE 9 feature pack from the others. See if the maven dependency set from those two sections can be used by both the legacy feature pack and the galleon feature pack, thus eliminating the duplication of dependency declaration we currently have. License.xml generation will likely require https://github.com/wildfly/maven-plugins/issues/10 as the split would mean the input would be split as well. > Organize feature pack code to facilitate separate EE 8 and EE 9 variants > ------------------------------------------------------------------------ > > Key: WFCORE-4993 > URL: https://issues.redhat.com/browse/WFCORE-4993 > Project: WildFly Core > Issue Type: Task > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 13.0.0.Beta1 > > > Separate feature pack code for EE 8 API modules and other modules we may not want in a EE 9 feature pack from the others. > See if the maven dependency set from those two sections can be used by both the legacy feature pack and the galleon feature pack, thus eliminating the duplication of dependency declaration we currently have. > License.xml generation will likely require https://github.com/wildfly/maven-plugins/issues/10 as the split would mean the input would be split as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4993) Organize feature pack code to facilitate separate EE 8 and EE 9 variants

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4993: ---------------------------------------- Summary: Organize feature pack code to facilitate separate EE 8 and EE 9 variants Key: WFCORE-4993 URL: https://issues.redhat.com/browse/WFCORE-4993 Project: WildFly Core Issue Type: Task Components: Build System Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 13.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13567) Disable MPScriptTestCase in the 'alt-dist' test jobs

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-13567: --------------------------------------- Summary: Disable MPScriptTestCase in the 'alt-dist' test jobs Key: WFLY-13567 URL: https://issues.redhat.com/browse/WFLY-13567 Project: WildFly Issue Type: Task Components: Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 21.0.0.Beta1 The 'alt-dist' jobs like https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxAltDistJdk8 configure the TS to use the output of the ee-build/ee-dist modules or to provision using the wildfly-ee FP. MPScriptTestCase can't pass in such a scenario as the enable-microprofile.cli script it wants to run does not exist. So use a JUnit Assume to disable it. Checking for -Dtestsuite.default.build.project.prefix=ee- would probably do the trick. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13567) Disable MPScriptTestCase in the 'alt-dist' test jobs

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13567?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFLY-13567: --------------------------------------- Assignee: (was: Brian Stansberry) > Disable MPScriptTestCase in the 'alt-dist' test jobs > ---------------------------------------------------- > > Key: WFLY-13567 > URL: https://issues.redhat.com/browse/WFLY-13567 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Brian Stansberry > Priority: Minor > Fix For: 21.0.0.Beta1 > > > The 'alt-dist' jobs like https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxAltDistJdk8 configure the TS to use the output of the ee-build/ee-dist modules or to provision using the wildfly-ee FP. MPScriptTestCase can't pass in such a scenario as the enable-microprofile.cli script it wants to run does not exist. So use a JUnit Assume to disable it. Checking for -Dtestsuite.default.build.project.prefix=ee- would probably do the trick. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 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 June 2020