April 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-775) Performance degradation with objects with many fields and method in working memory.

by Federico Bertola (JIRA)

Federico Bertola created DROOLS-775: --------------------------------------- Summary: Performance degradation with objects with many fields and method in working memory. Key: DROOLS-775 URL: https://issues.jboss.org/browse/DROOLS-775 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 6.2.0.Final, 6.1.0.Final, 6.0.0.Final, 6.3.0.Final Environment: Ubuntu 14.10 x64, jdk 8 Reporter: Federico Bertola Assignee: Mario Fusco I experience some major performance degradation while migrating from drools 5.0.1 to 6.x. I'm inserting objects with many properties into the working memory and firing some very basic rules which will match against a very small subset of those properties. I expected that the older version of Drools, which uses pure reflection, to be somewhat slower that the newer, which uses some clever ASM optimization., but this is not the case. I've also noticed that if the required properties are scattered across multiple level of hierarchy, the performance issue will aggravate. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-574) Upgrade jboss-invocation with version that includes fix for WFLY-4316

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-574?page=com.atlassian.jira.plugin... ] David Lloyd resolved WFCORE-574. -------------------------------- Fix Version/s: 1.0.0.Beta6 (was: 1.0.0.CR1) Resolution: Done Guess I forgot to resolve this. > Upgrade jboss-invocation with version that includes fix for WFLY-4316 > --------------------------------------------------------------------- > > Key: WFCORE-574 > URL: https://issues.jboss.org/browse/WFCORE-574 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Reporter: Tomaz Cerar > Assignee: David Lloyd > Fix For: 1.0.0.Beta6 > > > Upgrade jboss-invocation with version that includes https://github.com/jbossas/jboss-invocation/pull/7 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-25) Windows PowerShell scripts in bin

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-25?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFCORE-25: ----------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > Windows PowerShell scripts in bin > --------------------------------- > > Key: WFCORE-25 > URL: https://issues.jboss.org/browse/WFCORE-25 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > Fix For: 1.0.0.CR1 > > > Add .psh scripts that match the functionality of our .sh scripts. Leave the .bat scripts in their current limited-functionality form for people still on XP, but use PowerShell as the recommended Windows scripting language. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-43) Clarify the meaning of the 'server-state' and 'host-state' attributes

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-43?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFCORE-43: ----------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > Clarify the meaning of the 'server-state' and 'host-state' attributes > --------------------------------------------------------------------- > > Key: WFCORE-43 > URL: https://issues.jboss.org/browse/WFCORE-43 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: luck3y > Fix For: 1.0.0.CR1 > > > This JIRA is to implement what I described in the dev list discussion around the various states a server can be in for graceful shutdown (http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002360.html) > "I do think these are orthogonal and should not be combined. > The existing attribute is fundamentally about how the state of the > runtime services relates to the persistent configuration. > STARTING == out of sync due to still getting in sync during start > RUNNING == in sync > RELOAD_REQUIRED = out of sync, needs a reload to get in sync > RESTART_REQUIRED = out of sync, needs a full process restart to get in sync > There are two problems though with the existing attribute that exposes this: > 1) It's named "server-state" on a server and "host-state" on a Host > Controller. Really crappy name; way too broad. > That's fixable by creating a new attribute and making the old one an > alias for compatibility purposes. > 2) The RUNNING state is really poorly named. > The could perhaps be fixed by coming up with a new name and translating > it back to "RUNNING" in the handlers for the legacy "server-state" and > "host-state" attributes." -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-54) Add Keycloak authentication/authorization to http management endpoint

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-54?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFCORE-54: ----------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > Add Keycloak authentication/authorization to http management endpoint > --------------------------------------------------------------------- > > Key: WFCORE-54 > URL: https://issues.jboss.org/browse/WFCORE-54 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Affects Versions: 1.0.0.Alpha4 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: 1.0.0.CR1 > > > This is here to track the core changes needed for WFLY-3591. See that jira for details. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-91) Review use of Locale in toLowerCase() calls

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-91?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFCORE-91: ----------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > Review use of Locale in toLowerCase() calls > ------------------------------------------- > > Key: WFCORE-91 > URL: https://issues.jboss.org/browse/WFCORE-91 > Project: WildFly Core > Issue Type: Task > Components: CLI, Domain Management > Reporter: Brian Stansberry > Fix For: 1.0.0.CR1 > > > There are places where we are converting strings to lower case without specifying Locale.ENGLISH. Some of these may be fine, but some are not and they should all be reviewed: > {code} > $ git grep "toLowerCase()" > cli/src/main/java/org/jboss/as/cli/impl/CommandContextImpl.java: CommandHandler handler = cmdRegistry.getCommandHandler(cmdName.toLowerCase()); > cli/src/main/java/org/jboss/as/cli/impl/CommandContextImpl.java: CommandHandler handler = cmdRegistry.getCommandHandler(cmdName.toLowerCase()); > controller/src/main/java/org/jboss/as/controller/operations/global/ReadResourceDescriptionHandler.java: final AccessControl value = localName != null ? MAP.get(local > core-model-test/tests/src/test/java/org/jboss/as/core/model/test/access/RoleMappingTestCase.java: return super.toString().toLowerCase(); > core-model-test/tests/src/test/java/org/jboss/as/core/model/test/access/RoleMappingTestCase.java: return super.toString().toLowerCase(); > core-model-test/tests/src/test/java/org/jboss/as/core/model/test/standalone/root/StandaloneRootResourceTestCase.java: String hostName = NetworkUtils.canonize(InetAddress > domain-management/src/main/java/org/jboss/as/domain/management/security/adduser/ConfirmationChoice.java: String temp = response.toLowerCase(); // We now need to matc > domain-management/src/test/java/org/jboss/as/domain/management/security/auditlog/AbstractAuditLogHandlerTestCase.java: PathElement.pathElement(PROTOCOL, transpor > host-controller/src/main/java/org/jboss/as/host/controller/DirectoryGrouping.java: final DirectoryGrouping directoryGrouping = localName != null ? MAP.get(localName.toLo > host-controller/src/main/java/org/jboss/as/host/controller/HostControllerEnvironment.java: qualifiedHostName = qualifiedHostName.trim().toLowerCase(); > host-controller/src/main/java/org/jboss/as/host/controller/discovery/S3Util.java: String lk=hashKey.toLowerCase(); > server/src/main/java/org/jboss/as/server/ServerEnvironment.java: qualifiedHostName = qualifiedHostName.trim().toLowerCase(); > testsuite-core/domain/src/test/java/org/jboss/as/test/integration/domain/rbac/RbacSoakTest.java: super("TestClient-" + id + " (" + type.toString().toLowerCase() + " > testsuite-core/domain/src/test/java/org/jboss/as/test/integration/domain/rbac/RbacSoakTest.java: this.description = "TestClient-" + id + " (" + type.toString().toLow > testsuite-core/shared/src/main/java/org/jboss/as/test/integration/management/interfaces/JmxInterfaceStringUtils.java: return string.replaceAll(regex, replacement).toLowe > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-60) Capabilities and requirements in a managed process

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-60?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFCORE-60: ----------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > Capabilities and requirements in a managed process > -------------------------------------------------- > > Key: WFCORE-60 > URL: https://issues.jboss.org/browse/WFCORE-60 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 1.0.0.CR1 > > > Implement the aspects discussed under the "Runtime" section of https://community.jboss.org/docs/DOC-52712 > Add an API to the OperationContext for handlers to publish capabilities and for other handlers to register a requirement for those capabilities and to access the API object associated with the capability. > The registry of capabilities and requirements should be maintained with a semantic equivalent to the resource tree. The registry is copied-on-write, making the copy invisible to concurrently executing operations, and then the copy is published on commit of the operation that modified it. If the operation does not commit, the copy is discarded, so handlers have no need to revert changes they make to the registry. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-109) Update syslog handler attributes

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-109?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-109: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > Update syslog handler attributes > -------------------------------- > > Key: WFCORE-109 > URL: https://issues.jboss.org/browse/WFCORE-109 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > Fix For: 1.0.0.CR1 > > > The syslog handler does not currently expose the formatter for formatting messages. There will also be changes in a future logmanager release for TCP support and various other properties based on the new TCP support. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-129) Overlay does not work for subunits in exploded deployments.

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-129?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-129: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > Overlay does not work for subunits in exploded deployments. > ----------------------------------------------------------- > > Key: WFCORE-129 > URL: https://issues.jboss.org/browse/WFCORE-129 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 1.0.0.Alpha8 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 1.0.0.CR1 > > > If deployment is exploded and has subdeployments overlay wont work on files contained in said subdeployments. > Reproducers: https://github.com/baranowb/wildfly/tree/WFCORE-83-TESTS -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-114) Get RuntimeVaultReader into WildFly Core

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-114?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFCORE-114: ------------------------------ Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta6) > Get RuntimeVaultReader into WildFly Core > ---------------------------------------- > > Key: WFCORE-114 > URL: https://issues.jboss.org/browse/WFCORE-114 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha8 > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > Priority: Blocker > Fix For: 1.0.0.CR1 > > > The only real implementation of AbstractVaultReader isn't in wildfly-core; it's in the wildfly-full security subsystem module. > This means WildFly Core currently doesn't really support vault expressions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 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 April 2015