May 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13485) Upgrade WildFly Core 12.0.0.Beta3

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-13485?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFLY-13485: ------------------------------- Description: Tag + Release Notes: https://github.com/wildfly/wildfly-core/releases/tag/12.0.0.Beta3 Diff to previous integrated version: https://github.com/wildfly/wildfly-core/compare/12.0.0.Beta2...12.0.0.Beta3 > Upgrade WildFly Core 12.0.0.Beta3 > --------------------------------- > > Key: WFLY-13485 > URL: https://issues.redhat.com/browse/WFLY-13485 > Project: WildFly > Issue Type: Component Upgrade > Components: Management > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > Fix For: 20.0.0.Beta1 > > > Tag + Release Notes: https://github.com/wildfly/wildfly-core/releases/tag/12.0.0.Beta3 > Diff to previous integrated version: https://github.com/wildfly/wildfly-core/compare/12.0.0.Beta2...12.0.0.Beta3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13485) Upgrade WildFly Core 12.0.0.Beta3

by Jeff Mesnil (Jira)

Jeff Mesnil created WFLY-13485: ---------------------------------- Summary: Upgrade WildFly Core 12.0.0.Beta3 Key: WFLY-13485 URL: https://issues.redhat.com/browse/WFLY-13485 Project: WildFly Issue Type: Component Upgrade Components: Management Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 20.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4484) Support SSH authentication for Git persistence

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-4484?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-4484: -------------------------------- Fix Version/s: 12.0.0.Beta4 (was: 12.0.0.Beta3) > Support SSH authentication for Git persistence > ---------------------------------------------- > > Key: WFCORE-4484 > URL: https://issues.redhat.com/browse/WFCORE-4484 > Project: WildFly Core > Issue Type: Feature Request > Components: Management, Security > Reporter: Farah Juma > Assignee: Ashley Abdel-Sayed > Priority: Major > Labels: EAP-CD19 > Fix For: 12.0.0.Beta4 > > > Currently Elytron only supports authentication for HTTP(s) URLS so there is no way to connect to a SSH git server to pull/push configuration history -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4670) Upgrade JBoss MSC to 1.4.12.Final

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-4670?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-4670: -------------------------------- Fix Version/s: 12.0.0.Beta4 (was: 12.0.0.Beta3) > Upgrade JBoss MSC to 1.4.12.Final > --------------------------------- > > Key: WFCORE-4670 > URL: https://issues.redhat.com/browse/WFCORE-4670 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Reporter: Katarina Hermanova > Assignee: Richard Opalka > Priority: Major > Fix For: 12.0.0.Beta4 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4962) Add a SecurityMetaData for all deployments

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-4962?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-4962: -------------------------------- Fix Version/s: 12.0.0.Beta4 (was: 12.0.0.Beta3) > Add a SecurityMetaData for all deployments > ------------------------------------------ > > Key: WFCORE-4962 > URL: https://issues.redhat.com/browse/WFCORE-4962 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 12.0.0.Beta4 > > > For all deployments we should associate a new class SecurityMetaData with the deployment, initially the purpose of this will be to hold the ServiceName of any Elytron SecurityDomain if one is being used. > At a later point additional security policy information can be added as we move away from the ApplicationSecurityDomain resources. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4963) At the end of Phase.PARSE populate SecurityMetaData with the name of any Virtual SecurityDomain

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-4963?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-4963: -------------------------------- Fix Version/s: 12.0.0.Beta4 (was: 12.0.0.Beta3) > At the end of Phase.PARSE populate SecurityMetaData with the name of any Virtual SecurityDomain > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-4963 > URL: https://issues.redhat.com/browse/WFCORE-4963 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 12.0.0.Beta4 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4972) LatersTest doesn't follow module aliases

by Jean Francois Denise (Jira)

Jean Francois Denise created WFCORE-4972: -------------------------------------------- Summary: LatersTest doesn't follow module aliases Key: WFCORE-4972 URL: https://issues.redhat.com/browse/WFCORE-4972 Project: WildFly Core Issue Type: Bug Components: Test Suite Reporter: Jean Francois Denise Assignee: Jean Francois Denise -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13444) Observing High CPU in EPollArrayWrapper.epollCtl default I/O thread

by Srinivas ev (Jira)

[ https://issues.redhat.com/browse/WFLY-13444?page=com.atlassian.jira.plugi... ] Srinivas ev updated WFLY-13444: ------------------------------- Priority: Critical (was: Major) > Observing High CPU in EPollArrayWrapper.epollCtl default I/O thread > ------------------------------------------------------------------- > > Key: WFLY-13444 > URL: https://issues.redhat.com/browse/WFLY-13444 > Project: WildFly > Issue Type: Bug > Components: Remoting > Affects Versions: 10.1.0.Final > Reporter: Srinivas ev > Assignee: Flavia Rainone > Priority: Critical > Attachments: IO thread memory.PNG, IO thread.PNG, Thread consuming high CPU.PNG, ThreadDump1set.zip, ThreadDump2set.zip, default IO thread 73.PNG, default io consuming snapshot.PNG, default io consuming.PNG, stack trace from snapshot.PNG, stack trace in thread dump.PNG, threaddump-1589514505334.tdump, top command output.PNG > > > Facing high CPU by one of the default I/O thread In Wildfly 10.1.0 Final. Looks none of our application component thread is consuming. > Can somebody check what is triggering this issue? I attached the thread stack to this Jira. This is blocking our releases. When the CPU cores are high in number, multiple default I/O threads will kick in consuming the CPU in 90~100% range continuously. > Wildfly 10.1.0 Final > Java - > openjdk version "1.8.0_232" > OpenJDK Runtime Environment (build 1.8.0_232-b09) > OpenJDK 64-Bit Server VM (build 25.232-b09, mixed mode > --------------------------------------------------------------------------------------------------- > at java.lang.Throwable.fillInStackTrace(Native Method) > at java.lang.Throwable.fillInStackTrace(Throwable.java:784) > at java.lang.Throwable.<init>(Throwable.java:251) > at java.lang.Exception.<init>(Exception.java:54) > at java.io.IOException.<init>(IOException.java:47) > at java.nio.channels.ClosedChannelException.<init>(ClosedChannelException.java:52) > at org.xnio.ssl.JsseStreamConduit.write(JsseStreamConduit.java:1022) > at org.xnio.conduits.ConduitStreamSinkChannel.write(ConduitStreamSinkChannel.java:150) > at org.xnio.http.HttpUpgrade$HttpUpgradeState$StringWriteListener.handleEvent(HttpUpgrade.java:385) > at org.xnio.http.HttpUpgrade$HttpUpgradeState$StringWriteListener.handleEvent(HttpUpgrade.java:372) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.conduits.WriteReadyHandler$ChannelListenerHandler.writeReady(WriteReadyHandler.java:65) > at org.xnio.ssl.JsseStreamConduit.run(JsseStreamConduit.java:393) > at org.xnio.ssl.JsseStreamConduit.readReady(JsseStreamConduit.java:547) > at org.xnio.ssl.JsseStreamConduit$2.readReady(JsseStreamConduit.java:319) > at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:567) > ------------------------------------------------------------------------------------------- > at sun.nio.ch.EPollArrayWrapper.epollCtl(Native Method) > at sun.nio.ch.EPollArrayWrapper.updateRegistrations(EPollArrayWrapper.java:299) > at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:268) > at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93) > at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:101) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:515) > ----------------------------------------------------------------------------------- -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13484) JSF - submitting empty fields does not work

by Frank Heldt (Jira)

[ https://issues.redhat.com/browse/WFLY-13484?page=com.atlassian.jira.plugi... ] Frank Heldt updated WFLY-13484: ------------------------------- Description: A simple JSF webapp with an input field <p:inputMask value="#\{myCtrl.num\}" mask="?9999" slotChar="" size="4" maxlength="4"/> and in the controller private Short num; // + getter/setter When the input field is empty, the setter is never called on submit. The same webapp under WildFly 19.0.0 works as expected, in this case the setter is called with a null value. was: A simple JSF webapp with an input field <p:inputMask value="#{myCtrl.num}" mask="?9999" slotChar="" size="4" maxlength="4"/> and in the controller private Short num; // + getter/setter When the input field is empty, the setter is never called on submit. The same webapp under WildFly 19.0.0 works as expected, in this case the setter is called with a null value. > JSF - submitting empty fields does not work > ------------------------------------------- > > Key: WFLY-13484 > URL: https://issues.redhat.com/browse/WFLY-13484 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 19.1.0.Final > Reporter: Frank Heldt > Assignee: Farah Juma > Priority: Major > > A simple JSF webapp with an input field > <p:inputMask value="#\{myCtrl.num\}" mask="?9999" slotChar="" size="4" maxlength="4"/> > and in the controller > private Short num; // + getter/setter > When the input field is empty, the setter is never called on submit. > The same webapp under WildFly 19.0.0 works as expected, in this case the setter is called with a null value. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13484) JSF - submitting empty fields does not work

by Frank Heldt (Jira)

[ https://issues.redhat.com/browse/WFLY-13484?page=com.atlassian.jira.plugi... ] Frank Heldt updated WFLY-13484: ------------------------------- Description: A simple JSF webapp with an input field <p:inputMask value="#{myCtrl.num}" mask="?9999" slotChar="" size="4" maxlength="4"/> and in the controller private Short num; // + getter/setter When the input field is empty, the setter is never called on submit. The same webapp under WildFly 19.0.0 works as expected, in this case the setter is called with a null value. was: A simple JSF webapp with an input field {{<p:inputMask value="#{myCtrl.num}" mask="?9999" slotChar="" size="4" maxlength="4"/> }} and in the controller {{private Short num; // + getter/setter}} When the input field is empty, the setter is never called on submit. The same webapp under WildFly 19.0.0 works as expected, in this case the setter is called with a null value. > JSF - submitting empty fields does not work > ------------------------------------------- > > Key: WFLY-13484 > URL: https://issues.redhat.com/browse/WFLY-13484 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 19.1.0.Final > Reporter: Frank Heldt > Assignee: Farah Juma > Priority: Major > > A simple JSF webapp with an input field > <p:inputMask value="#{myCtrl.num}" mask="?9999" slotChar="" size="4" maxlength="4"/> > and in the controller > private Short num; // + getter/setter > When the input field is empty, the setter is never called on submit. > The same webapp under WildFly 19.0.0 works as expected, in this case the setter is called with a null value. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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 May 2020