June 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1208) Listed deployed packages are duplicated when creating a new Container in Workbench.

by Jonathan Holmström (JIRA)

Jonathan Holmström created DROOLS-1208: ------------------------------------------ Summary: Listed deployed packages are duplicated when creating a new Container in Workbench. Key: DROOLS-1208 URL: https://issues.jboss.org/browse/DROOLS-1208 Project: Drools Issue Type: Bug Affects Versions: 6.4.0.Final Reporter: Jonathan Holmström Assignee: Mark Proctor This only seems to occur on the first container create window you open after starting the workbench UI. Closing and reopening the window removes the duplication. When the packages are duplicated, clicking the second entry for each package will result in: 11:17:40,985 ERROR [org.guvnor.m2repo.backend.server.GuvnorM2Repository] (default task-64) error in opening zip file And will not fill in any package fields. The first entry works as expected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6730) Upgrade Artemis 1.3.0

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-6730: --------------------------------- Summary: Upgrade Artemis 1.3.0 Key: WFLY-6730 URL: https://issues.jboss.org/browse/WFLY-6730 Project: WildFly Issue Type: Component Upgrade Components: JMS Reporter: Jeff Mesnil Assignee: Jeff Mesnil -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1207) Container Runtime Strategy and Merge Mode cannot be changed from Workbench

by Jonathan Holmström (JIRA)

Jonathan Holmström created DROOLS-1207: ------------------------------------------ Summary: Container Runtime Strategy and Merge Mode cannot be changed from Workbench Key: DROOLS-1207 URL: https://issues.jboss.org/browse/DROOLS-1207 Project: Drools Issue Type: Bug Affects Versions: 6.4.0.Final Reporter: Jonathan Holmström Assignee: Mark Proctor The same thing applies to creating a new container. No matter what is set in the Process Configuration tab, the runtime strategy will always be created as "Singleton" and the merge mode will always be "Keep All" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1203) OptaPlanner on KIE Server running on Wildfly 9.0.2 throwing IllegalArgumentException on startup

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1203?page=com.atlassian.jira.plugi... ] Geoffrey De Smet resolved DROOLS-1203. -------------------------------------- Fix Version/s: 7.0.0.Beta1 Resolution: Duplicate Issue Duplicates PLANNER-562. I 'll try to find some time to fix that on master, should be an easy fix. > OptaPlanner on KIE Server running on Wildfly 9.0.2 throwing IllegalArgumentException on startup > ----------------------------------------------------------------------------------------------- > > Key: DROOLS-1203 > URL: https://issues.jboss.org/browse/DROOLS-1203 > Project: Drools > Issue Type: Bug > Affects Versions: 6.4.0.Final > Environment: Wildfly 9.0.2 > Reporter: Jonathan Holmström > Assignee: Geoffrey De Smet > Fix For: 7.0.0.Beta1 > > > The following exception is thrown at startup. The server still starts successfully. > [31m04:08:44,729 ERROR [org.kie.server.services.impl.KieServerImpl] (ServerService Thread Pool -- 65) Error when initializing server extension of type OptaPlanner KIE Server extension: java.lang.IllegalArgumentException > at java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1307) > at java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1195) > at org.kie.server.services.optaplanner.OptaplannerKieServerExtension.init(OptaplannerKieServerExtension.java:75) > at org.kie.server.services.impl.KieServerImpl.<init>(KieServerImpl.java:108) > at org.kie.server.services.impl.KieServerLocator.<clinit>(KieServerLocator.java:20) > at org.kie.server.services.Bootstrap.contextInitialized(Bootstrap.java:50) > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173) > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:195) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:100) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:82) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1203) OptaPlanner on KIE Server running on Wildfly 9.0.2 throwing IllegalArgumentException on startup

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1203?page=com.atlassian.jira.plugi... ] Geoffrey De Smet reassigned DROOLS-1203: ---------------------------------------- Assignee: Geoffrey De Smet (was: Mark Proctor) > OptaPlanner on KIE Server running on Wildfly 9.0.2 throwing IllegalArgumentException on startup > ----------------------------------------------------------------------------------------------- > > Key: DROOLS-1203 > URL: https://issues.jboss.org/browse/DROOLS-1203 > Project: Drools > Issue Type: Bug > Affects Versions: 6.4.0.Final > Environment: Wildfly 9.0.2 > Reporter: Jonathan Holmström > Assignee: Geoffrey De Smet > > The following exception is thrown at startup. The server still starts successfully. > [31m04:08:44,729 ERROR [org.kie.server.services.impl.KieServerImpl] (ServerService Thread Pool -- 65) Error when initializing server extension of type OptaPlanner KIE Server extension: java.lang.IllegalArgumentException > at java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1307) > at java.util.concurrent.ThreadPoolExecutor.<init>(ThreadPoolExecutor.java:1195) > at org.kie.server.services.optaplanner.OptaplannerKieServerExtension.init(OptaplannerKieServerExtension.java:75) > at org.kie.server.services.impl.KieServerImpl.<init>(KieServerImpl.java:108) > at org.kie.server.services.impl.KieServerLocator.<clinit>(KieServerLocator.java:20) > at org.kie.server.services.Bootstrap.contextInitialized(Bootstrap.java:50) > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173) > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:195) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:100) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:82) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1206) KIE Execution Server documentation shows faulty time unit for KieScanner interval.

by Jonathan Holmström (JIRA)

Jonathan Holmström created DROOLS-1206: ------------------------------------------ Summary: KIE Execution Server documentation shows faulty time unit for KieScanner interval. Key: DROOLS-1206 URL: https://issues.jboss.org/browse/DROOLS-1206 Project: Drools Issue Type: Bug Affects Versions: 6.4.0.Final Reporter: Jonathan Holmström Assignee: Mark Proctor In Rule Deployments -> Container -> Version Configuration The input interval is interpreted as milliseconds, not seconds. The documentation indicates that this should be seconds. From: https://docs.jboss.org/drools/release/6.4.0.Final/drools-docs/html/ch22.html Quote: Automatic Update: If you want a deployed Container to always have the latest version of your deployment without manually editing it, you will need to set the Version property to the value of LATEST and start a Scanner. This will ensure that the deployed provision always contains the latest version. The Scanner can be started just once on demand by clicking the Scan Now button or you can start it in the background with scans happening at a specified interval (in seconds).You can also set this value to LATEST when you are first creating this deployment. The Resolved Release Id in this case will show you the actual, latest version number. Relevant section: "scans happening at a specified interval (in seconds)" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1205) Workbench UI does not indicate the time unit for the scanner update interval

by Jonathan Holmström (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1205?page=com.atlassian.jira.plugi... ] Jonathan Holmström updated DROOLS-1205: --------------------------------------- Description: in Rule Deployments -> Container -> Version Configuration > Workbench UI does not indicate the time unit for the scanner update interval > ---------------------------------------------------------------------------- > > Key: DROOLS-1205 > URL: https://issues.jboss.org/browse/DROOLS-1205 > Project: Drools > Issue Type: Bug > Affects Versions: 6.4.0.Final > Reporter: Jonathan Holmström > Assignee: Mark Proctor > > in Rule Deployments -> Container -> Version Configuration -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1205) Workbench UI does not indicate the time unit for the scanner update interval

by Jonathan Holmström (JIRA)

Jonathan Holmström created DROOLS-1205: ------------------------------------------ Summary: Workbench UI does not indicate the time unit for the scanner update interval Key: DROOLS-1205 URL: https://issues.jboss.org/browse/DROOLS-1205 Project: Drools Issue Type: Bug Affects Versions: 6.4.0.Final Reporter: Jonathan Holmström Assignee: Mark Proctor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-122) Add maxBackupIndex to periodic-rotating-file-handlers

by Rémy Garrigue (JIRA)

Rémy Garrigue created JBLOGGING-122: --------------------------------------- Summary: Add maxBackupIndex to periodic-rotating-file-handlers Key: JBLOGGING-122 URL: https://issues.jboss.org/browse/JBLOGGING-122 Project: JBoss Logging Issue Type: Enhancement Reporter: Rémy Garrigue Assignee: James Perkins Priority: Minor That's all in the title. We would like to have a daily log, keeping 15 days of log. Actually there's no way to do that except maybe custom handler which we can't get to work. That'ld be far easier if there was the same maxBackupIndex option as in size rotating handler. Regards, -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1204) KieScanner on KIE server does not start automatically after container restart or server restart.

by Jonathan Holmström (JIRA)

Jonathan Holmström created DROOLS-1204: ------------------------------------------ Summary: KieScanner on KIE server does not start automatically after container restart or server restart. Key: DROOLS-1204 URL: https://issues.jboss.org/browse/DROOLS-1204 Project: Drools Issue Type: Bug Affects Versions: 6.4.0.Final Reporter: Jonathan Holmström Assignee: Mark Proctor KieScanner does not pick up new project versions after the container or kie server is restarted, even though the workbench UI indicates that the scanner is running. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 June 2016