April 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4347) CLONE - http://localhost:9990/error/index_win.html refers to add-user.sh

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/AS7-4347?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on AS7-4347: --------------------------------------- Actually no the windows version is supposed to reference just the .bat > CLONE - http://localhost:9990/error/index_win.html refers to add-user.sh > ------------------------------------------------------------------------ > > Key: AS7-4347 > URL: https://issues.jboss.org/browse/AS7-4347 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.0.Final, 7.1.1.Final > Environment: Windows 7 > Reporter: Burr Sutter > Fix For: 7.1.2.Final > > Attachments: add-user.sh.png > > > Welcome to EAP 6 > Your JBoss Enterprise Application Platform is running. > However you have not yet added any users to be able to access the admin console. > To add a new user execute the add-user.sh script within the bin folder of your EAP 6 installation and enter the requested information. > By default the realm name used by EAP 6 is "ManagementRealm" this is already selected by default. > After you have added the user follow this link to Try Again. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-4347) CLONE - http://localhost:9990/error/index_win.html refers to add-user.sh

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/AS7-4347?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse reassigned AS7-4347: ------------------------------------- Assignee: Darran Lofthouse > CLONE - http://localhost:9990/error/index_win.html refers to add-user.sh > ------------------------------------------------------------------------ > > Key: AS7-4347 > URL: https://issues.jboss.org/browse/AS7-4347 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.0.Final, 7.1.1.Final > Environment: Windows 7 > Reporter: Burr Sutter > Assignee: Darran Lofthouse > Fix For: 7.1.2.Final > > Attachments: add-user.sh.png > > > Welcome to EAP 6 > Your JBoss Enterprise Application Platform is running. > However you have not yet added any users to be able to access the admin console. > To add a new user execute the add-user.sh script within the bin folder of your EAP 6 installation and enter the requested information. > By default the realm name used by EAP 6 is "ManagementRealm" this is already selected by default. > After you have added the user follow this link to Try Again. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-4347) http://localhost:9990/error/index_win.html refers to add-user.sh

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/AS7-4347?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated AS7-4347: ---------------------------------- Summary: http://localhost:9990/error/index_win.html refers to add-user.sh (was: CLONE - http://localhost:9990/error/index_win.html refers to add-user.sh) > http://localhost:9990/error/index_win.html refers to add-user.sh > ---------------------------------------------------------------- > > Key: AS7-4347 > URL: https://issues.jboss.org/browse/AS7-4347 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.0.Final, 7.1.1.Final > Environment: Windows 7 > Reporter: Burr Sutter > Assignee: Darran Lofthouse > Fix For: 7.1.2.Final > > Attachments: add-user.sh.png > > > Welcome to EAP 6 > Your JBoss Enterprise Application Platform is running. > However you have not yet added any users to be able to access the admin console. > To add a new user execute the add-user.sh script within the bin folder of your EAP 6 installation and enter the requested information. > By default the realm name used by EAP 6 is "ManagementRealm" this is already selected by default. > After you have added the user follow this link to Try Again. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-3949) Admin console: invalid parameter value being specified when creating datasources

by Jan Martiska (JIRA)

Jan Martiska created AS7-3949: --------------------------------- Summary: Admin console: invalid parameter value being specified when creating datasources Key: AS7-3949 URL: https://issues.jboss.org/browse/AS7-3949 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.Final Reporter: Jan Martiska Assignee: Heiko Braun Priority: Critical When creating a datasource (regular or XA datasource), the console sets by default "background-validation-millis" => 0L .. This will cause the operation to fail with message: "JBAS014708: 0 is an invalid value for parameter background-validation-millis. A minimum value of 1 is required" Tested on latest upstream snapshot. -- 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

12 years

3
12
0 / 0

[JBoss JIRA] Created: (JBRULES-3220) getFactHandle(fact) sometimes returns null even thought the fact is there.

by Geoffrey De Smet (JIRA)

getFactHandle(fact) sometimes returns null even thought the fact is there. -------------------------------------------------------------------------- Key: JBRULES-3220 URL: https://issues.jboss.org/browse/JBRULES-3220 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Assignee: Mario Fusco see MiscTest.testGetFactHandle() which is a regression test for that issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

5
10
0 / 0

[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

12 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

12 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

12 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

12 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

12 years

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2012