December 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2083) Reduce number of object allocations and memory footprint

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2083?page=com.atlassian.jira.plugi... ] Tomaz Cerar updated WFCORE-2083: -------------------------------- Summary: Reduce number of object allocations and memory footprint (was: Increased Memory footprint in recent builds) > Reduce number of object allocations and memory footprint > -------------------------------------------------------- > > Key: WFCORE-2083 > URL: https://issues.jboss.org/browse/WFCORE-2083 > Project: WildFly Core > Issue Type: Bug > Components: Modules, Server > Affects Versions: 3.0.0.Alpha14 > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Priority: Critical > > In our test scenario (see below) memory footprint has been increased between EAP 7.0.0.GA and current EAP 7.1.0.DR7 for more than 8% (~8MB) for Full profile and more than 9% (~6.5MB) for web profile. Could you please comment whether this is intended. > Test scenario: > # Start EAP instance. > # Measure its memory footprint - try to get the lowest possible footprint, that means force garbage collection a few times right before measuring. We enforce GC 10 times. > We see an increase both in heap size (~ 29 vs. 34 MB) and the metaspace size (~ 64 vs. 68 MB) - these numbers are for standalone-full profile. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2083) Increased Memory footprint in recent builds

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2083?page=com.atlassian.jira.plugi... ] Tomaz Cerar moved WFLY-7729 to WFCORE-2083: ------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-2083 (was: WFLY-7729) Component/s: Modules Server (was: Server) Affects Version/s: 3.0.0.Alpha14 (was: 11.0.0.Alpha1) > Increased Memory footprint in recent builds > ------------------------------------------- > > Key: WFCORE-2083 > URL: https://issues.jboss.org/browse/WFCORE-2083 > Project: WildFly Core > Issue Type: Bug > Components: Modules, Server > Affects Versions: 3.0.0.Alpha14 > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Priority: Critical > > In our test scenario (see below) memory footprint has been increased between EAP 7.0.0.GA and current EAP 7.1.0.DR7 for more than 8% (~8MB) for Full profile and more than 9% (~6.5MB) for web profile. Could you please comment whether this is intended. > Test scenario: > # Start EAP instance. > # Measure its memory footprint - try to get the lowest possible footprint, that means force garbage collection a few times right before measuring. We enforce GC 10 times. > We see an increase both in heap size (~ 29 vs. 34 MB) and the metaspace size (~ 64 vs. 68 MB) - these numbers are for standalone-full profile. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7728) Increased Memory footprint in recent builds

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7728?page=com.atlassian.jira.plugin.... ] Tomaz Cerar moved JBEAP-7625 to WFLY-7728: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7728 (was: JBEAP-7625) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Server (was: Performance) (was: Server) Affects Version/s: 11.0.0.Alpha1 (was: 7.1.0.DR7) (was: 7.1.0.DR8) (was: 7.1.0.DR9) > Increased Memory footprint in recent builds > ------------------------------------------- > > Key: WFLY-7728 > URL: https://issues.jboss.org/browse/WFLY-7728 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 11.0.0.Alpha1 > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Priority: Critical > > In our test scenario (see below) memory footprint has been increased between EAP 7.0.0.GA and current EAP 7.1.0.DR7 for more than 8% (~8MB) for Full profile and more than 9% (~6.5MB) for web profile. Could you please comment whether this is intended. > Test scenario: > # Start EAP instance. > # Measure its memory footprint - try to get the lowest possible footprint, that means force garbage collection a few times right before measuring. We enforce GC 10 times. > We see an increase both in heap size (~ 29 vs. 34 MB) and the metaspace size (~ 64 vs. 68 MB) - these numbers are for standalone-full profile. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7729) Increased Memory footprint in recent builds

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-7729: --------------------------------- Summary: Increased Memory footprint in recent builds Key: WFLY-7729 URL: https://issues.jboss.org/browse/WFLY-7729 Project: WildFly Issue Type: Bug Components: Server Affects Versions: 11.0.0.Alpha1 Reporter: Tomaz Cerar Assignee: Tomaz Cerar Priority: Critical In our test scenario (see below) memory footprint has been increased between EAP 7.0.0.GA and current EAP 7.1.0.DR7 for more than 8% (~8MB) for Full profile and more than 9% (~6.5MB) for web profile. Could you please comment whether this is intended. Test scenario: # Start EAP instance. # Measure its memory footprint - try to get the lowest possible footprint, that means force garbage collection a few times right before measuring. We enforce GC 10 times. We see an increase both in heap size (~ 29 vs. 34 MB) and the metaspace size (~ 64 vs. 68 MB) - these numbers are for standalone-full profile. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2082) Outdated deployment-scanner xml snippet in deployments readme.txt

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2082?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet moved JBEAP-7624 to WFCORE-2082: -------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2082 (was: JBEAP-7624) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Deployment Scanner (was: Deployment Scanner) (was: User Experience) Affects Version/s: 3.0.0.Alpha14 (was: 7.1.0.DR7) > Outdated deployment-scanner xml snippet in deployments readme.txt > ----------------------------------------------------------------- > > Key: WFCORE-2082 > URL: https://issues.jboss.org/browse/WFCORE-2082 > Project: WildFly Core > Issue Type: Bug > Components: Deployment Scanner > Affects Versions: 3.0.0.Alpha14 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Priority: Trivial > > $JBOSS_HOME/standalone/deployments/README.txt contains following configuration XML snippet: > {code:xml} > <deployment-scanner scan-interval="5000" relative-to="jboss.server.base.dir" path="deployments" auto-deploy-zipped="true" auto-deploy-exploded="false"/> > {code} > but actual snippet from standalone.xml config file is > {code:xml} > <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" runtime-failure-causes-rollback="${jboss.deployment.scanner.rollback.on.failure:false}"/> > {code} > This might be confusing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2081) Confusing description of scan-enabled attribute in deployment scanner XSD

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2081?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet moved JBEAP-7623 to WFCORE-2081: -------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2081 (was: JBEAP-7623) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Deployment Scanner (was: Deployment Scanner) (was: User Experience) Affects Version/s: 3.0.0.Alpha14 (was: 7.1.0.DR7) > Confusing description of scan-enabled attribute in deployment scanner XSD > ------------------------------------------------------------------------- > > Key: WFCORE-2081 > URL: https://issues.jboss.org/browse/WFCORE-2081 > Project: WildFly Core > Issue Type: Bug > Components: Deployment Scanner > Affects Versions: 3.0.0.Alpha14 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Priority: Optional > > Documentation of *scan-enabled* attribute in $JBOSS_HOME/docs/schema/jboss-as-deployment-scanner_2_0.xsd is > _Flag indicating that all *scanning* (including initial scanning at startup) should be *disabled*._ > This is confusing. Please change it to something like > _Flag indicating if all scanning (including initial scanning at startup) should be enabled or disabled._ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7498) Elytron Credential Store "store.base" parameter doesn't work properly.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFLY-7498?page=com.atlassian.jira.plugin.... ] Hynek Švábek updated WFLY-7498: ------------------------------- Priority: Blocker (was: Major) > Elytron Credential Store "store.base" parameter doesn't work properly. > ---------------------------------------------------------------------- > > Key: WFLY-7498 > URL: https://issues.jboss.org/browse/WFLY-7498 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Peter Skopek > Priority: Blocker > > Elytron Credential Store "store.base" parameter doesn't work properly. > I tried create credential store from scratch: > {code} > /subsystem=elytron/credential-store=cs001_sb:add(uri="cr-store://test/key126.jceks?store.password=pass123;key.password=pass456;create.storage=true; > store.base=/tmp;key.alias=MY_ALIAS") > {code} > {code} > /subsystem=elytron/credential-store=cs001_sb/alias=alias001:add(secret-value=secValue) > {code} > and credential store file *is created in JBOSS_EAP/Standalone/data path not in /tmp.* > *My investigation* > * Here it seems fine https://github.com/wildfly-security/wildfly-elytron/blob/0f0e0109c2652fdc... > * Maybe some kind of compiler optimisation (switch line execution?) https://github.com/wildfly-security/wildfly-elytron/blob/0f0e0109c2652fdc... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7623) Multiple CredentialStores with ONE backed credential store file can rewrite values each other.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFLY-7623?page=com.atlassian.jira.plugin.... ] Hynek Švábek updated WFLY-7623: ------------------------------- Priority: Blocker (was: Major) > Multiple CredentialStores with ONE backed credential store file can rewrite values each other. > ---------------------------------------------------------------------------------------------- > > Key: WFLY-7623 > URL: https://issues.jboss.org/browse/WFLY-7623 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Peter Skopek > Priority: Blocker > > Multiple CredentialStores with ONE backed credential store file can rewrite values each other. > *How to reproduce* > {code} > /subsystem=elytron/credential-store=credStore001:add(uri="cr-store://test/cs001.jceks?store.password=pass123;create.storage=true") > /subsystem=elytron/credential-store=credStore001/alias="alias1":add(secret-value=Elytron) > {code} > {code} > /subsystem=elytron/credential-store=credStore002:add(uri="cr-store://test/cs001.jceks?store.password=pass123") > {code} > check CS file > there is "alias1" entry > {code} > /subsystem=elytron/credential-store=credStore001/alias="alias2":add(secret-value=Elytron) > {code} > check CS file > there are "alias1" and "alias2" entries > {code} > /subsystem=elytron/credential-store=credStore002/alias="alias123":add(secret-value=Elytron) > {code} > check CS file > there are "alias1" and "alias123" entries". > *NOTE* > It is problem, because we have one backed file. In memory we have right values for all Credential Stores, but after restart we can lost new entries. > In my opinion reason for this behaviour is: > We have CS loaded in memory and when we add new alias to CS then we save whole CS from memory to file. > We can set CS as non-modifiable when we use same backed file for CredentialStore but we must find better default behaviour. > *My suggestion for default behaviour* > When we want to add new alias to CredentialStore we can do this: > # refresh CS from file (and this file lock) > # add new alias to CS > # save CS to file > # unlock file > *But there is posible problem with performance....* -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-652) There isn't possibility set entry-type for new entry in Credential Store.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/ELY-652?page=com.atlassian.jira.plugin.sy... ] Hynek Švábek updated ELY-652: ----------------------------- Priority: Critical (was: Major) > There isn't possibility set entry-type for new entry in Credential Store. > ------------------------------------------------------------------------- > > Key: ELY-652 > URL: https://issues.jboss.org/browse/ELY-652 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store > Reporter: Hynek Švábek > Assignee: Peter Skopek > Priority: Critical > > There isn't possibility set entry-type for new entry in Credential Store > This CLI command > {code} > /subsystem=elytron/credential-store=testCS/alias=aliasEntryType:add(secret-value=secretVALUE, entry-type=org.wildfly.security.credential.PasswordCredential) > {code} > ends with > {code} > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: WFLYELY00909: Credential store 'testCS' does not support given credential store entry type 'org.wildfly.security.credential.PasswordCredential'", > "rolled-back" => true > } > {code} > *Server log:* > {code} > 10:30:39,074 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 18) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("credential-store" => "testCS"), > ("alias" => "aliasEntryType") > ]): java.lang.IllegalArgumentException: WFLYELY00909: Credential store 'testCS' does not support given credential store entry type 'org.wildfly.security.credential.PasswordCredential' > at org.wildfly.extension.elytron.CredentialStoreAliasDefinition$AddHandler.performRuntime(CredentialStoreAliasDefinition.java:166) > at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:151) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:940) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:683) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:382) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1363) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:410) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:232) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:213) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:136) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-676) There isn't possible change value for given alias in Credential Store over CLI.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/ELY-676?page=com.atlassian.jira.plugin.sy... ] Hynek Švábek updated ELY-676: ----------------------------- Priority: Critical (was: Major) > There isn't possible change value for given alias in Credential Store over CLI. > ------------------------------------------------------------------------------- > > Key: ELY-676 > URL: https://issues.jboss.org/browse/ELY-676 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store > Affects Versions: 1.1.0.Beta10 > Reporter: Hynek Švábek > Assignee: Peter Skopek > Priority: Critical > > There isn't possible change value for given alias in Credential Store over CLI. > I expected something like this > {code} > /subsystem=elytron/credential-store=credStore/alias=entryAlias:update(secret-value=newSecretValue) > {code} > Write-attribute operation doesn't work too. Operation pass but any changes are not propagated to Credential Store. > {code} > /subsystem=elytron/credential-store=credStore/alias=entryAlias:write-attribute(name="secret-value" value="newSecretValue") > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2016