January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1276) Undertow 1.3.12.Final

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1276?page=com.atlassian.jira.plugi... ] Stuart Douglas moved JBEAP-2591 to WFCORE-1276: ----------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-1276 (was: JBEAP-2591) Workflow: GIT Pull Request workflow (was: CDW v1) > Undertow 1.3.12.Final > --------------------- > > Key: WFCORE-1276 > URL: https://issues.jboss.org/browse/WFCORE-1276 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Stuart Douglas > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1275) CLI resolve-parameter-values set to true does not recognise vaulted strings

by Lin Gao (JIRA)

Lin Gao created WFCORE-1275: ------------------------------- Summary: CLI resolve-parameter-values set to true does not recognise vaulted strings Key: WFCORE-1275 URL: https://issues.jboss.org/browse/WFCORE-1275 Project: WildFly Core Issue Type: Bug Components: CLI Affects Versions: 2.0.5.Final Reporter: Lin Gao Assignee: Lin Gao When enabling <resolve-parameter-values>true</resolve-parameter-values> in "bin\jboss-cli.xml" vaulted string will get misinterpreted. Example, if a command has "${VAULT::tom::tom::1}" then the parser sees this as ${name:defaultValue} with name="VAULT" defaultValue=":tom::tom::1" Escaping the $ sign in various ways did not help. The only way is to switch <resolve-parameter-values> back to false. Ideally, the parser should recognize vaulted string and pass then in unchanged. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1274) CLI resolve-parameter-values set to true does not recognise vaulted strings

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1274?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated WFCORE-1274: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1286677 > CLI resolve-parameter-values set to true does not recognise vaulted strings > --------------------------------------------------------------------------- > > Key: WFCORE-1274 > URL: https://issues.jboss.org/browse/WFCORE-1274 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.5.Final > Reporter: Lin Gao > Assignee: Lin Gao > > When enabling > <resolve-parameter-values>true</resolve-parameter-values> > in "bin\jboss-cli.xml" > vaulted string will get misinterpreted. > Example, if a command has "${VAULT::tom::tom::1}" then > the parser sees this as ${name:defaultValue} with > name="VAULT" > defaultValue=":tom::tom::1" > Escaping the $ sign in various ways did not help. The only way is to switch <resolve-parameter-values> back to false. > Ideally, the parser should recognize vaulted string and pass then in unchanged. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1274) CLI resolve-parameter-values set to true does not recognise vaulted strings

by Lin Gao (JIRA)

Lin Gao created WFCORE-1274: ------------------------------- Summary: CLI resolve-parameter-values set to true does not recognise vaulted strings Key: WFCORE-1274 URL: https://issues.jboss.org/browse/WFCORE-1274 Project: WildFly Core Issue Type: Bug Components: CLI Affects Versions: 2.0.5.Final Reporter: Lin Gao Assignee: Lin Gao When enabling <resolve-parameter-values>true</resolve-parameter-values> in "bin\jboss-cli.xml" vaulted string will get misinterpreted. Example, if a command has "${VAULT::tom::tom::1}" then the parser sees this as ${name:defaultValue} with name="VAULT" defaultValue=":tom::tom::1" Escaping the $ sign in various ways did not help. The only way is to switch <resolve-parameter-values> back to false. Ideally, the parser should recognize vaulted string and pass then in unchanged. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5822) Clustering performance regression in ejbremote-dist-sync scenario

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/WFLY-5822?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz edited comment on WFLY-5822 at 1/6/16 7:59 PM: ------------------------------------------------------------------- Some statistics on session creation calls, method invocation calls and the resulting gets/puts during such calls (totals over running the test for a few iterations): EAP 7.0.0.DR9: ||operation||perf18||perf19||perf20||perf21|| |SessionCreation|98|99|103|100| |MethodInvocation|35854|35871|36046|36037| |Get|179368|179454|180333|180205| |Put|808|808|558|393| EAP 6.4.0: ||operation||perf18||perf19||perf20||perf21|| |SessionCreation|22|22|36|29| |MethodInvocation|4299|6954|4738|6614| |Get|8598|13911|9478|13253| |Put|9473 |11742|12512|11598| For every method invocation: EAP 7.0.0 has 5 gets EAP 6.4.0 has 2 gets was (Author: rachmato): Some statistics on session creation calls, method invocation calls and the resulting gets/puts during such calls (totals over running the test for a few iterations): EAP 7.0.0.DR9: ||operation||perf18||perf19||perf20||perf21|| |SessionCreation|98|99|103|100| |MethodInvocation|35854|35871|36046|36037| |Get|179368|179454|180333|180205| |Put|808|808|558|393| EAP 6.4.0: ||operation||perf18||perf19||perf20||perf21|| |SessionCreation|22|22|36|29| |MethodInvocation|4299|6954|4738|6614| |Get|8598|13911|9478|13253| |Put|9473 |11742|12512|11598| > Clustering performance regression in ejbremote-dist-sync scenario > ------------------------------------------------------------------ > > Key: WFLY-5822 > URL: https://issues.jboss.org/browse/WFLY-5822 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB > Affects Versions: 10.0.0.CR5 > Reporter: Michal Vinkler > Assignee: Richard Achmatowicz > Priority: Critical > > Compared to EAP 6, all SYNC scenarios have the same/better performance except of this one, wonder why? > Compare these results: > stress-ejbremote-dist-sync > 7.0.0.ER2: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...] > 6.4.0.GA: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...] > --------------------------------------- > Just for comparison: ejbremote REPL_SYNC scenario *performs well* on the other hand: > stress-ejbremote-repl-sync > 7.0.0.ER2: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...] > 6.4.0.GA: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5822) Clustering performance regression in ejbremote-dist-sync scenario

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/WFLY-5822?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz edited comment on WFLY-5822 at 1/6/16 7:57 PM: ------------------------------------------------------------------- Some statistics on session creation calls, method invocation calls and the resulting gets/puts during such calls (totals over running the test for a few iterations): EAP 7.0.0.DR9: ||operation||perf18||perf19||perf20||perf21|| |SessionCreation|98|99|103|100| |MethodInvocation|35854|35871|36046|36037| |Get|179368|179454|180333|180205| |Put|808|808|558|393| EAP 6.4.0: ||operation||perf18||perf19||perf20||perf21|| |SessionCreation|22|22|36|29| |MethodInvocation|4299|6954|4738|6614| |Get|8598|13911|9478|13253| |Put|9473 |11742|12512|11598| was (Author: rachmato): Some statistics on gets/puts during invocations: EAP 7.0.0.DR9: ||operation||perf18||perf19||perf20||perf21|| |SessionCreation|98|99|103|100| |MethodInvocation|35854|35871|36046|36037| |Get|179368|179454|180333|180205| |Put|808|808|558|393| EAP 6.4.0: ||operation||perf18||perf19||perf20||perf21|| |SessionCreation|22|22|36|29| |MethodInvocation|4299|6954|4738|6614| |Get|8598|13911|9478|13253| |Put|9473 |11742|12512|11598| > Clustering performance regression in ejbremote-dist-sync scenario > ------------------------------------------------------------------ > > Key: WFLY-5822 > URL: https://issues.jboss.org/browse/WFLY-5822 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB > Affects Versions: 10.0.0.CR5 > Reporter: Michal Vinkler > Assignee: Richard Achmatowicz > Priority: Critical > > Compared to EAP 6, all SYNC scenarios have the same/better performance except of this one, wonder why? > Compare these results: > stress-ejbremote-dist-sync > 7.0.0.ER2: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...] > 6.4.0.GA: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...] > --------------------------------------- > Just for comparison: ejbremote REPL_SYNC scenario *performs well* on the other hand: > stress-ejbremote-repl-sync > 7.0.0.ER2: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...] > 6.4.0.GA: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5822) Clustering performance regression in ejbremote-dist-sync scenario

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/WFLY-5822?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz edited comment on WFLY-5822 at 1/6/16 7:56 PM: ------------------------------------------------------------------- Some statistics on gets/puts during invocations: EAP 7.0.0.DR9: ||operation||perf18||perf19||perf20||perf21|| |SessionCreation|98|99|103|100| |MethodInvocation|35854|35871|36046|36037| |Get|179368|179454|180333|180205| |Put|808|808|558|393| EAP 6.4.0: ||operation||perf18||perf19||perf20||perf21|| |SessionCreation|22|22|36|29| |MethodInvocation|4299|6954|4738|6614| |Get|8598|13911|9478|13253| |Put|9473 |11742|12512|11598| was (Author: rachmato): Some statistics on gets/puts during invocations: EAP 7.x: ||operation||perf18||perf19||perf20||perf21|| |SessionCreation|98|99|103|100| |MethodInvocation|35854|35871|36046|36037| |Get|179368|179454|180333|180205| |Put|808|808|558|393| > Clustering performance regression in ejbremote-dist-sync scenario > ------------------------------------------------------------------ > > Key: WFLY-5822 > URL: https://issues.jboss.org/browse/WFLY-5822 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB > Affects Versions: 10.0.0.CR5 > Reporter: Michal Vinkler > Assignee: Richard Achmatowicz > Priority: Critical > > Compared to EAP 6, all SYNC scenarios have the same/better performance except of this one, wonder why? > Compare these results: > stress-ejbremote-dist-sync > 7.0.0.ER2: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...] > 6.4.0.GA: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...] > --------------------------------------- > Just for comparison: ejbremote REPL_SYNC scenario *performs well* on the other hand: > stress-ejbremote-repl-sync > 7.0.0.ER2: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...] > 6.4.0.GA: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5822) Clustering performance regression in ejbremote-dist-sync scenario

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/WFLY-5822?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz commented on WFLY-5822: ------------------------------------------- Some statistics on gets/puts during invocations: EAP 7.x: ||operation||perf18||perf19||perf20||perf21|| |SessionCreation|98|99|103|100| |MethodInvocation|35854|35871|36046|36037| |Get|179368|179454|180333|180205| |Put|808|808|558|393| > Clustering performance regression in ejbremote-dist-sync scenario > ------------------------------------------------------------------ > > Key: WFLY-5822 > URL: https://issues.jboss.org/browse/WFLY-5822 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB > Affects Versions: 10.0.0.CR5 > Reporter: Michal Vinkler > Assignee: Richard Achmatowicz > Priority: Critical > > Compared to EAP 6, all SYNC scenarios have the same/better performance except of this one, wonder why? > Compare these results: > stress-ejbremote-dist-sync > 7.0.0.ER2: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...] > 6.4.0.GA: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...] > --------------------------------------- > Just for comparison: ejbremote REPL_SYNC scenario *performs well* on the other hand: > stress-ejbremote-repl-sync > 7.0.0.ER2: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...] > 6.4.0.GA: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5945) immutable-entity cache configuration is not started by the JPA subsystem

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-5945?page=com.atlassian.jira.plugin.... ] Paul Ferraro reassigned WFLY-5945: ---------------------------------- Assignee: Paul Ferraro (was: Scott Marlow) > immutable-entity cache configuration is not started by the JPA subsystem > ------------------------------------------------------------------------ > > Key: WFLY-5945 > URL: https://issues.jboss.org/browse/WFLY-5945 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Paul Ferraro > Fix For: 10.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5946) naturalid cache configuration is not started by the JPA subsystem

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-5946?page=com.atlassian.jira.plugin.... ] Paul Ferraro reassigned WFLY-5946: ---------------------------------- Assignee: Paul Ferraro (was: Scott Marlow) > naturalid cache configuration is not started by the JPA subsystem > ----------------------------------------------------------------- > > Key: WFLY-5946 > URL: https://issues.jboss.org/browse/WFLY-5946 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 10.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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 January 2016