September 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9324) Driver-name parameter should not be required

by Michal Petrov (JIRA)

Michal Petrov created WFLY-9324: ----------------------------------- Summary: Driver-name parameter should not be required Key: WFLY-9324 URL: https://issues.jboss.org/browse/WFLY-9324 Project: WildFly Issue Type: Bug Components: Domain Management, JCA Affects Versions: 11.0.0.CR1 Reporter: Michal Petrov Assignee: Brian Stansberry Kind of a regression of AS7-4041. Currently the AttributeDefinition for {{driver-name}} is [marked as required|https://github.com/wildfly/wildfly/blob/5278ccf0cd392c2d82e96385...] which is unnecessary since the name is taken from the operation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9322) Elytron uses parallel streams in situations that do not require then

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-9322?page=com.atlassian.jira.plugin.... ] Jan Kalina updated WFLY-9322: ----------------------------- Labels: (was: eap72) > Elytron uses parallel streams in situations that do not require then > -------------------------------------------------------------------- > > Key: WFLY-9322 > URL: https://issues.jboss.org/browse/WFLY-9322 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Jan Kalina > Assignee: Jan Kalina > > This can have a big performance impact, as unless there are a large number of elements parallel streams are significantly more expensive than non parallel ones. I see it being used in: > org.jboss.as.ejb3.remote.AssociationImpl#registerClusterTopologyListener > org.wildfly.elytron.web.undertow.server.ElytronAccount#ElytronAccount > org.wildfly.elytron.web.undertow.server.ElytronHttpExchange#getRequestParameters > org.jboss.as.security.remoting.RemotingConnectionCredential#RemotingConnectionCredential > org.jboss.as.security.api.ConnectionSecurityContext#getConnectionPrincipals -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9323) TimerManagementTestCase fail with non-"en_US.UTF-8" locale settings

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFLY-9323?page=com.atlassian.jira.plugin.... ] Marek Kopecký moved JBEAP-13083 to WFLY-9323: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9323 (was: JBEAP-13083) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Test Suite (was: Test Suite) Affects Version/s: (was: 7.1.0.CR1) > TimerManagementTestCase fail with non-"en_US.UTF-8" locale settings > ------------------------------------------------------------------- > > Key: WFLY-9323 > URL: https://issues.jboss.org/browse/WFLY-9323 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Marek Kopecký > Assignee: Marek Kopecký > > *Description of problem:* > TimerManagementTestCase fail with non-"en_US.UTF-8" locale settings. These LANG are affected: > * de_DE.UTF-8 > * es_ES.UTF-8 > * fr_FR.UTF-8 > * ja_JP.UTF-8 > * pt_BR.UTF-8 > * zh_CN.UTF-8 > *How reproducible:* > Always > *Steps to Reproduce:* > # export LANG=de_DE.UTF-8 > # mvn install -B -fae -Dmaven.test.failure.ignore=true -llr -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 -Dts.basic -Djboss.dist=$JBOSS_DIST -Dtest=TimerManagementTestCase -DfailIfNoTests=false -DtestLogToFile=false > *Actual results:* > {noformat} > java.lang.AssertionError: "{\"outcome\" => \"failed\",\"failure-description\" => \"WFLYCTL0216: Recurso de administración '[ > (\\\"deployment\\\" => \\\"ejb-mgmt-timers.jar\\\"), > (\\\"subsystem\\\" => \\\"ejb3\\\"), > (\\\"stateless-session-bean\\\" => \\\"TimerBean\\\"), > (\\\"service\\\" => \\\"timer-service\\\"), > (\\\"timer\\\" => \\\"8355ac14-8067-436c-9e50-3fcf77eff7cf\\\") > ]' no encontrado\",\"rolled-back\" => true}" > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9322) Elytron uses parallel streams in situations that do not require then

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-9322?page=com.atlassian.jira.plugin.... ] Jan Kalina moved JBEAP-13078 to WFLY-9322: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9322 (was: JBEAP-13078) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) > Elytron uses parallel streams in situations that do not require then > -------------------------------------------------------------------- > > Key: WFLY-9322 > URL: https://issues.jboss.org/browse/WFLY-9322 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Jan Kalina > Assignee: Jan Kalina > Labels: eap72 > > This can have a big performance impact, as unless there are a large number of elements parallel streams are significantly more expensive than non parallel ones. I see it being used in: > org.jboss.as.ejb3.remote.AssociationImpl#registerClusterTopologyListener > org.wildfly.elytron.web.undertow.server.ElytronAccount#ElytronAccount > org.wildfly.elytron.web.undertow.server.ElytronHttpExchange#getRequestParameters > org.jboss.as.security.remoting.RemotingConnectionCredential#RemotingConnectionCredential > org.jboss.as.security.api.ConnectionSecurityContext#getConnectionPrincipals -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1361) Elytron uses parallel streams in situations that do not require then

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1361?page=com.atlassian.jira.plugin.s... ] Jan Kalina updated ELY-1361: ---------------------------- Labels: (was: eap72) > Elytron uses parallel streams in situations that do not require then > -------------------------------------------------------------------- > > Key: ELY-1361 > URL: https://issues.jboss.org/browse/ELY-1361 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Jan Kalina > Assignee: Jan Kalina > > This can have a big performance impact, as unless there are a large number of elements parallel streams are significantly more expensive than non parallel ones. I see it being used in: > org.jboss.as.ejb3.remote.AssociationImpl#registerClusterTopologyListener > org.wildfly.elytron.web.undertow.server.ElytronAccount#ElytronAccount > org.wildfly.elytron.web.undertow.server.ElytronHttpExchange#getRequestParameters > org.jboss.as.security.remoting.RemotingConnectionCredential#RemotingConnectionCredential > org.jboss.as.security.api.ConnectionSecurityContext#getConnectionPrincipals -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1361) Elytron uses parallel streams in situations that do not require then

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1361?page=com.atlassian.jira.plugin.s... ] Jan Kalina moved JBEAP-13075 to ELY-1361: ----------------------------------------- Project: WildFly Elytron (was: JBoss Enterprise Application Platform) Key: ELY-1361 (was: JBEAP-13075) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: (was: Security) > Elytron uses parallel streams in situations that do not require then > -------------------------------------------------------------------- > > Key: ELY-1361 > URL: https://issues.jboss.org/browse/ELY-1361 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Jan Kalina > Assignee: Jan Kalina > Labels: eap72 > > This can have a big performance impact, as unless there are a large number of elements parallel streams are significantly more expensive than non parallel ones. I see it being used in: > org.jboss.as.ejb3.remote.AssociationImpl#registerClusterTopologyListener > org.wildfly.elytron.web.undertow.server.ElytronAccount#ElytronAccount > org.wildfly.elytron.web.undertow.server.ElytronHttpExchange#getRequestParameters > org.jboss.as.security.remoting.RemotingConnectionCredential#RemotingConnectionCredential > org.jboss.as.security.api.ConnectionSecurityContext#getConnectionPrincipals -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3262) Log stacktrace when exception occures in static method

by Martin Stefanko (JIRA)

Martin Stefanko created WFCORE-3262: --------------------------------------- Summary: Log stacktrace when exception occures in static method Key: WFCORE-3262 URL: https://issues.jboss.org/browse/WFCORE-3262 Project: WildFly Core Issue Type: Bug Components: CLI Affects Versions: 3.0.1.Final Reporter: Martin Stefanko Assignee: Martin Stefanko Priority: Critical There is a bug JBEAP-12968. It was very hard to find out was is going on as stacktrace of exception was hidden. Even setting TRACE level in jboss-cli.properties does not reveal anything. {code} ./jboss-cli.bat -c "-Dwildfly.config.url=C:\wildfly-config.xml" java.lang.ExceptionInInitializerError: java.lang.NullPointerException {code} Please log full stacktrace into jboss-cli.log in such case. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1583) Enhance a CLI logging

by Martin Stefanko (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1583?page=com.atlassian.jira.plugi... ] Martin Stefanko reassigned WFCORE-1583: --------------------------------------- Assignee: Martin Stefanko (was: Jean-Francois Denise) > Enhance a CLI logging > --------------------- > > Key: WFCORE-1583 > URL: https://issues.jboss.org/browse/WFCORE-1583 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Reporter: Alexey Loubyansky > Assignee: Martin Stefanko > Priority: Minor > > We should improve a logging capabilities of CLI. CLI logging is disabled by default, but it can be enabled by altering the jboss-cli-logging.properties. > Here is my test scenario. > {noformat} > [pkremens@localhost bin]$ ./jboss-cli.sh -c > [standalone@localhost:9990 /] /system-property=foo:add(value=bar bar) > {"outcome" => "success"} > [standalone@localhost:9990 /] shutdown > {noformat} > Set CLI logger level to ALL (logger.org.jboss.as.cli.level=ALL) to see all logs produced by CLI > actual content of jboss-cli.log - only server response is logged > {noformat} > 13:45:48,041 DEBUG [org.jboss.as.cli.CommandContext] connecting to localhost:9990 as null > 13:46:04,033 INFO [org.jboss.as.cli.CommandContext] {"outcome" => "success"} > {noformat} > I can imagine content like following could be helpful for troubleshooting > {noformat} > ... > <TIME> <LEVEL> [org.jboss.as.cli.CommandContext] /system-property=foo:add(value=bar bar) > { > "address" => [("system-property" => "foo")], > "operation" => "add", > "value" => "barbar" > } > <TIME> <LEVEL> [org.jboss.as.cli.CommandContext] {"outcome" => "success"} > {noformat} > AFAICT the only possibility to get the actual CLI requests in raw form is to map the content of $HOME/.jboss-cli-history file with configuration history or audit log now. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2217) TOA doesn't ignore DATA_MESSAGE from non-members

by Pedro Ruivo (JIRA)

Pedro Ruivo created JGRP-2217: --------------------------------- Summary: TOA doesn't ignore DATA_MESSAGE from non-members Key: JGRP-2217 URL: https://issues.jboss.org/browse/JGRP-2217 Project: JGroups Issue Type: Bug Affects Versions: 4.0.6 Reporter: Pedro Ruivo Assignee: Bela Ban TOA accepts and handle DATA_MESSAGE from members that aren't in the view. In that case, the message stays in the queue, in the pending state, until a new view is installed and it is cleanup. This blocks the deliver queue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2217) TOA doesn't ignore DATA_MESSAGE from non-members

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/JGRP-2217?page=com.atlassian.jira.plugin.... ] Pedro Ruivo reassigned JGRP-2217: --------------------------------- Assignee: Pedro Ruivo (was: Bela Ban) > TOA doesn't ignore DATA_MESSAGE from non-members > ------------------------------------------------ > > Key: JGRP-2217 > URL: https://issues.jboss.org/browse/JGRP-2217 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.6 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > > TOA accepts and handle DATA_MESSAGE from members that aren't in the view. In that case, the message stays in the queue, in the pending state, until a new view is installed and it is cleanup. > This blocks the deliver queue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 September 2017