October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1420) Release WildFly Elytron 1.2.0.Beta8

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1420?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1420. ----------------------------------- Resolution: Done > Release WildFly Elytron 1.2.0.Beta8 > ----------------------------------- > > Key: ELY-1420 > URL: https://issues.jboss.org/browse/ELY-1420 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta8 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1417) Add unseen nonce count tracking support

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1417?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1417: ---------------------------------- Fix Version/s: 1.2.0.Beta9 (was: 1.1.6.CR1) > Add unseen nonce count tracking support > --------------------------------------- > > Key: ELY-1417 > URL: https://issues.jboss.org/browse/ELY-1417 > Project: WildFly Elytron > Issue Type: Sub-task > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta9 > > > i.e. the ranges of missing nonce counts we have not yet seen. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2223) Make DNS_PING more user-friendly

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/JGRP-2223?page=com.atlassian.jira.plugin.... ] Paul Ferraro reassigned JGRP-2223: ---------------------------------- Assignee: Paul Ferraro (was: Sebastian Łaskawiec) > Make DNS_PING more user-friendly > -------------------------------- > > Key: JGRP-2223 > URL: https://issues.jboss.org/browse/JGRP-2223 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 4.0.7 > Reporter: Sebastian Łaskawiec > Assignee: Paul Ferraro > Priority: Minor > Fix For: 4.0.8 > > > Currently the {{DNS_PING}} protocol is pretty hard to use. User needs to specify both DNS Server Address (which could be automatically discovered) and needs to specify {{svc.cluster.local}} suffix (which could be automatically added - if missing). -- 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 David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-9456?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-9456: ----------------------------------- What about direct buffer space? > 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] (WFCORE-3366) Upgrade JBoss Remoting to 5.0.5.Final

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3366?page=com.atlassian.jira.plugi... ] David Lloyd updated WFCORE-3366: -------------------------------- Summary: Upgrade JBoss Remoting to 5.0.5.Final (was: Upgrade JBoss Remoting to 5.0.4.Final) > Upgrade JBoss Remoting to 5.0.5.Final > ------------------------------------- > > Key: WFCORE-3366 > URL: https://issues.jboss.org/browse/WFCORE-3366 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Remoting > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 4.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9458) Support expressions for "site" attribute inside "backup" element in infinispan subsystem

by Marek Posolda (JIRA)

Marek Posolda created WFLY-9458: ----------------------------------- Summary: Support expressions for "site" attribute inside "backup" element in infinispan subsystem Key: WFLY-9458 URL: https://issues.jboss.org/browse/WFLY-9458 Project: WildFly Issue Type: Feature Request Components: Clustering Affects Versions: 11.0.0.CR1 Reporter: Marek Posolda Assignee: Paul Ferraro Priority: Minor Assume I have this in standalone.xml in infinispan subsystem: {code} <distributed-cache name="foo"> <backups> <backup site="${remote.site}" failure-policy="${backup.policy}" strategy="SYNC" enabled="true"/> </backups> </distributed-cache> {code} and I run server with: {code} ./standalone.sh -Dremote.site=mysite -Dbackup.policy=FAIL {code} I can see that "backup.policy" expression is correctly resolved, but "remote.site" is not. Indeed BackupResourceDefinition class, enum "Attribute" doesn't contain SITE attribute. It will be nice if expressions are supported for "site" attribute too, so that I can have single ZIP distribution and use it for simulate testing with more sites and just use different system properties to simulate different site. BTV. JGroups subsystem already supports the expressions inside "relay" element. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3347) add-content operation of deployment resource contains alternative attributes that doesn't exist

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3347?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3347: ------------------------------------------ [~soul2zimate] Sounds like a bug. That if test can be removed altogether since if !isFlagPresent the method will have returned. Double checking is wasteful and a source of bugs like this. > add-content operation of deployment resource contains alternative attributes that doesn't exist > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-3347 > URL: https://issues.jboss.org/browse/WFCORE-3347 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Claudio Miranda > Assignee: Chao Wang > Priority: Minor > > add-content operation contains "content" attribute, > {code} > /deployment=*:read-operation-description(name=add-content) > {code} > "content" attribute it is a list of other attributes as: input-stream-index, hash, bytes, url. They themselves contains the alternatives metadata as > {code} > "url" => { > "type" => STRING, > "description" => "The URL at which the deployment content is available for upload to the domain's or standalone server's deployment content repository.. Note that the URL must be accessible from the target of the operation (i.e. the Domain Controller or standalone server).", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "alternatives" => [ > "input-stream-index", > "hash", > "bytes", > "path", > "relative-to", > "empty" > ], > "min-length" => 1L, > "max-length" => 2147483647L > }, > {code} > But the following attributes doesn't exist: path, relative-to, empty -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1421) Elytron 1.2 user impacting issues

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-1421?page=com.atlassian.jira.plugin.s... ] Martin Choma reassigned ELY-1421: --------------------------------- Assignee: Martin Choma (was: Darran Lofthouse) > Elytron 1.2 user impacting issues > --------------------------------- > > Key: ELY-1421 > URL: https://issues.jboss.org/browse/ELY-1421 > Project: WildFly Elytron > Issue Type: Tracker > Reporter: Martin Choma > Assignee: Martin Choma > Priority: Trivial > > This issue is for tracking changes in Elytron 1.2 which brings new configuration options to users. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3376) Modules may create loggers on a deployments log context

by James Perkins (JIRA)

James Perkins created WFCORE-3376: ------------------------------------- Summary: Modules may create loggers on a deployments log context Key: WFCORE-3376 URL: https://issues.jboss.org/browse/WFCORE-3376 Project: WildFly Core Issue Type: Bug Components: Logging Reporter: James Perkins Assignee: James Perkins Currently WildFly uses a {{ClassLoaderLogContextSelector}} to determine the log context to use when creating loggers. If a deployment has it's own log context, via logging-profile or per-deployment logging, and a dependency on a module, that module may create loggers on the deployments log context. This is due to the fact the the call stack is walked until it finds a log context associated with a class loader. What is needed is a way to short-circuit once a non-logging API class loader is found and determine if there is an associated log context with the callers class loader. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1422) Add possibility to disable channel binding in Elytron clients

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1422?page=com.atlassian.jira.plugin.s... ] Jan Kalina moved JBEAP-13558 to ELY-1422: ----------------------------------------- Project: WildFly Elytron (was: JBoss Enterprise Application Platform) Key: ELY-1422 (was: JBEAP-13558) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: SASL (was: Security) Affects Version/s: 1.2.0.Beta7 (was: 7.1.0.CR1) > Add possibility to disable channel binding in Elytron clients > ------------------------------------------------------------- > > Key: ELY-1422 > URL: https://issues.jboss.org/browse/ELY-1422 > Project: WildFly Elytron > Issue Type: Feature Request > Components: SASL > Affects Versions: 1.2.0.Beta7 > Reporter: Jan Kalina > > Add Elytron client option to disable channel binding so non-PLUS (SCRAM) mechanisms can be used even if the SSL context is configured for the underlying remoting connection. > This is a follow up jira to JBEAP-12231 (and transitively JBEAP-11396) - look for full discussion there. -- 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