June 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4838) Add smoke test for cloning profiles in CLI

by Marek Kopecký (JIRA)

Marek Kopecký created WFLY-4838: ----------------------------------- Summary: Add smoke test for cloning profiles in CLI Key: WFLY-4838 URL: https://issues.jboss.org/browse/WFLY-4838 Project: WildFly Issue Type: Task Components: Test Suite Reporter: Marek Kopecký Assignee: Marek Kopecký https://issues.jboss.org/browse/EAP7-35 provides profile cloning ability (runtime (CLI)) to create new profiles based on existing JBoss profiles (web, full, web-ha, full-ha). This test serves as basic smoke tests to be run within the testsuite. CloneProfileTestCase: * clone default, full, ha, full-ha profiles via CLI * check results -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-751) Different threads accessing LeftTuple fields that reference LeftTupleSet

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-751?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-751: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1218291|https://bugzilla.redhat.com/show_bug.cgi?id=1218291] from ASSIGNED to MODIFIED > Different threads accessing LeftTuple fields that reference LeftTupleSet > ------------------------------------------------------------------------ > > Key: DROOLS-751 > URL: https://issues.jboss.org/browse/DROOLS-751 > Project: Drools > Issue Type: Bug > Affects Versions: 6.0.0.Final, 6.1.0.Final, 6.2.0.Final > Reporter: Tibor Zimányi > Assignee: Mario Fusco > Priority: Critical > Fix For: 6.3.0.Beta1 > > > In class LeftTupleSetsImpl there are missing nullchecks in some methods that contains handling LeftTuple instances. I.e. in method removeInsert there is LeftTuple variable previous that is not nullchecked. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-894) Improve SimpleRoleGroup Scalability to Large Numbers of Roles

by Philippe Marschall (JIRA)

[ https://issues.jboss.org/browse/SECURITY-894?page=com.atlassian.jira.plug... ] Philippe Marschall resolved SECURITY-894. ----------------------------------------- Resolution: Done pull request merged > Improve SimpleRoleGroup Scalability to Large Numbers of Roles > ------------------------------------------------------------- > > Key: SECURITY-894 > URL: https://issues.jboss.org/browse/SECURITY-894 > Project: PicketBox > Issue Type: Patch > Components: Identity > Reporter: Philippe Marschall > Assignee: Stefan Guilhen > Fix For: PicketBox_4_9_3.Beta1 > > Attachments: attachment-0001.png > > > During load testing we found out that SimpleRoleGroup does not scale well to large numbers of roles (200 in our case). The reason for this is that it uses {{ArrayList#contains}} with scales linearly with the size of the collection. Since the method is called in a loop the scalability is actually quadratic. > See the following [mailing list discussion|http://lists.jboss.org/pipermail/wildfly-dev/2015-June/004033....] and the attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-894) Improve SimpleRoleGroup Scalability to Large Numbers of Roles

by Philippe Marschall (JIRA)

[ https://issues.jboss.org/browse/SECURITY-894?page=com.atlassian.jira.plug... ] Philippe Marschall updated SECURITY-894: ---------------------------------------- Fix Version/s: PicketBox_4_9_3.Beta1 > Improve SimpleRoleGroup Scalability to Large Numbers of Roles > ------------------------------------------------------------- > > Key: SECURITY-894 > URL: https://issues.jboss.org/browse/SECURITY-894 > Project: PicketBox > Issue Type: Patch > Components: Identity > Reporter: Philippe Marschall > Assignee: Stefan Guilhen > Fix For: PicketBox_4_9_3.Beta1 > > Attachments: attachment-0001.png > > > During load testing we found out that SimpleRoleGroup does not scale well to large numbers of roles (200 in our case). The reason for this is that it uses {{ArrayList#contains}} with scales linearly with the size of the collection. Since the method is called in a loop the scalability is actually quadratic. > See the following [mailing list discussion|http://lists.jboss.org/pipermail/wildfly-dev/2015-June/004033....] and the attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4801) When expression is used in jndi name attribute of datasource then test-connection-in-pool operation is not working

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4801?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4801: ----------------------------------------------- Chao Wang <chaowan(a)redhat.com> changed the Status of [bug 1232781|https://bugzilla.redhat.com/show_bug.cgi?id=1232781] from ASSIGNED to POST > When expression is used in jndi name attribute of datasource then test-connection-in-pool operation is not working > ------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-4801 > URL: https://issues.jboss.org/browse/WFLY-4801 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 10.0.0.Alpha3 > Reporter: Chao Wang > Assignee: Chao Wang > Fix For: 9.0.0.Final, 10.0.0.Alpha4 > > > {noformat} > Description of problem: > ======================== > - Expression is added in the datasource JNDI name attribute as below: > ----- > <datasource jndi-name="${ds}" pool-name="ExampleDS" enabled="true" use-java-context="true"> > ----- > - Value for the expression is passed to the JBoss server during the JBoss startup as below: > ----- > ./standalone.sh -Dds=java:jboss/datasources/ExampleDS > ----- > - In the server.log file below is the information regarding the datasource. > ----- > INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [${ds}] > ----- > - Test the datasource using the below command and here is the result: > ---- > [standalone@localhost:9999 /] /subsystem=datasources/data-source=ExampleDS:test-connection-in-pool() > { > "outcome" => "failed", > "failure-description" => "JBAS010440: failed to invoke operation: JBAS010442: failed to match pool. Check JndiName: java:/${ds}", > "rolled-back" => true > } > ---- > - Here is the information regarding the JNDI name attribute: > ---- > [standalone@localhost:9999 /] /subsystem=datasources/data-source=ExampleDS:read-resource-description(recursive=true) > { > "outcome" => "success", > "result" => { > : > "jndi-name" => { > "type" => STRING, > "description" => "Specifies the JNDI name for the datasource", > "expressions-allowed" => true, > "nillable" => false, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "no-services" > }, > : > } > ----- > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4695) Remove infinispan-query module and its dependencies

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/WFLY-4695?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on WFLY-4695: --------------------------------------- [~pferraro] What do you prefer, should I take your branch as a starting point for a new pull request? > Remove infinispan-query module and its dependencies > --------------------------------------------------- > > Key: WFLY-4695 > URL: https://issues.jboss.org/browse/WFLY-4695 > Project: WildFly > Issue Type: Task > Components: Clustering > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > > We generally expect people to use the version bundled by the Infinispan project, and there are no strong reasons to include this in WildFly. > Also it makes it much harder to upgrade components such as Hibernate and Infinispan as this components introduces strong coupling on several of these components, essentially mandating that these are all upgraded in lock step. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3805) JGroupsBroadcastGroupConfiguration Serialization Problem

by Ravi Soni (JIRA)

[ https://issues.jboss.org/browse/WFLY-3805?page=com.atlassian.jira.plugin.... ] Ravi Soni commented on WFLY-3805: --------------------------------- I am stuck on this issue in AWS deployment using S3_ping, is there workout alternative to this issue. until this get fix/PR get marge to master. > JGroupsBroadcastGroupConfiguration Serialization Problem > -------------------------------------------------------- > > Key: WFLY-3805 > URL: https://issues.jboss.org/browse/WFLY-3805 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 8.1.0.Final > Reporter: Yong Hao Gao > Assignee: Yong Hao Gao > Fix For: 9.0.0.Final > > > When configuring JMS connection factories using jgroups discovery group, the client will get serialization exceptions because we pass a JChannel which is not serializable. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4806) Do not deploy artifacts until subsystem MBeans are registered

by Brian Riehman (JIRA)

[ https://issues.jboss.org/browse/WFLY-4806?page=com.atlassian.jira.plugin.... ] Brian Riehman closed WFLY-4806. ------------------------------- Resolution: Won't Fix Thank you for the very helpful comments, [~kabirkhan]. Closing since this seems to be working as intended. > Do not deploy artifacts until subsystem MBeans are registered > ------------------------------------------------------------- > > Key: WFLY-4806 > URL: https://issues.jboss.org/browse/WFLY-4806 > Project: WildFly > Issue Type: Feature Request > Components: JMX, Server > Reporter: Brian Riehman > Assignee: Kabir Khan > Priority: Minor > > When the server starts up and begins to deploy artifacts, the subsystem MBeans are not yet available. Our application has implemented a {{ServletContextListener}} and is attempting to lookup attributes from a DataSource MBean (e.g. {{jboss.as:subsystem=datasources,xa-data-source=DefaultDS}}). This MBean is not available at the time the listener is called when the server is first starting up. Some time after the deployment has run, the MBean is available and can be queried. > If the deployment is added after the server has already successfully started, the MBean can be queried successfully. I would imagine the deploy operation is done in parallel with the MBean registration, but I cannot find where the datasource subsystem MBean registration occurs. > It is odd that the datasource exists but the datasources subsystem MBean is not yet available for querying. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-220) Add a RegExSplittingNameRewriter

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-220?page=com.atlassian.jira.plugin.sy... ] David Lloyd commented on ELY-220: --------------------------------- The regex form was intended to allow this: {code} NameRewriter extractingRewriter = new RegexNameRewriter(Pattern.compile("([a-z0-9])(a)mycompany\\.com"), "$1", true); {code} If you want to put a literal $ in the target, you can escape it, or do this: {code} NameRewriter transformingRewriter = new RegexNameRewriter(Pattern.compile("@"), Matcher.quoteReplacement("$"), true); {code} > Add a RegExSplittingNameRewriter > --------------------------------- > > Key: ELY-220 > URL: https://issues.jboss.org/browse/ELY-220 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Utils > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha2 > > > The existing implementations allow for replacing a portion of a name based on a regular expression or validating a name based on a regular expression - however we do not have a form that allows you to easily extract a portion of a name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-220) Add a RegExSplittingNameRewriter

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-220: ------------------------------------ Summary: Add a RegExSplittingNameRewriter Key: ELY-220 URL: https://issues.jboss.org/browse/ELY-220 Project: WildFly Elytron Issue Type: Feature Request Components: Utils Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.0.Alpha2 The existing implementations allow for replacing a portion of a name based on a regular expression or validating a name based on a regular expression - however we do not have a form that allows you to easily extract a portion of a name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 June 2015