June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6684) JMS Bridge should display statistics about messages that have been processed.

by Jiri Daněk (JIRA)

[ https://issues.jboss.org/browse/WFLY-6684?page=com.atlassian.jira.plugin.... ] Jiri Daněk commented on WFLY-6684: ---------------------------------- [~bayern39] I believe that the Artemis patch does not do exactly what is desired. See discussion on ENTMQBR-256. The getMessageCount gives number of messages that the bridge attempted to send, not "number of messages successfully committed". > JMS Bridge should display statistics about messages that have been processed. > ----------------------------------------------------------------------------- > > Key: WFLY-6684 > URL: https://issues.jboss.org/browse/WFLY-6684 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 10.0.0.Final > Environment: JBoss EAP 7 > Reporter: Chen Maoqian > Assignee: Chen Maoqian > Attachments: JBEAP-4653.patch > > > The JMS bridge should show some statistics about messages that have been processed through the bridge for example: > - number of messages successfully committed > - number of messages aborted/rollback -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8895) Upstream dependencies BOMs

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-8895?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-8895: ----------------------------- Labels: (was: eap71_beta) > Upstream dependencies BOMs > -------------------------- > > Key: WFLY-8895 > URL: https://issues.jboss.org/browse/WFLY-8895 > Project: WildFly > Issue Type: Bug > Components: Build System > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Priority: Critical > Fix For: 11.0.0.Beta1 > > > There is upstream dependency in EJB client legacy BOM dependency tree: > {{org.wildfly.client:wildfly-client-config:jar:1.0.0.Beta4:compile}} > Full dependency tree is: > {code} > \- org.jboss.eap:wildfly-ejb-client-legacy-bom:pom:7.1.0.Beta1-redhat-4:compile > +- org.jboss:jboss-ejb-client-legacy:jar:3.0.0.Beta7-redhat-1:compile > +- org.jboss.logging:jboss-logging:jar:3.3.1.Final-redhat-1:compile > +- org.jboss.marshalling:jboss-marshalling:jar:2.0.0.Beta8-redhat-1:compile > +- org.jboss.marshalling:jboss-marshalling-river:jar:2.0.0.Beta8-redhat-1:compile > +- org.jboss.remoting:jboss-remoting:jar:5.0.0.Beta24-redhat-1:compile > | \- org.wildfly.client:wildfly-client-config:jar:1.0.0.Beta4:compile > +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:jar:1.0.1.Final-redhat-1:compile > +- org.jboss.spec.javax.ejb:jboss-ejb-api_3.2_spec:jar:1.0.0.Final-redhat-1:compile > +- org.jboss.xnio:xnio-api:jar:3.5.0.Beta6-redhat-1:compile > +- org.jboss.xnio:xnio-nio:jar:3.5.0.Beta6-redhat-1:compile > +- org.wildfly:wildfly-naming-client:jar:1.0.0.Beta15-redhat-1:compile > +- org.wildfly.common:wildfly-common:jar:1.2.0.Beta10-redhat-1:compile > \- org.wildfly.security:wildfly-elytron:jar:1.1.0.Beta47-redhat-1:compile > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2928) Elytron getting incorrect failure-description storing an inexistent key-store

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2928?page=com.atlassian.jira.plugi... ] Yeray Borges moved JBEAP-11405 to WFCORE-2928: ---------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2928 (was: JBEAP-11405) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) Affects Version/s: (was: 7.1.0.DR19) > Elytron getting incorrect failure-description storing an inexistent key-store > ----------------------------------------------------------------------------- > > Key: WFCORE-2928 > URL: https://issues.jboss.org/browse/WFCORE-2928 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Yeray Borges > Assignee: Yeray Borges > > If we add a non-existing key-store the error message description is incorrect. We get: > "WFLYELY00010: Unable to save KeyStore - path is not defined." it should rather says something like "Keystore test001.jks file does not exist" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8905) Remove wildfly-config.xml from app client test in basic testsuite.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8905?page=com.atlassian.jira.plugin.... ] Darran Lofthouse moved JBEAP-11403 to WFLY-8905: ------------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8905 (was: JBEAP-11403) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security Test Suite (was: Security) (was: Test Suite) > Remove wildfly-config.xml from app client test in basic testsuite. > ------------------------------------------------------------------ > > Key: WFLY-8905 > URL: https://issues.jboss.org/browse/WFLY-8905 > Project: WildFly > Issue Type: Bug > Components: Security, Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 11.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8905) Remove wildfly-config.xml from app client test in basic testsuite.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8905?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-8905: ----------------------------------- Fix Version/s: 11.0.0.Beta1 > Remove wildfly-config.xml from app client test in basic testsuite. > ------------------------------------------------------------------ > > Key: WFLY-8905 > URL: https://issues.jboss.org/browse/WFLY-8905 > Project: WildFly > Issue Type: Bug > Components: Security, Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 11.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1550) wildfly-init-redhat.sh script does not work on RHEL 5 OS

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1550?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1550: ------------------------------------------------- Ivo Hradek <ihradek(a)redhat.com> changed the Status of [bug 1328146|https://bugzilla.redhat.com/show_bug.cgi?id=1328146] from ON_QA to VERIFIED > wildfly-init-redhat.sh script does not work on RHEL 5 OS > -------------------------------------------------------- > > Key: WFCORE-1550 > URL: https://issues.jboss.org/browse/WFCORE-1550 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 2.2.0.CR2 > Reporter: Vlado Pakan > Assignee: Vlado Pakan > Fix For: 3.0.0.Alpha2 > > > Wildfly start-up script $JBOSS_HOME/docs/contrib/scripts/init.d/wildfly-init-redhat.sh tries to get successful start timestamp using following command: > grep -o '[0-9]*' $JBOSS_MARKERFILE > This however does not work on RHEL 5 OS, as grep-2.5.1 does not return regular expression result correctly when used with -o option. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2927) Cut the number of java.util.RegularEnumSet used for attribute and operation flags

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2927?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-2927: ---------------------------------------- Assignee: Brian Stansberry > Cut the number of java.util.RegularEnumSet used for attribute and operation flags > --------------------------------------------------------------------------------- > > Key: WFCORE-2927 > URL: https://issues.jboss.org/browse/WFCORE-2927 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > A heap dump of full wildfly standalone-full-ha shows > 14K enum sets with retained heap of over 566K. The bulk of these are for attribute or operation definitions. > The vast majority of these contain the same few combinations of elements, so AD / OD should detect and use a single instance of these. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2926) CLI class doesn't allow to disable errorOnInteract flag

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2926?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-2926: ----------------------------------------- Description: This flag has been introduced in 7.0. It is enabled by default, CLI class should have been updated to disable it by default. In addition a connect(CommandContextConfiguration config) API should be added to the CLI class to allow for full control on the CommandContext configuration. CommandContextConfiguration being located in the impl package, it should be moved to the API package. was: This flag has been introduced in 7.0. It is enabled by default, CLI class should have been updated to disable it by default. In addition a connect(CommandContextConfiguration config) API should be added to the CLI class to allow for full control on the CommandContext configuration. > CLI class doesn't allow to disable errorOnInteract flag > ------------------------------------------------------- > > Key: WFCORE-2926 > URL: https://issues.jboss.org/browse/WFCORE-2926 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > Priority: Critical > > This flag has been introduced in 7.0. It is enabled by default, CLI class should have been updated to disable it by default. > In addition a connect(CommandContextConfiguration config) API should be added to the CLI class to allow for full control on the CommandContext configuration. > CommandContextConfiguration being located in the impl package, it should be moved to the API package. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2927) Cut the number of java.util.RegularEnumSet used for attribute and operation flags

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-2927: ---------------------------------------- Summary: Cut the number of java.util.RegularEnumSet used for attribute and operation flags Key: WFCORE-2927 URL: https://issues.jboss.org/browse/WFCORE-2927 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Reporter: Brian Stansberry A heap dump of full wildfly standalone-full-ha shows > 14K enum sets with retained heap of over 566K. The bulk of these are for attribute or operation definitions. The vast majority of these contain the same few combinations of elements, so AD / OD should detect and use a single instance of these. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2926) CLI class doesn't allow to disable errorOnInteract flag

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-2926: -------------------------------------------- Summary: CLI class doesn't allow to disable errorOnInteract flag Key: WFCORE-2926 URL: https://issues.jboss.org/browse/WFCORE-2926 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise Priority: Critical This flag has been introduced in 7.0. It is enabled by default, CLI class should have been updated to disable it by default. In addition a connect(CommandContextConfiguration config) API should be added to the CLI class to allow for full control on the CommandContext configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 June 2017