May 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1503) Reading the logging subsystem resource can be slow if several log files exist

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1503?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-1503: --------------------------------------- Excellent thanks for the confirmation [~pvorb]! > Reading the logging subsystem resource can be slow if several log files exist > ----------------------------------------------------------------------------- > > Key: WFCORE-1503 > URL: https://issues.jboss.org/browse/WFCORE-1503 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Labels: 2.2 > Attachments: wildfly-logging-patch-02.jar > > > The logging subsystem uses a dynamic resource to list log files as resources. These are the files that are allowed to be read or downloaded and are attached to known file handlers. > When several file handlers are defined the file tree walker is invoked several times per {{read-resource-operation}}. This may be happening for each stage of an operation. Ideally we could either cache the file listing per-operation or only execute at the runtime stage. This may not be an option for dynamic resources however. > As a result of this poor performance the web console is very slow to load the logging subsystem configuration. This is not an issue with the web console. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1153) Version detection when adding drools runtime doesn't work

by Tomas David (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1153?page=com.atlassian.jira.plugi... ] Tomas David commented on DROOLS-1153: ------------------------------------- After discussion with [~bbrodt]: proposed solution is to take a version from the manifest file of a one drools runtime jar. This allows to automatically complete the version in drools preferences page. > Version detection when adding drools runtime doesn't work > --------------------------------------------------------- > > Key: DROOLS-1153 > URL: https://issues.jboss.org/browse/DROOLS-1153 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Environment: JBDS 9.1.0.GA > Drools plugin 6.4.1-Snapshot > Reporter: Tomas David > Assignee: Robert (Bob) Brodt > Priority: Minor > Labels: reported-by-qe > Attachments: add_drools_runtime_dialog.png > > > When you add a drools runtime, version is not automatically detected and "Version must be in the form major#.minor#.patch#" text is displayed. User has to specify a version manually instead of automatic detection from binaries. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-429) Incremental redeployment (single file update) over management API

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-429?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFCORE-429: ----------------------------------------- I've drafted a requirements doc for this: https://developer.jboss.org/docs/DOC-55497 I've also got a local prototype branch that does a small bit of this, which I'll link later this week once it gets polished a bit more. At that point it won't have much functionality particularly interesting to a user but it should have a lot of the needed underpinnings. > Incremental redeployment (single file update) over management API > ----------------------------------------------------------------- > > Key: WFCORE-429 > URL: https://issues.jboss.org/browse/WFCORE-429 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI, Domain Management > Reporter: Ondrej Zizka > Labels: deploy, deployment, incremental, redeployment > Fix For: 3.0.0.Beta1 > > > (Based on JBDS use case - see EAP6-1) > See also https://mojo.redhat.com/docs/DOC-934058 for notes > By incremental redeployment, we mean the situation when something is deployed, and after changes (in IDE e.g.), only that single file (.jsp, .xml, .class) would be re-deployed to the server, *over management API* - which is, you'd give it a stream and a path where it belongs in the deployment, and the operation would accept that file and put it to the right place in VFS, clear caches etc. > Use cases: > Big .war's, mainly on remote > Cloud deployments > Also, you loose sessions etc. > "JSP recompile on file update" - mgmt API operation - added in WildFly 8? > Not expected to work in domain mode. > Stuart said that session persistence is implemented in WFly 8, but not the incremental redeployment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-429) Incremental redeployment (single file update) over management API

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-429?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-429: ------------------------------------ Fix Version/s: 3.0.0.Beta1 > Incremental redeployment (single file update) over management API > ----------------------------------------------------------------- > > Key: WFCORE-429 > URL: https://issues.jboss.org/browse/WFCORE-429 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI, Domain Management > Reporter: Ondrej Zizka > Labels: deploy, deployment, incremental, redeployment > Fix For: 3.0.0.Beta1 > > > (Based on JBDS use case - see EAP6-1) > See also https://mojo.redhat.com/docs/DOC-934058 for notes > By incremental redeployment, we mean the situation when something is deployed, and after changes (in IDE e.g.), only that single file (.jsp, .xml, .class) would be re-deployed to the server, *over management API* - which is, you'd give it a stream and a path where it belongs in the deployment, and the operation would accept that file and put it to the right place in VFS, clear caches etc. > Use cases: > Big .war's, mainly on remote > Cloud deployments > Also, you loose sessions etc. > "JSP recompile on file update" - mgmt API operation - added in WildFly 8? > Not expected to work in domain mode. > Stuart said that session persistence is implemented in WFly 8, but not the incremental redeployment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-517) Utilities for the easy atomic manipulation of SSLSession values

by David Lloyd (JIRA)

David Lloyd created ELY-517: ------------------------------- Summary: Utilities for the easy atomic manipulation of SSLSession values Key: ELY-517 URL: https://issues.jboss.org/browse/ELY-517 Project: WildFly Elytron Issue Type: Feature Request Components: SSL Reporter: David Lloyd Assignee: David Lloyd Priority: Minor Fix For: 1.1.0.Beta6 SSLSession has poor support for atomic getting/setting of session values. Add some util methods which are atomic with respect to each other, and reasonably performant. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1154) Add drools runtime dialog doesn't support version naming of the product

by Tomas David (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1154?page=com.atlassian.jira.plugi... ] Tomas David commented on DROOLS-1154: ------------------------------------- After discussion with [~bbrodt], this issue will be fixed in 6.4.1 version of drools plugin. It should supports different versions of drools or brms naming. > Add drools runtime dialog doesn't support version naming of the product > ------------------------------------------------------------------------ > > Key: DROOLS-1154 > URL: https://issues.jboss.org/browse/DROOLS-1154 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Environment: JBDS 9.1.0.GA > Drools plugin 6.4.1-Snapshot > Reporter: Tomas David > Assignee: Robert (Bob) Brodt > Labels: reported-by-qe > Attachments: add_button.png > > > When you add a drools product runtime and you try to specify a version of runtime (for example "6.4.0.Final-redhat-2"), the Add button of Add Drools runtime dialog is not enabled so it is not possible to complete the runtime adding. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-974) Activation group doesn't work as expected

by Vitali Kviatkouski (JIRA)

[ https://issues.jboss.org/browse/DROOLS-974?page=com.atlassian.jira.plugin... ] Vitali Kviatkouski commented on DROOLS-974: ------------------------------------------- Any chance to get this fixed in Drools 6.x? > Activation group doesn't work as expected > ----------------------------------------- > > Key: DROOLS-974 > URL: https://issues.jboss.org/browse/DROOLS-974 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.Final, 6.3.0.Final > Environment: Mac OS X 10.8.3 > jdk 1.7.0_60 > Reporter: Hanbing Luo > Assignee: Mario Fusco > Fix For: 7.0.0.Final > > > In some rare cases activation group doesn't work as expected. For example, two rules with same ruleflow-group and activation-group but different salience are both get fired if reuse kie session. > Some investigation notes to help address. > 1) This issue never happen if use a new fresh kie session. > 2) I also tried to write a drools style unit test (testActivationGroupIssue in ExecutionFlowControlTest.java) but can't reproduce this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1152) New jBPM maven project can be created only with hello world process

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1152?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-1152: ------------------------------------- Please notice , that missing radio and check boxes will appear if wizard popup window is resized. > New jBPM maven project can be created only with hello world process > ------------------------------------------------------------------- > > Key: DROOLS-1152 > URL: https://issues.jboss.org/browse/DROOLS-1152 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 6.4.0.Final > Environment: * JBDS 9.1.0.GA > * drools-jbpm plugin 6.4.1.201604291802 > Reporter: Jozef Marko > Assignee: Robert (Bob) Brodt > > In project created via [1] can be created only hello world sample process while in project created via [2] can be created also more complex sample process and optionally JUnit test. > [1] > File -> New -> Other -> jBPM -> jBPM project -> project with example files -> build project using maven > [2] > File -> New -> Other -> jBPM -> jBPM project -> project with example files -> build project using Java and jBPM classes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1154) Add drools runtime dialog doesn't support version naming of the product

by Tomas David (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1154?page=com.atlassian.jira.plugi... ] Tomas David updated DROOLS-1154: -------------------------------- Labels: reported-by-qe (was: ) > Add drools runtime dialog doesn't support version naming of the product > ------------------------------------------------------------------------ > > Key: DROOLS-1154 > URL: https://issues.jboss.org/browse/DROOLS-1154 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Environment: JBDS 9.1.0.GA > Drools plugin 6.4.1-Snapshot > Reporter: Tomas David > Assignee: Robert (Bob) Brodt > Labels: reported-by-qe > Attachments: add_button.png > > > When you add a drools product runtime and you try to specify a version of runtime (for example "6.4.0.Final-redhat-2"), the Add button of Add Drools runtime dialog is not enabled so it is not possible to complete the runtime adding. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1151) Missing libraries in new jBPM project

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1151?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-1151: -------------------------------- Environment: * JBDS 9.1.0.GA * drools-jbpm plugin 6.4.1.201604291802 was:JBDS 9.1.0.GA + drools-jbpm plugin from http://downloads.jboss.org/jbpm/updatesite-6.4.1/ > Missing libraries in new jBPM project > ------------------------------------- > > Key: DROOLS-1151 > URL: https://issues.jboss.org/browse/DROOLS-1151 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 6.4.0.Final > Environment: * JBDS 9.1.0.GA > * drools-jbpm plugin 6.4.1.201604291802 > Reporter: Jozef Marko > Assignee: Robert (Bob) Brodt > > In project created via [1] are missing libraries. Specifically classes from packages [2] can not be found. > [1] > File -> New -> Other -> jBPM -> jBPM project -> project with example files -> build project using Java and jBPM classes > [2] > javax.persistence.* > org.jbpm.test.* -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2016