May 2016 - jboss-jira - Jboss List Archives

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

by Robert (Bob) Brodt (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1151?page=com.atlassian.jira.plugi... ] Robert (Bob) Brodt commented on DROOLS-1151: -------------------------------------------- We usually recommend users to run the jbpm-installer to construct a jbpm runtime environment; this pulls in the jbpm-test jar as well. Not sure that downloading just the jbpm*-bin.zip and unpacking it is a recommended workflow. > 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)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1156) drools-worker threads are created but not cleaned up

by C R (JIRA)

C R created DROOLS-1156: --------------------------- Summary: drools-worker threads are created but not cleaned up Key: DROOLS-1156 URL: https://issues.jboss.org/browse/DROOLS-1156 Project: Drools Issue Type: Bug Components: core engine, kie server Affects Versions: 6.4.0.Final Reporter: C R Assignee: Mario Fusco There is an issue with creation of threads in drools, when using drools in a container (Web Container oder Java EE application server) environment. This could be reproduce as well in KIE execution server as in a dummy web application. If you create a container in drools, there are several new threads named "drools-worker" created. The number of threads depends on the number of CPU cores. When disposing the container, these threads are still running. Even when we undeploy the application, these threads are still running, as they are created by threadpoolexecutor and not by any managedexecutorservice. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6559) Expose stats for transaction System Rollbacks and Average Commit Time in the CLI

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/WFLY-6559?page=com.atlassian.jira.plugin.... ] Michael Musgrove reassigned WFLY-6559: -------------------------------------- Assignee: Tomas Hofman (was: Michael Musgrove) > Expose stats for transaction System Rollbacks and Average Commit Time in the CLI > -------------------------------------------------------------------------------- > > Key: WFLY-6559 > URL: https://issues.jboss.org/browse/WFLY-6559 > Project: WildFly > Issue Type: Feature Request > Components: Transactions > Affects Versions: 10.0.0.Final > Reporter: Michael Musgrove > Assignee: Tomas Hofman > > JBTM-2341 added to two statistics for counting the number of transaction system rollbacks and for reporting the average commit time. These should be exposed in the wildfly CLI. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6559) Expose stats for transaction System Rollbacks and Average Commit Time in the CLI

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/WFLY-6559?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on WFLY-6559: ---------------------------------------- [~thofman] That would be very generous, thanks > Expose stats for transaction System Rollbacks and Average Commit Time in the CLI > -------------------------------------------------------------------------------- > > Key: WFLY-6559 > URL: https://issues.jboss.org/browse/WFLY-6559 > Project: WildFly > Issue Type: Feature Request > Components: Transactions > Affects Versions: 10.0.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > JBTM-2341 added to two statistics for counting the number of transaction system rollbacks and for reporting the average commit time. These should be exposed in the wildfly CLI. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5970) Plain JMS clients don't fallback

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5970?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-5970: ----------------------------------------------- Dmitrii Tikhomirov <dtikhomi(a)redhat.com> changed the Status of [bug 1258304|https://bugzilla.redhat.com/show_bug.cgi?id=1258304] from NEW to ASSIGNED > Plain JMS clients don't fallback > -------------------------------- > > Key: WFLY-5970 > URL: https://issues.jboss.org/browse/WFLY-5970 > Project: WildFly > Issue Type: Bug > Components: EE > Affects Versions: 9.0.2.Final > Environment: all > Reporter: Yong Hao Gao > Assignee: Yong Hao Gao > Fix For: 9.x.x TBD > > > Plain JMS clients don't fallback when the Live server takes over > Version-Release number of selected component > messaging subsystem 1.4 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1148) Enumeration in a extended scenario

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1148?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-1148: ---------------------------------------- [~mario.fusco] [~mark.proctor] I suspect this JIRA has far reaching implications to KieModule. KJARs are runtime artefacts; whereas the meta-data Users can define in the workbench for enumerations is currently authoring-time artefacts (and hence are filtered from the KJAR assembly). The request here is that if Project A contains enumeration defintions; and Project B has Project A as a Maven dependency then the enumerations in Project A should be re-usable. We'd require (1) certain Authoring meta-data is retained in the compiled KJAR and, (2) a means to query a KJAR for certain resources (based on file extension/package). I'm happy to look into the changes; but want to ask whether this is something you're happy with being in a KJAR (as it'd also mean things like DSLs are also retained in the KJAR). IDK whether it'd also mean we should support generation of a KJAR-sources.jar in addition to the regular JAR (as it's the -sources that has the additional meta-data). I'd also need a little guidance as to where to change things. > Enumeration in a extended scenario > ---------------------------------- > > Key: DROOLS-1148 > URL: https://issues.jboss.org/browse/DROOLS-1148 > Project: Drools > Issue Type: Feature Request > Components: tools > Affects Versions: 6.4.0.Final > Reporter: angelo difino > Assignee: Michael Anstis > Priority: Minor > Labels: enumeration, workbench > > in a extended scanrio (a workbench project that include as dependency another project) if an enumeration is defined in base class, in the extended class ( if the dataobject is correctly imported) the drop-down list not appears in workbench. > in the base class the class the drop-down list correctly appears > the issue was discussed here > https://groups.google.com/forum/#!topic/drools-usage/jFVeSZZWi54 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1148) Enumeration in a extended scenario

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1148?page=com.atlassian.jira.plugi... ] Mario Fusco reassigned DROOLS-1148: ----------------------------------- Assignee: Michael Anstis (was: Mario Fusco) > Enumeration in a extended scenario > ---------------------------------- > > Key: DROOLS-1148 > URL: https://issues.jboss.org/browse/DROOLS-1148 > Project: Drools > Issue Type: Feature Request > Components: tools > Affects Versions: 6.4.0.Final > Reporter: angelo difino > Assignee: Michael Anstis > Priority: Minor > Labels: enumeration, workbench > > in a extended scanrio (a workbench project that include as dependency another project) if an enumeration is defined in base class, in the extended class ( if the dataobject is correctly imported) the drop-down list not appears in workbench. > in the base class the class the drop-down list correctly appears > the issue was discussed here > https://groups.google.com/forum/#!topic/drools-usage/jFVeSZZWi54 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6582) Plain JMS clients don't fallback

by Enrique González Martínez (JIRA)

Enrique González Martínez created WFLY-6582: ----------------------------------------------- Summary: Plain JMS clients don't fallback Key: WFLY-6582 URL: https://issues.jboss.org/browse/WFLY-6582 Project: WildFly Issue Type: Bug Components: EE Affects Versions: 9.0.2.Final Environment: all Reporter: Enrique González Martínez Assignee: Yong Hao Gao Fix For: 9.x.x TBD Plain JMS clients don't fallback when the Live server takes over Version-Release number of selected component messaging subsystem 1.4 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 commented on DROOLS-1151: ------------------------------------- Hello [~bbrodt], When I download runtime from this link[1] javax.persistence.* is not missing more but org.jbpm.test.* is still missing. I think that sample project should not demand more as can be found in official runtime downloaded directly from jbpm site. What do you think? [1] http://download.jboss.org/jbpm/release/6.4.0.Final/jbpm-6.4.0.Final-bin.zip > 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)

9 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 updated DROOLS-1152: -------------------------------- Attachment: Screenshot from 2016-05-03 08-12-54.png Screenshot from 2016-05-03 08-13-06.png > 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 > Attachments: Screenshot from 2016-05-03 08-12-54.png, Screenshot from 2016-05-03 08-13-06.png > > > 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)

9 years, 8 months

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 May 2016