October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9267) Upgrade Hibernate Validator to 6.0.3.Final

by Leandro Kersting de Freitas (JIRA)

[ https://issues.jboss.org/browse/WFLY-9267?page=com.atlassian.jira.plugin.... ] Leandro Kersting de Freitas updated WFLY-9267: ---------------------------------------------- Summary: Upgrade Hibernate Validator to 6.0.3.Final (was: Upgrade Hibernate Validator to 6.0.2.Final ) > Upgrade Hibernate Validator to 6.0.3.Final > ------------------------------------------- > > Key: WFLY-9267 > URL: https://issues.jboss.org/browse/WFLY-9267 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Leandro Kersting de Freitas > Assignee: Jason Greene > Fix For: 11.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9266) Upgrade Hibernate ORM to 5.2.12.Final

by Leandro Kersting de Freitas (JIRA)

[ https://issues.jboss.org/browse/WFLY-9266?page=com.atlassian.jira.plugin.... ] Leandro Kersting de Freitas updated WFLY-9266: ---------------------------------------------- Summary: Upgrade Hibernate ORM to 5.2.12.Final (was: Upgrade Hibernate ORM to 5.2.11.Final) > Upgrade Hibernate ORM to 5.2.12.Final > ------------------------------------- > > Key: WFLY-9266 > URL: https://issues.jboss.org/browse/WFLY-9266 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Leandro Kersting de Freitas > Assignee: Jason Greene > Fix For: 11.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9456) High non heap memory consumption

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-9456?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-9456: ------------------------------------- I'm not sure this is the issue, but there was a bug with OpenJDK 1.8.0_144-b01 where large memory consumption was an issue. On Fedora there was a fix for it earlier this week I believe. For me on Fedora with the latest OpenJDK I get the following: {code:title=WildFly 11.0.0.CR1} jperkins 13639 9.3 0.8 6366512 287328 pts/9 Sl+ 13:23 0:08 java -D[Standalone] -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m {code} {code:title=WildFly 10.1.0.Final} jperkins 14634 172 0.9 6394860 295060 pts/9 Sl+ 13:29 0:08 java -D[Standalone] -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m {code} > High non heap memory consumption > -------------------------------- > > Key: WFLY-9456 > URL: https://issues.jboss.org/browse/WFLY-9456 > Project: WildFly > Issue Type: Bug > Components: Class Loading > Affects Versions: 11.0.0.CR1 > Environment: CentOS 7 on Google compute engine VM > openjdk version "1.8.0_144" > OpenJDK Runtime Environment (build 1.8.0_144-b01) > OpenJDK 64-Bit Server VM (build 25.144-b01, mixed mode) > Reporter: Klaus Erber > Assignee: David Lloyd > Attachments: wf10-nmt.txt, wf11-nmt.txt > > > After a clean install of WF11CR1 without any configuration changes and startup with standalone.sh we see a high memory usage on the system side (about 800 MB). > Wenn we do the same with WF10Final we see a memory usage of about 210 MB. > Her are the output auf ps aux: > wf11 > ke4 1652 14.0 22.1 2863404 *801620* pts/3 Sl+ 14:01 0:07 java -D[Standalone] -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m > wf10 > ke4 1836 42.1 5.7 2687744 *209204* pts/2 Sl+ 14:02 0:06 java -D[Standalone] -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m > The result is, that we can only start 3 instances of wildfly 11 on a 3.75 GB VM. The 4th instance crashes the system. In our real scenario (Wildfly instances in docker containers hosting the REST interface for our application) we see about 1 GB memory consumption per backend node. > The heap and other memory pools not seems to be the reason for this behaviour - see the attached native memory tracking results. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9459) Outdated doc für ejb client

by Wolfgang Knauf (JIRA)

Wolfgang Knauf created WFLY-9459: ------------------------------------ Summary: Outdated doc für ejb client Key: WFLY-9459 URL: https://issues.jboss.org/browse/WFLY-9459 Project: WildFly Issue Type: Bug Components: Documentation Affects Versions: 11.0.0.CR1 Reporter: Wolfgang Knauf The WildFly doc contains some pages which should be updated to reflect the change to "WildFly naming client" instead of "EJB client API"/"remote naming project": [link EJB invocations from a remote client using JNDI|https://docs.jboss.org/author/display/WFLY/EJB+invocations+from+a+re...] [link Remote EJB invocations via JNDI - EJB client API or remote-naming project |https://docs.jboss.org/author/display/WFLY/Remote+EJB+invocations+via+JNDI+-+EJB+client+API+or+remote-naming+project] This should be fixed mainly in the new asciidoc -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9459) Outdated doc für ejb client

by Wolfgang Knauf (JIRA)

[ https://issues.jboss.org/browse/WFLY-9459?page=com.atlassian.jira.plugin.... ] Wolfgang Knauf updated WFLY-9459: --------------------------------- Description: The WildFly doc contains some pages which should be updated to reflect the change to "WildFly naming client" instead of "EJB client API"/"remote naming project": [EJB invocations from a remote client using JNDI|https://docs.jboss.org/author/display/WFLY/EJB+invocations+from+a+re...] [Remote EJB invocations via JNDI - EJB client API or remote-naming project |https://docs.jboss.org/author/display/WFLY/Remote+EJB+invocations+via+JNDI+-+EJB+client+API+or+remote-naming+project] This should be fixed mainly in the new asciidoc was: The WildFly doc contains some pages which should be updated to reflect the change to "WildFly naming client" instead of "EJB client API"/"remote naming project": [link EJB invocations from a remote client using JNDI|https://docs.jboss.org/author/display/WFLY/EJB+invocations+from+a+re...] [link Remote EJB invocations via JNDI - EJB client API or remote-naming project |https://docs.jboss.org/author/display/WFLY/Remote+EJB+invocations+via+JNDI+-+EJB+client+API+or+remote-naming+project] This should be fixed mainly in the new asciidoc > Outdated doc für ejb client > --------------------------- > > Key: WFLY-9459 > URL: https://issues.jboss.org/browse/WFLY-9459 > Project: WildFly > Issue Type: Bug > Components: Documentation > Affects Versions: 11.0.0.CR1 > Reporter: Wolfgang Knauf > > The WildFly doc contains some pages which should be updated to reflect the change to "WildFly naming client" instead of "EJB client API"/"remote naming project": > [EJB invocations from a remote client using JNDI|https://docs.jboss.org/author/display/WFLY/EJB+invocations+from+a+re...] > [Remote EJB invocations via JNDI - EJB client API or remote-naming project |https://docs.jboss.org/author/display/WFLY/Remote+EJB+invocations+via+JNDI+-+EJB+client+API+or+remote-naming+project] > This should be fixed mainly in the new asciidoc -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1409) Update HTTP authentication mechanism API to support re-use of response handlers

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1409?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1409: ---------------------------------- Fix Version/s: 1.2.0.Beta9 (was: 1.2.0.Beta8) > Update HTTP authentication mechanism API to support re-use of response handlers > ------------------------------------------------------------------------------- > > Key: ELY-1409 > URL: https://issues.jboss.org/browse/ELY-1409 > Project: WildFly Elytron > Issue Type: Task > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta9 > > > At the moment the response handler can only access the response, it can not access anything from the request unless created with access to the request. > Making the scopes available should allow for state to be transferred on the request scope. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1405) The password attribute of resource owner credentials should support a credential store reference

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1405?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1405: ---------------------------------- Fix Version/s: 1.2.0.Beta9 (was: 1.2.0.Beta8) > The password attribute of resource owner credentials should support a credential store reference > ------------------------------------------------------------------------------------------------ > > Key: ELY-1405 > URL: https://issues.jboss.org/browse/ELY-1405 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta9 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1386) <certificate-revocation-list /> should also support a URI and resource in addition to path.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1386?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1386: ---------------------------------- Fix Version/s: 1.2.0.Beta9 (was: 1.2.0.Beta8) > <certificate-revocation-list /> should also support a URI and resource in addition to path. > ------------------------------------------------------------------------------------------- > > Key: ELY-1386 > URL: https://issues.jboss.org/browse/ELY-1386 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta9 > > > KeyStores can be loaded from a path, a URI, or as a resource - the certificate revocation list should be the same. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1385) Add option to override the TrustManager within <authentication-client ></authentication>

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1385?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1385: ---------------------------------- Fix Version/s: 1.2.0.Beta9 (was: 1.2.0.Beta8) > Add option to override the TrustManager within <authentication-client ></authentication> > ---------------------------------------------------------------------------------------- > > Key: ELY-1385 > URL: https://issues.jboss.org/browse/ELY-1385 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta9 > > > At the moment we can reference an alias from a KeyStore and reference a complete KeyStore for use by the TrustManager but there is not option to override which > trust managers are actually enabled. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1379) KeyStore element does not support overriding Provider discovery

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1379?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1379: ---------------------------------- Fix Version/s: 1.2.0.Beta9 (was: 1.2.0.Beta8) > KeyStore element does not support overriding Provider discovery > --------------------------------------------------------------- > > Key: ELY-1379 > URL: https://issues.jboss.org/browse/ELY-1379 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta9 > > > Additionally it doesn't take into account the default Provider discovery or the Provider definition at the root of the <authentication-configuration /> definition. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 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 October 2017