April 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-424) .jar's on "current runtime classpath"

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-424?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-424: ------------------------------------ Fix Version/s: (was: 1.0.0.CR1) > .jar's on "current runtime classpath" > ------------------------------------- > > Key: WFCORE-424 > URL: https://issues.jboss.org/browse/WFCORE-424 > Project: WildFly Core > Issue Type: Feature Request > Components: Modules > Reporter: Ondrej Zizka > Assignee: David Lloyd > > (Based on JBDS use case - see EAP6-1) > In certain scenarios, JBDS needs to know the classpath. (Compilation of non-maven project, against a remote server, ...(?) ) > The classpath would be: > * for the deployment after deployed > * for a generic deployment if it was deployed right now - what would WildFly use? > * for the deployment before deployed - sounds a bit advanced but technically possible > We (David, Stuart, Jason, Max, Ondra) have discussed this on EAP F2F 2014. > The output was that we don't need exact classpath / list of jars which would probably end up being almost all modules; rather we need the direct deps. As someone said - "just to get rid of the red lines in the IDE". > The non-maven compilation use case is that the user has a server in a directory, and the jars to build against should all be in there. So the IDE should be able to ask WildFly for a list of .jar's to build the application against, and just use that instead of forcing the user to gather them manually. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

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

by Federico Bertola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-775?page=com.atlassian.jira.plugin... ] Federico Bertola edited comment on DROOLS-775 at 4/28/15 11:13 AM: ------------------------------------------------------------------- After further investigation (profiling) I found that if I stub the {{ClassObjectTypeConf#checkPropertyListenerSupport}} method (which uses reflection internally) I experience a noticeable performance increase. was (Author: fbertola): After further investigation (profiling) I found that if I stub the {{ClassObjectTypeConf#checkPropertyListenerSupport}} method (which uses reflection internally) I experience a noticeable performance increase. The field {{supportsPropertyListeners}} is not used anywhere else. There's something I'm missing? > Performance degradation with objects with many properties 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.0.0.Final, 6.1.0.Final, 6.2.0.Final > Environment: Ubuntu 14.10 x64, jdk 8 > Reporter: Federico Bertola > Assignee: Mario Fusco > Labels: regression > Attachments: drools-test.zip > > > 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 than 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. > For example, after 100k iterations: > droosl 5.0.1 > -- Meters ---------------------------------------------------------------------- > org.acme.test.drools5.DroolsPerformance.analized > count = 100000 > mean rate = 549.27 events/second > ... > drools 6.2.0.Final > -- Meters ---------------------------------------------------------------------- > org.acme.test.drools6.DroolsPerformance.analized > count = 100000 > mean rate = 198.58 events/second > ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-313) DefaultOperationDescriptionProvider uses incorrect call to create reply parameter description

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-313?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-313: ------------------------------------ Fix Version/s: 2.0.0.Beta1 (was: 1.0.0.CR1) > DefaultOperationDescriptionProvider uses incorrect call to create reply parameter description > --------------------------------------------------------------------------------------------- > > Key: WFCORE-313 > URL: https://issues.jboss.org/browse/WFCORE-313 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 2.0.0.Beta1 > > > When creating reply descriptions, DefaultOperationDescriptionProvider calls attributeDescriptionResolver.getOperationParameterDescription instead of attributeDescriptionResolver.getOperationReplyValueTypeDescription. > A fix needs to not break compatibility for existing users of the incorrect behavior; i.e. call the correct method in a try block, catch any MissingResourceException, and if caught call the incorrect method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-43?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFCORE-43: ----------------------------------- Fix Version/s: 2.0.0.Beta1 (was: 1.0.0.CR1) > 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: 2.0.0.Beta1 > > > 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

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-60?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFCORE-60: ----------------------------------- Fix Version/s: 2.0.0.Beta1 (was: 1.0.0.CR1) > 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: 2.0.0.Beta1 > > > 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

1
0
0 / 0

[JBoss JIRA] (WFCORE-170) Create a shared ScheduledExecutorService

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-170?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-170: ------------------------------------ Fix Version/s: 2.0.0.Alpha1 (was: 1.0.0.CR1) > Create a shared ScheduledExecutorService > ---------------------------------------- > > Key: WFCORE-170 > URL: https://issues.jboss.org/browse/WFCORE-170 > Project: WildFly Core > Issue Type: Feature Request > Components: Server > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 2.0.0.Alpha1 > > > There are number of ScheduledExecutorService instances being created around wf-core. Create a single service and inject it. > This will reduce resource usage by creating fewer threads, and will reduce the risk of code mistakes around shutting down the various executors, > I see these used in: > LdapCacheService > RemoteDomainConnectionService > DeploymentMountProvider > DeploymentScannerService > plus the operation response attachment stuff I'm doing will need one. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-91?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFCORE-91: ----------------------------------- Fix Version/s: 2.0.0.Alpha1 (was: 1.0.0.CR1) > 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: 2.0.0.Alpha1 > > > 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

1
0
0 / 0

[JBoss JIRA] (WFCORE-230) Failure by ProcessController to launch a server vm is not logged

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-230?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFCORE-230: ----------------------------------------- [~ehugonnet] Will you be able to do anything on this in the next couple days? If not, please reschedule to 10.0.0.Alpha1. > Failure by ProcessController to launch a server vm is not logged > ---------------------------------------------------------------- > > Key: WFCORE-230 > URL: https://issues.jboss.org/browse/WFCORE-230 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha11 > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > Fix For: 1.0.0.CR1 > > > In a domain configuration, if a server is associated with an incorrectly configurated jvm java-home (e.g. domain.xml -> server-groups -> jvm), it will fail silently (no error shown in logs). For example: > ``` > <server-group name="mySrvrGrp" profile="full"> > <jvm name="my-default" java-home="/usr/java/wrongPath"> > <heap size="1024m" max-size="4096m"/> > <permgen size="256m" max-size="256m"/> > <stack size="256k"/> > ``` -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-185) Api returns internal server error instead of not found for non-existing path

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-185?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFCORE-185: ----------------------------------------- (Status note) https://github.com/bstansberry/wildfly-core/tree/WFCORE-185 is a now quite out of date branch with work on this. The big implementation issue here is properly propagating status codes back to the master and on to the user in a managed domain. That branch was starting to feel hacky, and I had other critical priorities, so I moved off of it. > Api returns internal server error instead of not found for non-existing path > ---------------------------------------------------------------------------- > > Key: WFCORE-185 > URL: https://issues.jboss.org/browse/WFCORE-185 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Rupp > Assignee: Brian Stansberry > Labels: rhq > Fix For: 2.0.0.Beta1 > > > When I try to e.g. /subsystem=foo:read-resource the api returns a 500 internal server error. > In http-land, the return code for "not found" is normally 404. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-185) Api returns internal server error instead of not found for non-existing path

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-185?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-185: ------------------------------------ Fix Version/s: 2.0.0.Beta1 (was: 1.0.0.CR1) > Api returns internal server error instead of not found for non-existing path > ---------------------------------------------------------------------------- > > Key: WFCORE-185 > URL: https://issues.jboss.org/browse/WFCORE-185 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Rupp > Assignee: Brian Stansberry > Labels: rhq > Fix For: 2.0.0.Beta1 > > > When I try to e.g. /subsystem=foo:read-resource the api returns a 500 internal server error. > In http-land, the return code for "not found" is normally 404. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

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