April 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3061) Can't create periodic rotating file handler in CLI or console

by Stan Silvert (Created) (JIRA)

Can't create periodic rotating file handler in CLI or console ------------------------------------------------------------- Key: AS7-3061 URL: https://issues.jboss.org/browse/AS7-3061 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.1.0.Beta1b Reporter: Stan Silvert Assignee: James Perkins CLI command:{noformat} /subsystem=logging/periodic-rotating-file-handler=periodicrotating/:add(name=periodicrotating,level=INFO,file={"path" => "myfoo.log", "relative-to" => "jboss.server.log.dir"}) {noformat} CLI error:{noformat} [standalone@localhost:9999 /] /subsystem=logging/periodic-rotating-file-handler=periodicrotating/:add(name=periodicrotating,level=INFO,file={"path" => "myfoo.log", "relat ive-to" => "jboss.server.log.dir"}) { "outcome" => "failed", "failure-description" => {"JBAS014671: Failed services" => {"jboss.logging.handler.periodicrotating" => "org.jboss.msc.service.StartException in service jboss.logging .handler.periodicrotating: Failed to start service"}}, "rolled-back" => true, "response-headers" => {"process-state" => "reload-required"} } {noformat} In server console:{noformat} 15:04:29,303 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.logging.handler.periodicrotating: org.jboss.msc.service.S tartException in service jboss.logging.handler.periodicrotating: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1780) [jboss-msc-1.0.1.GA.jar:] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29] at java.lang.Thread.run(Thread.java:662) [:1.6.0_29] Caused by: java.lang.NullPointerException at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:493) [:1.6.0_29] at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:475) [:1.6.0_29] at org.jboss.logmanager.handlers.PeriodicRotatingFileHandler.setSuffix(PeriodicRotatingFileHandler.java:119) [jboss-logmanager-1.2.0.GA.jar:] at org.jboss.as.logging.handlers.file.PeriodicRotatingFileHandlerService.start(PeriodicRotatingFileHandlerService.java:74) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:] ... 3 more {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
3
0 / 0

[JBoss JIRA] (JBRULES-3367) Planner: score calculation with plain old Java

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created JBRULES-3367: ----------------------------------------- Summary: Planner: score calculation with plain old Java Key: JBRULES-3367 URL: https://issues.jboss.org/browse/JBRULES-3367 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Provide an plain old java alternative to score calculations, so the user has choice (= freedom): - A) Drools score calculation (default). Does incremental calculation automatically, without extra code. - B) Java non-incremental score calculation. Very easy to reuse existing score code, but not fast. - C) Java incremental score calculation. Requires incremental boilerplate code, but experiments show that in some use cases (with little rules) it can be a 100 times faster than A) with drools 5.3. Note that undo-then and JIT compiling might change that number drastically in future drools versions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
10
0 / 0

[JBoss JIRA] (AS7-4104) Admin console" Missing validation of cache container's JNDI name

by Jan Martiska (JIRA)

Jan Martiska created AS7-4104: --------------------------------- Summary: Admin console" Missing validation of cache container's JNDI name Key: AS7-4104 URL: https://issues.jboss.org/browse/AS7-4104 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Jan Martiska Assignee: Heiko Braun Priority: Minor create a cache container (or use the default 'hibernate' one).. set its JNDI name. For all other JNDI names in the console, there is a unified validation pattern, in this case it isn't used and you can set any string here. Console version: 1.1.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
6
0 / 0

[JBoss JIRA] (JBRULES-3288) Sliding time window ignored when using @timestamp and pseudo clock

by Colin Webber (Created) (JIRA)

Sliding time window ignored when using @timestamp and pseudo clock ------------------------------------------------------------------ Key: JBRULES-3288 URL: https://issues.jboss.org/browse/JBRULES-3288 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (fusion) Affects Versions: 5.3.0.Final Environment: Mac OSX 10.6.8 Reporter: Colin Webber Assignee: Mark Proctor When using a custom @timestamp together with PSEUDO clock, all events are accumulated rather than just those within the window:time period. I have tried using long (millisecond) and java.util.Date without success. ================================== declare SimpleObject @role(event) @timestamp(customTime) @expires(10m) end; rule "honour custom timestamp" when $avgVal : Number (longValue > 0) from accumulate ( SimpleObject($valueLng : valueLong ) over window:time (10s) from entry-point "SimpleEP", average ( $valueLng ) ) then System.out.println("avg: " + $avgVal); end --------------------------------------- import java.util.Date; public class SimpleObject { private long customTime; public long valueLong; public SimpleObject(Date customTime, long valueLong) { this.customTime = customTime.getTime(); this.valueLong = valueLong; } public long getCustomTime() { return customTime; } public void setCustomTime(long customTime) { this.customTime = customTime; } public long getValueLong() { return valueLong; } public void setValueLong(long valueLong) { this.valueLong = valueLong; } } ------------ Trivial Spock/Groovy unit test ---------------- @IgnoreRest def "should honour custom timestamp"() { when: use (TimeCategory) { def now = new Date() simpleEp.insert(new SimpleObject(now, 100)) ksession.fireAllRules() clock.advanceTime( 5, TimeUnit.SECONDS ); ksession.fireAllRules() simpleEp.insert(new SimpleObject(5.seconds.from.now, 90)) ksession.fireAllRules() clock.advanceTime( 5, TimeUnit.SECONDS ); ksession.fireAllRules() simpleEp.insert(new SimpleObject(10.seconds.from.now, 80)) ksession.fireAllRules() clock.advanceTime( 5, TimeUnit.SECONDS ); ksession.fireAllRules() simpleEp.insert(new SimpleObject(15.seconds.from.now, 70)) ksession.fireAllRules() clock.advanceTime( 5, TimeUnit.SECONDS ); ksession.fireAllRules() simpleEp.insert(new SimpleObject(20.seconds.from.now, 60)) ksession.fireAllRules() clock.advanceTime( 5, TimeUnit.SECONDS ); ksession.fireAllRules() simpleEp.insert(new SimpleObject(25.seconds.from.now, 50)) ksession.fireAllRules() clock.advanceTime( 5, TimeUnit.SECONDS ); ksession.fireAllRules() } then: 1 == 1 // no assertions - we're examining the stdout. } ================================== OUTPUT (INCORRECT - all values are included for each evalutation): avg: 100.0 avg: 95.0 avg: 90.0 avg: 85.0 avg: 80.0 avg: 75.0 Note that when commenting out the @timestamp tag the output changes to the following (correct) output: avg: 100.0 avg: 95.0 avg: 90.0 avg: 85.0 avg: 80.0 avg: 75.0 avg: 70.0 avg: 65.0 avg: 60.0 avg: 55.0 avg: 50.0 Also note that when using the REALTIME clock with Thread.sleep the output is correct. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
1
0 / 0

[JBoss JIRA] (JBRULES-3332) Accumulate with nested field binding has bad type inference

by Adar Dembo (Created) (JIRA)

Accumulate with nested field binding has bad type inference ----------------------------------------------------------- Key: JBRULES-3332 URL: https://issues.jboss.org/browse/JBRULES-3332 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.3.1.Final Reporter: Adar Dembo Assignee: Mark Proctor (I'm completely new to Drools, so bear with me as I try to describe this) When a rule specifies an accumulate CE containing a variable bound to a nested field expression, the inferred type of the variable is incorrect. I have attached a pull request containing a unit test that is broken by this bug. If I make the nested class' field private and add a getter for it, the test passes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
1
0 / 0

[JBoss JIRA] (JBRULES-3336) Could not parse knowledge when using 'not contains' in a parentheses leading a '!'

by Miles Wen (Created) (JIRA)

Could not parse knowledge when using 'not contains' in a parentheses leading a '!' ---------------------------------------------------------------------------------- Key: JBRULES-3336 URL: https://issues.jboss.org/browse/JBRULES-3336 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.3.0.Final Environment: jdk 1.6u27 drools 5.3.0 final Reporter: Miles Wen Assignee: Mark Proctor This code could not be parsed correctly: rule "out" when Msg(!(set not contains "test")) then end I tried a few simple situations and found that when using 'not contains' operator in a '!' leading parentheses triggers this problem. If no '!' prefixing the parentheses,the program works like a charm... The example above seemed so stupid(you can use a 'contains' operator instead), but this is the simplest toy example.And this problem would be looked more important if you want to write some logic like this: Msg(!(set not contains "test" || !bool && string == "hello")) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
3
0 / 0

[JBoss JIRA] (JBRULES-3360) Wumpus World

by Mark Proctor (JIRA)

Mark Proctor created JBRULES-3360: ------------------------------------- Summary: Wumpus World Key: JBRULES-3360 URL: https://issues.jboss.org/browse/JBRULES-3360 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
2
0 / 0

[JBoss JIRA] (JBRULES-3342) Incorrect/Misleading Expert Documentation For Drools XML Language

by Justin Holmes (JIRA)

Justin Holmes created JBRULES-3342: -------------------------------------- Summary: Incorrect/Misleading Expert Documentation For Drools XML Language Key: JBRULES-3342 URL: https://issues.jboss.org/browse/JBRULES-3342 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-docs-expert Affects Versions: 5.4.0.Beta1, 5.3.1.Final, 5.2.0.Final, 5.1.1.FINAL, 5.0.1.FINAL Environment: None - this a documentation issue Reporter: Justin Holmes Assignee: Mark Proctor The Drools XML language "...has not been developed since drools 4.0, and is considered a deprecated feature." However, the docs for 5.x versions of Drools clearly state, "All the features are available with XML that are available to DRL." As such,the docs need to be updated to reflect the current state of the XML language so users are not mislead. A simple yellow Warning box at the beginning of the XML section stating that the XML hasn't been developed since 4.0 and is consider deprecated will be enough to properly inform users. Removing the "All features..." would be useful as well. I'm planning to provided a pull request in the next week or so.do -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
12
0 / 0

[JBoss JIRA] (JBRULES-3420) ModifyPreviousTuples should avoid creating HashMaps

by Mark Proctor (JIRA)

Mark Proctor created JBRULES-3420: ------------------------------------- Summary: ModifyPreviousTuples should avoid creating HashMaps Key: JBRULES-3420 URL: https://issues.jboss.org/browse/JBRULES-3420 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core (expert) Reporter: Mark Proctor Assignee: Mark Proctor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
2
0 / 0

[JBoss JIRA] (JBRULES-3380) Add RuleFlowGroup events

by Mark Proctor (JIRA)

Mark Proctor created JBRULES-3380: ------------------------------------- Summary: Add RuleFlowGroup events Key: JBRULES-3380 URL: https://issues.jboss.org/browse/JBRULES-3380 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor This is needed to fix JBRULES-3378 "ClassCastException when retrieving AgendaEventListener collection" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
13
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 2012