August 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-5099) Upgrade WildFly OpenSSL Natives to 2.0.0.Alpha1

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFCORE-5099?page=com.atlassian.jira.plug... ] Farah Juma deleted WFCORE-5099: ------------------------------- > Upgrade WildFly OpenSSL Natives to 2.0.0.Alpha1 > ----------------------------------------------- > > Key: WFCORE-5099 > URL: https://issues.redhat.com/browse/WFCORE-5099 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5099) Upgrade WildFly OpenSSL Natives to 2.0.0.Alpha1

by Farah Juma (Jira)

Farah Juma created WFCORE-5099: ---------------------------------- Summary: Upgrade WildFly OpenSSL Natives to 2.0.0.Alpha1 Key: WFCORE-5099 URL: https://issues.redhat.com/browse/WFCORE-5099 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5098) Upgrade WildFly OpenSSL to 2.0.0.Alpha1

by Farah Juma (Jira)

Farah Juma created WFCORE-5098: ---------------------------------- Summary: Upgrade WildFly OpenSSL to 2.0.0.Alpha1 Key: WFCORE-5098 URL: https://issues.redhat.com/browse/WFCORE-5098 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SSLNTV-2) Add jdk.min.version property and set it to JDK 11

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/SSLNTV-2?page=com.atlassian.jira.plugin.... ] Farah Juma updated SSLNTV-2: ---------------------------- Fix Version/s: 2.1.0.Alpha1 > Add jdk.min.version property and set it to JDK 11 > ------------------------------------------------- > > Key: SSLNTV-2 > URL: https://issues.redhat.com/browse/SSLNTV-2 > Project: WildFly OpenSSL Natives > Issue Type: Tracker > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 2.1.0.Alpha1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SSLNTV-3) Add support for TLSv1.3

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/SSLNTV-3?page=com.atlassian.jira.plugin.... ] Farah Juma moved WFSSL-44 to SSLNTV-3: -------------------------------------- Project: WildFly OpenSSL Natives (was: WildFly OpenSSL) Key: SSLNTV-3 (was: WFSSL-44) Issue Type: Tracker (was: Improvement) Workflow: GIT Pull Request workflow (was: classic default workflow) Fix Version/s: 2.1.0.Alpha1 (was: 2.0.0.Alpha1) > Add support for TLSv1.3 > ----------------------- > > Key: SSLNTV-3 > URL: https://issues.redhat.com/browse/SSLNTV-3 > Project: WildFly OpenSSL Natives > Issue Type: Tracker > Reporter: Tristan Tarrant > Assignee: Farah Juma > Priority: Major > Fix For: 2.1.0.Alpha1 > > > The WildFly OpenSSL provider does not register a handler for TLSv1.3. It should :) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SSLNTV-1) Release WildFly OpenSSL Natives 2.0.0.Alpha1

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/SSLNTV-1?page=com.atlassian.jira.plugin.... ] Farah Juma updated SSLNTV-1: ---------------------------- Fix Version/s: 2.0.0.Alpha1 > Release WildFly OpenSSL Natives 2.0.0.Alpha1 > -------------------------------------------- > > Key: SSLNTV-1 > URL: https://issues.redhat.com/browse/SSLNTV-1 > Project: WildFly OpenSSL Natives > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 2.0.0.Alpha1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SSLNTV-2) Add jdk.min.version property and set it to JDK 11

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/SSLNTV-2?page=com.atlassian.jira.plugin.... ] Farah Juma updated SSLNTV-2: ---------------------------- Fix Version/s: (was: 2.0.0.Alpha1) > Add jdk.min.version property and set it to JDK 11 > ------------------------------------------------- > > Key: SSLNTV-2 > URL: https://issues.redhat.com/browse/SSLNTV-2 > Project: WildFly OpenSSL Natives > Issue Type: Tracker > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SSLNTV-2) Add jdk.min.version property and set it to JDK 11

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/SSLNTV-2?page=com.atlassian.jira.plugin.... ] Farah Juma moved WFSSL-43 to SSLNTV-2: -------------------------------------- Project: WildFly OpenSSL Natives (was: WildFly OpenSSL) Key: SSLNTV-2 (was: WFSSL-43) Issue Type: Tracker (was: Task) Fix Version/s: 2.0.0.Alpha1 (was: 2.0.0.Alpha1) > Add jdk.min.version property and set it to JDK 11 > ------------------------------------------------- > > Key: SSLNTV-2 > URL: https://issues.redhat.com/browse/SSLNTV-2 > Project: WildFly OpenSSL Natives > Issue Type: Tracker > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 2.0.0.Alpha1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4674) Custom handlers, formatters and filters cause the server to crash if the log manager is on the boot class path

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-4674?page=com.atlassian.jira.plug... ] James Perkins commented on WFCORE-4674: --------------------------------------- [~francisco.melojr] That is correct. You'd pass any agent required to JBoss Modules, {{java -jar jboss-modules.jar -javaagent:myagent.jar ...}}. With WildFly you'd just the {{MODULE_OPTS="-javaagent:myagent.jar"}} in the {{standalone.conf}}. For WildFly 18 there is no real solution without modifying the server. You'd need to upgrade the JBoss Modules version and edit the {{standalone.sh}} if that is what is used to launch the container. > Custom handlers, formatters and filters cause the server to crash if the log manager is on the boot class path > -------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4674 > URL: https://issues.redhat.com/browse/WFCORE-4674 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Critical > Labels: OpenShift, jdk11 > Fix For: 13.0.0.Beta1 > > > If the log manager is on the boot class path with Java 11, {{-Xbootclasspath/a:jboss-logmanager.jar}}, and a custom handler, formatter or filter is used the server will fail to boot as the log manager can't see the types in jboss-modules. This seems due to the fact that the log manager is on the boot class path and jboss-modules is on the system class path. > Example exception: > {code} > Failed to read or configure the org.jboss.logmanager.LogManager > java.lang.IllegalArgumentException: Failed to load module "org.jboss.logmanager" for formatter "JSON" > at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:65) > at org.jboss.logmanager.config.FormatterConfigurationImpl.<init>(FormatterConfigurationImpl.java:30) > at org.jboss.logmanager.config.LogContextConfigurationImpl.addFormatterConfiguration(LogContextConfigurationImpl.java:172) > at org.jboss.logmanager.PropertyConfigurator.configureFormatter(PropertyConfigurator.java:631) > at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:701) > at org.jboss.logmanager.PropertyConfigurator.configureLogger(PropertyConfigurator.java:583) > at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:521) > at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:97) > at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:170) > at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:132) > at java.util.logging.LogManager$3.run(LogManager.java:399) > at java.util.logging.LogManager$3.run(LogManager.java:396) > at java.security.AccessController.doPrivileged(Native Method) > at java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:396) > at java.util.logging.LogManager.access$800(LogManager.java:145) > at java.util.logging.LogManager$2.run(LogManager.java:345) > at java.security.AccessController.doPrivileged(Native Method) > at java.util.logging.LogManager.ensureLogManagerInitialized(LogManager.java:338) > at java.util.logging.LogManager.getLogManager(LogManager.java:378) > at org.jboss.modules.Main.main(Main.java:523) > Caused by: java.lang.NoClassDefFoundError: org/jboss/modules/ModuleLoader > at org.jboss.logmanager.config.AbstractPropertyConfiguration$ModuleFinder.getClassLoader(AbstractPropertyConfiguration.java:556) > at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:63) > ... 19 more > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13787) Batch subsystem docs don't integrate properly in the Admin Guide

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-13787?page=com.atlassian.jira.plugi... ] Cheng Fang commented on WFLY-13787: ----------------------------------- The section id in batch_JSR-352.adoc: [[Batch_(JSR-352)]] contains invalid characters ( ), which messed up rendering. I'll fix it. If all renders correctly, section 9.18 will be Resource Adapter, section 9.19 for batch, and section 9.20 for JSF, etc. > Batch subsystem docs don't integrate properly in the Admin Guide > ---------------------------------------------------------------- > > Key: WFLY-13787 > URL: https://issues.redhat.com/browse/WFLY-13787 > Project: WildFly > Issue Type: Bug > Components: Batch, Documentation > Affects Versions: 20.0.0.Final > Reporter: Brian Stansberry > Assignee: Cheng Fang > Priority: Major > > https://docs.wildfly.org/20/Admin_Guide.html#Resource_adapters > Sections 9.18.1-4 are about resource adapters but then the doc changes to being about batch but number sequence continues with 9.18.5 etc. So something is wrong preventing the document page getting properly integrated into the overal structure. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 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 2020