September 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2187) Make module and class writable attributes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2187?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2187: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1013830 > Make module and class writable attributes > ----------------------------------------- > > Key: WFLY-2187 > URL: https://issues.jboss.org/browse/WFLY-2187 > Project: WildFly > Issue Type: Feature Request > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > Fix For: 8.0.0.CR1 > > > The {{class}} and {{module}} attributes on a {{custom-handler}} should be made writable. If changed the logmanager config API will just need to remove the original handler and add a new one. This may also need to check whether the handler is attached to a logger or other handlers. > If the add/remove won't work from the logmanager, then a {{reload}} should be required. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-272) KieSession.fireUntilHalt() consumes 100% CPU

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-272?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-272: ------------------------------------------------ Edson Tirelli <etirelli(a)redhat.com> made a comment on [bug 1012140|https://bugzilla.redhat.com/show_bug.cgi?id=1012140] Just an update, I fixed the 100% CPU problem in a local branch, but that broke a list of other tests. I've been going through each of those tests and fixing the side effects of the code changes. I will keep you posted. > KieSession.fireUntilHalt() consumes 100% CPU > -------------------------------------------- > > Key: DROOLS-272 > URL: https://issues.jboss.org/browse/DROOLS-272 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.CR3 > Environment: Mac OS-X 1.8.5 + Hotspot JDK 1.7.0_40, RHEL 6.4 + OpenJDK 1.7.0_25, Fedora 18 + Java 6. > Reporter: Duncan Doyle > Assignee: Mark Proctor > Priority: Blocker > > When I run a KieSession.fireUntilHalt(), my application starts consuming 100% CPU, without anything actually happening inside the app (no events/facts are being inserted, no rules are activated/fired, etc.). We've tested this on multiple machines, different OSs, different JDKs, etc., and they all show the same behaviour. > I've created a small test that shows the problem. The test loads a simple DRL via KieClasspathContainer, retrieves a new KieSession and runs a KieSession.fireUntilHalt() in a separate thread. After launching the thread, I let the main thread sleep for 30 seconds (3 * 10) and during this time period, CPU load increases to 100%. I then halt the session and sleep for another 10 seconds, which causes the CPU load to back to normal. The test project can be found here: https://github.com/DuncanDoyle/DroolsFireUntilHalt/ > Just run 'mvn clean test' on the project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2187) Make module and class writable attributes

by James Perkins (JIRA)

James Perkins created WFLY-2187: ----------------------------------- Summary: Make module and class writable attributes Key: WFLY-2187 URL: https://issues.jboss.org/browse/WFLY-2187 Project: WildFly Issue Type: Feature Request Components: Logging Reporter: James Perkins Assignee: James Perkins Priority: Minor Fix For: 8.0.0.CR1 The {{class}} and {{module}} attributes on a {{custom-handler}} should be made writable. If changed the logmanager config API will just need to remove the original handler and add a new one. This may also need to check whether the handler is attached to a logger or other handlers. If the add/remove won't work from the logmanager, then a {{reload}} should be required. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2183) Module and ClassName fields are disabled in new Custom handler dialog

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-2183?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-2183: ---------------------------------------- Thanks, James. That's the expected metadata then for an attribute that cannot be modified after creation. > Module and ClassName fields are disabled in new Custom handler dialog > --------------------------------------------------------------------- > > Key: WFLY-2183 > URL: https://issues.jboss.org/browse/WFLY-2183 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Logging > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 8.0.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2183) Module and ClassName fields are disabled in new Custom handler dialog

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-2183?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-2183: ----------------------------------- Assignee: Heiko Braun (was: James Perkins) > Module and ClassName fields are disabled in new Custom handler dialog > --------------------------------------------------------------------- > > Key: WFLY-2183 > URL: https://issues.jboss.org/browse/WFLY-2183 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Logging > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 8.0.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-276) Stream mode with CR4-Pre1 generates rules looping

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-276?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-276: ------------------------------------------------ Edson Tirelli <etirelli(a)redhat.com> changed the Status of [bug 1012933|https://bugzilla.redhat.com/show_bug.cgi?id=1012933] from NEW to ASSIGNED > Stream mode with CR4-Pre1 generates rules looping > -------------------------------------------------- > > Key: DROOLS-276 > URL: https://issues.jboss.org/browse/DROOLS-276 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.CR4 > Environment: Drools 6.0.0.CR4-Pre1 > Reporter: Richard Bourner > Assignee: Mark Proctor > Priority: Blocker > Attachments: Drools6Stream.zip > > > When in STREAM mode, our rules are looping because of an update. > The attached example doesn't demonstrate the looping but one rule is fired twice where it should only fire once. We are supposing that the issue is the same. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBJCA-1075) ironjacamar-deployers-common.jar contains source files (*.java)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1075?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1075: ------------------------------------------------ Fernando Nasser <fnasser(a)redhat.com> made a comment on [bug 996098|https://bugzilla.redhat.com/show_bug.cgi?id=996098] Hi Lin, we are now shipping 1.0.21, can you confirm if this fix is included or not? It it is, can you please set the Target Version and milestone to EAP 6.2.0 and ER3 respectively and move to ON_QA ? Thanks. > ironjacamar-deployers-common.jar contains source files (*.java) > --------------------------------------------------------------- > > Key: JBJCA-1075 > URL: https://issues.jboss.org/browse/JBJCA-1075 > Project: IronJacamar > Issue Type: Bug > Components: Build > Affects Versions: 1.0.20.Final, 1.1.0.Final > Reporter: Lin Gao > Assignee: Lin Gao > > There are .java files included in ironjacamar-deployers-common.jar: > {code}[lgao@dhcp-192-139 target]$ unzip -l ironjacamar-deployers-common.jar |grep ".java" > 8739 08-30-2013 16:30 org/jboss/jca/deployers/DeployersBundle_$bundle.java > 7944 08-30-2013 16:30 org/jboss/jca/deployers/DeployersLogger_$logger.java > {code} > The generated java file should not be packaged in the binary jar. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2183) Module and ClassName fields are disabled in new Custom handler dialog

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2183?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-2183: ------------------------------------- Indeed they are and noted as required. _Note: Omitted the filter value-type_ {code} { "outcome" => "success", "result" => { "operation-name" => "add", "description" => "Add a new logging handler.", "request-properties" => { "enabled" => { "type" => BOOLEAN, "description" => "If set to true the handler is enabled and functioning as normal, if set to false the handler is ignored when processing log messages.", "expressions-allowed" => true, "required" => false, "nillable" => true, "default" => true }, "module" => { "type" => STRING, "description" => "The module that the logging handler depends on.", "expressions-allowed" => false, "required" => true, "nillable" => false, "min-length" => 1L, "max-length" => 2147483647L }, "class" => { "type" => STRING, "description" => "The logging handler class to be used.", "expressions-allowed" => false, "required" => true, "nillable" => false, "min-length" => 1L, "max-length" => 2147483647L }, "named-formatter" => { "type" => STRING, "description" => "The name of the defined formatter to be used on the handler.", "expressions-allowed" => false, "required" => false, "nillable" => true, "alternatives" => ["formatter"], "min-length" => 1L, "max-length" => 2147483647L }, "properties" => { "type" => OBJECT, "description" => "Defines the properties used for the logging handler. All properties must be accessible via a setter method.", "expressions-allowed" => true, "required" => false, "nillable" => true, "value-type" => STRING }, "formatter" => { "type" => STRING, "description" => "Defines a pattern for the formatter.", "expressions-allowed" => true, "required" => false, "nillable" => true, "default" => "%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n", "alternatives" => ["named-formatter"], "min-length" => 1L, "max-length" => 2147483647L }, "filter-spec" => { "type" => STRING, "description" => "A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match(\"JBAS.*\"))", "expressions-allowed" => true, "required" => false, "nillable" => true, "alternatives" => ["filter"], "min-length" => 1L, "max-length" => 2147483647L }, "level" => { "type" => STRING, "description" => "The log level specifying which message levels will be logged by this logger. Message levels lower than this value will be discarded.", "expressions-allowed" => true, "required" => false, "nillable" => true, "default" => "ALL", "allowed" => [ "ALL", "FINEST", "FINER", "TRACE", "DEBUG", "FINE", "CONFIG", "INFO", "WARN", "WARNING", "ERROR", "FATAL", "OFF" ] }, "name" => { "type" => STRING, "description" => "The handler's name.", "expressions-allowed" => false, "required" => false, "nillable" => true, "min-length" => 1L, "max-length" => 2147483647L, "deprecated" => { "since" => "1.2.0", "reason" => "The name attribute should not be used as the handler's address contains the name." } }, "encoding" => { "type" => STRING, "description" => "The character encoding used by this Handler.", "expressions-allowed" => true, "required" => false, "nillable" => true, "min-length" => 1L, "max-length" => 2147483647L }, "filter" => { "type" => OBJECT, "description" => "Defines a simple filter type.", "expressions-allowed" => false, "required" => false, "nillable" => true, "alternatives" => ["filter-spec"], "deprecated" => { "since" => "1.2.0", "reason" => "Use filter-spec." }, "value-type" => { } }, "reply-properties" => {}, "read-only" => false } } {code} > Module and ClassName fields are disabled in new Custom handler dialog > --------------------------------------------------------------------- > > Key: WFLY-2183 > URL: https://issues.jboss.org/browse/WFLY-2183 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Logging > Reporter: Heiko Braun > Assignee: James Perkins > Fix For: 8.0.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2183) Module and ClassName fields are disabled in new Custom handler dialog

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-2183?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-2183: ----------------------------------- Assignee: James Perkins (was: Brian Stansberry) Component/s: Logging > Module and ClassName fields are disabled in new Custom handler dialog > --------------------------------------------------------------------- > > Key: WFLY-2183 > URL: https://issues.jboss.org/browse/WFLY-2183 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Logging > Reporter: Heiko Braun > Assignee: James Perkins > Fix For: 8.0.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2183) Module and ClassName fields are disabled in new Custom handler dialog

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-2183?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-2183: ---------------------------------------- James, what does the :read-operation-description for the :add op look like? Are these parameters present? > Module and ClassName fields are disabled in new Custom handler dialog > --------------------------------------------------------------------- > > Key: WFLY-2183 > URL: https://issues.jboss.org/browse/WFLY-2183 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Logging > Reporter: Heiko Braun > Assignee: James Perkins > Fix For: 8.0.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2013