November 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AG-44) Fix loading the AgroalDataSource implementation in modular enviroments

by Luis Barreiro (JIRA)

Luis Barreiro created AG-44: ------------------------------- Summary: Fix loading the AgroalDataSource implementation in modular enviroments Key: AG-44 URL: https://issues.jboss.org/browse/AG-44 Project: Agroal Issue Type: Bug Components: api Affects Versions: 0.3 Reporter: Luis Barreiro Assignee: Luis Barreiro Fix For: 0.4 This is caused by the ServiceLoader using the Thread context class loader. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3438) leading whitespace are not removed from input string

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3438?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-3438: ----------------------------------------- Summary: leading whitespace are not removed from input string (was: trailing whitespace are not removed from input string) > leading whitespace are not removed from input string > ---------------------------------------------------- > > Key: WFCORE-3438 > URL: https://issues.jboss.org/browse/WFCORE-3438 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > The string received by aesh used to be trimmed prior to be passed down to the CommandContext, that has been forgotten when re-implementing the console with aesh-readline. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3438) trailing whitespace are not removed from input string

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-3438: -------------------------------------------- Summary: trailing whitespace are not removed from input string Key: WFCORE-3438 URL: https://issues.jboss.org/browse/WFCORE-3438 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise The string received by aesh used to be trimmed prior to be passed down to the CommandContext, that has been forgotten when re-implementing the console with aesh-readline. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3415) Cut the time to execute MBeanServerConnection.getMBeanCount()

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3415?page=com.atlassian.jira.plugi... ] Brian Stansberry reopened WFCORE-3415: -------------------------------------- Reopening as this fix resulted in a TCK problem. > Cut the time to execute MBeanServerConnection.getMBeanCount() > ------------------------------------------------------------- > > Key: WFCORE-3415 > URL: https://issues.jboss.org/browse/WFCORE-3415 > Project: WildFly Core > Issue Type: Enhancement > Components: JMX > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 4.0.0.Alpha3 > > > The time it takes to count the mbeans associated with the jboss.as and jboss.as.expr domains is way too high, over a full second when the WildFly full standalone-full-ha.xml config is used, and potentially much higher if complex deployments are installed. See WFLY-9408. > This enhancement proposes doing two things to mitigate this: > 1) There is no point doing a full count of both jboss.as and jboss.as.expr as they are just 2 views on the same underlying resources. If both are present, count one and double it. > 2) Do not use RBAC to exclude from the count mbeans the user won't be allowed to see. They exist whether the user can see them or not. Simply count the resources. > Looking at the JMX specification (https://docs.oracle.com/javase/8/docs/technotes/guides/jmx/JMX_1_4_specif...) I see nothing directly on the topic of the effect of any security checks on the result of getMBeanCount(). Section 12.1.2.4 "Permission Checking for Queries" clearly states that permission checks should remove mbeans that should not be visible according to the permission scheme from the query result, so definitely queries returning a subset of the entire mbean universe is contemplated. Now, that section is about security manager permissions, not our RBAC scheme, but it's the most on topic thing I see. > Doing these two things I can get the cost of a getMBeanCount() from around 1 second to under 10 ms. (Note the 1 sec figure is the first call; once the JVM optimizes the existing code it drops to under 500ms.) > The enhancement will also make it possible for custom Resource implementations to optimize things. For example a resource that represents a possibly large number of dynamic children could ask the system behind those children for a child count, rather that iterating over the children. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3437) CLI can't be started on Solaris

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3437?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3437: ------------------------------------- Priority: Blocker (was: Critical) > CLI can't be started on Solaris > ------------------------------- > > Key: WFCORE-3437 > URL: https://issues.jboss.org/browse/WFCORE-3437 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Marek Kopecký > Assignee: Jean-Francois Denise > Priority: Blocker > > CLI (WildFly master) can't be started on Solaris: > {noformat} > [hudson@dev34-02 bin]$ ./jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > java.io.IOException: Error executing 'stty size': unknown mode: size > : Error executing 'stty size': unknown mode: size > [hudson@dev34-02 bin]$ > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9572) Speed-up clustering testsuite

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9572?page=com.atlassian.jira.plugin.... ] Radoslav Husar reopened WFLY-9572: ---------------------------------- > Speed-up clustering testsuite > ----------------------------- > > Key: WFLY-9572 > URL: https://issues.jboss.org/browse/WFLY-9572 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > For starters, move the testsuite away from using XSLT and just rely on the CLI scripts. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9583) Drop org.jboss.as.test.clustering.single.jdbcstore.TransactionalJdbcStoreTestCase

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9583?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9583: --------------------------------- Description: While the behaviour verification belongs to Infinspan rather than the AS, the dependent Jira is rejected ISPN-604. (was: While the behaviour verification belongs to Infinspan rather than the AS, the dependent Jira is rejected https://issues.jboss.org/browse/ISPN-604.) > Drop org.jboss.as.test.clustering.single.jdbcstore.TransactionalJdbcStoreTestCase > --------------------------------------------------------------------------------- > > Key: WFLY-9583 > URL: https://issues.jboss.org/browse/WFLY-9583 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 12.0.0.Alpha1 > > > While the behaviour verification belongs to Infinspan rather than the AS, the dependent Jira is rejected ISPN-604. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9583) Drop org.jboss.as.test.clustering.single.jdbcstore.TransactionalJdbcStoreTestCase

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9583?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9583: --------------------------------- Affects Version/s: 11.0.0.Final > Drop org.jboss.as.test.clustering.single.jdbcstore.TransactionalJdbcStoreTestCase > --------------------------------------------------------------------------------- > > Key: WFLY-9583 > URL: https://issues.jboss.org/browse/WFLY-9583 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 12.0.0.Alpha1 > > > While the behaviour verification belongs to Infinspan rather than the AS, the dependent Jira is rejected https://issues.jboss.org/browse/ISPN-604. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9574) Distribution files does not have POSIX permissions perfectly set

by Romain Pelisse (JIRA)

[ https://issues.jboss.org/browse/WFLY-9574?page=com.atlassian.jira.plugin.... ] Romain Pelisse updated WFLY-9574: --------------------------------- Description: The server provisioning copy (and extract) files in order to assemble the distribution based the information of the feature-pack. While doing so on a POSIX system, it keeps the permissions of the original files, which are not always optimum (see JBEAP-12374). Specifically, .properties and .jar files are associated with the mask rw-rw-r-- giving access to it to any other and allowing group member to modify the file ; On a "regular" Maven project, all of those changes could be specified in the assembly.xml, however in Wildfly cases, this is not really option because the provisioning-maven-plugin and feature-pack-build-maven-plugin are manipulating the content of the archive being built. Also, using assembly.xml would mean edit and update the 4 or 5 different assembly.xml in the project directory tree. I plan thus to propose a fix for wildfly-build-tools to address all those (small) problems. was: The server provisioning copy (and extract) files in order to assemble the distribution based the information of the feature-pack. While doing so on a POSIX system, it keeps the permissions of the original files, which are not always optimum (see JBEAP-12374). For instance: * .properties and .jar files are associated with the mask rw-rw-r-- giving access to it to any other and allowing group member to modify the file ; * some directories like domain/tmp/auth have to restrictive mask like rwx------ that needs to be turned into rwxrwxr-x and other, likes domain have again a too permissive mask rwxrwxr-x (should be rwxr-xr-x). On a "regular" Maven project, all of those changes could be specified in the assembly.xml, however in Wildfly cases, this is not really option because the provisioning-maven-plugin and feature-pack-build-maven-plugin are manipulating the content of the archive being built. Also, using assembly.xml would mean edit and update the 4 or 5 different assembly.xml in the project directory tree. I plan thus to propose a fix for wildfly-build-tools to address all those (small) problems. > Distribution files does not have POSIX permissions perfectly set > ---------------------------------------------------------------- > > Key: WFLY-9574 > URL: https://issues.jboss.org/browse/WFLY-9574 > Project: WildFly > Issue Type: Enhancement > Components: Build System > Affects Versions: 11.0.0.Final > Reporter: Romain Pelisse > Assignee: Romain Pelisse > Priority: Minor > > The server provisioning copy (and extract) files in order to assemble the distribution based the information of the feature-pack. > While doing so on a POSIX system, it keeps the permissions of the original files, which are not always optimum (see JBEAP-12374). Specifically, .properties and .jar files are associated with the mask rw-rw-r-- giving access to it to any other and allowing group member to modify the file ; > On a "regular" Maven project, all of those changes could be specified in the assembly.xml, however in Wildfly cases, this is not really option because the provisioning-maven-plugin and feature-pack-build-maven-plugin are manipulating the content of the archive being built. Also, using assembly.xml would mean edit and update the 4 or 5 different assembly.xml in the project directory tree. > I plan thus to propose a fix for wildfly-build-tools to address all those (small) problems. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9568) Test case for WFCORE-1392 - Undeploy doesn't remove Data content if server is in --admin-only mode

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFLY-9568?page=com.atlassian.jira.plugin.... ] Tomas Hofman closed WFLY-9568. ------------------------------ Resolution: Won't Do Closing, test will be implemented in core. > Test case for WFCORE-1392 - Undeploy doesn't remove Data content if server is in --admin-only mode > --------------------------------------------------------------------------------------------------- > > Key: WFLY-9568 > URL: https://issues.jboss.org/browse/WFLY-9568 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Tomas Hofman > Assignee: Tomas Hofman > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 November 2017