April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3097) Add support to export data from Scenario

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3097?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-3097: ---------------------------------- Description: As user I want to be able to export data from a scenario (was: As user I want to be able to import and export data from a scenario) > Add support to export data from Scenario > ---------------------------------------- > > Key: DROOLS-3097 > URL: https://issues.jboss.org/browse/DROOLS-3097 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > > As user I want to be able to export data from a scenario -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3843) DMN Editor Decision Navigator differentiate icons for DRGElement

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-3843: -------------------------------------- Summary: DMN Editor Decision Navigator differentiate icons for DRGElement Key: DROOLS-3843 URL: https://issues.jboss.org/browse/DROOLS-3843 Project: Drools Issue Type: Enhancement Components: DMN Editor Reporter: Matteo Mortari Assignee: Michael Anstis Attachments: image-2019-04-03-10-38-39-270.png In this example: !image-2019-04-03-10-38-39-270.png|thumbnail! The 1st one is a Decision, the other are Input Data. Experienced DMN practitioner may know that a decision logic can only happen to Decision or BKM node, hence one could distinguish potential Input data node by not having decision logic (context in the example). But also what about Decision or BKM for which you didn't write the decision logic yet? PLease consider distinguished icon for DRG Elements. For example leave Input Data with the filled circle Decision: filled square BKM: filled trapezoid. Thanks -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3097) Add support to export data from Scenario

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3097?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-3097: ---------------------------------- Summary: Add support to export data from Scenario (was: Add support to import/export data from Scenario) > Add support to export data from Scenario > ---------------------------------------- > > Key: DROOLS-3097 > URL: https://issues.jboss.org/browse/DROOLS-3097 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > > As user I want to be able to import and export data from a scenario -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBREM-1340) Memory leak related to org.jboss.threads.JBossThreadFactory

by Adrián López (Jira)

[ https://issues.jboss.org/browse/JBREM-1340?page=com.atlassian.jira.plugin... ] Adrián López commented on JBREM-1340: ------------------------------------- Where can I find some doc to know how to configure the new client with the "old" remoting? Kinda los with this protocol and its transports. Thanks > Memory leak related to org.jboss.threads.JBossThreadFactory > ----------------------------------------------------------- > > Key: JBREM-1340 > URL: https://issues.jboss.org/browse/JBREM-1340 > Project: JBoss Remoting > Issue Type: Bug > Components: jmx remoting > Reporter: Adrián López > Priority: Major > Attachments: img-2019-04-01-130952.png, lep2jia1-heapdump-1554113927775_Leak_Suspects.zip > > > We have a memory leak when using the jboss-cli-client JAR inside of Jolokia. > Jolokia uses remoting to connect to the JMX of several JBoss servers. After running for some days, the Old Gen memory space reach 100%. > A heap dump analyzed with Eclipse MAT returns: > {code} > One instance of "java.lang.ThreadGroup" loaded by "<system class loader>" occupies 377.517.248 (87,28%) bytes. The instance is referenced by org.jboss.threads.JBossThread @ 0xe0a81ef0 HTTP-11 , loaded by "org.jboss.modules.ModuleClassLoader @ 0xe04ffe20". The memory is accumulated in one instance of "java.lang.ThreadGroup[]" loaded by "<system class loader>". > The stacktrace of this Thread is available. See stacktrace. > Keywords > java.lang.ThreadGroup[] > org.jboss.modules.ModuleClassLoader @ 0xe04ffe20 > java.lang.ThreadGroup > {code} > Thread stack > {code} > HTTP-11 > at sun.misc.Unsafe.park(ZJ)V (Native Method) > at java.util.concurrent.locks.LockSupport.park(Ljava/lang/Object;)V (LockSupport.java:186) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await()V (AbstractQueuedSynchronizer.java:2043) > at java.util.concurrent.LinkedBlockingQueue.take()Ljava/lang/Object; (LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask()Ljava/lang/Runnable; (ThreadPoolExecutor.java:1068) > at java.util.concurrent.ThreadPoolExecutor.runWorker(Ljava/util/concurrent/ThreadPoolExecutor$Worker;)V (ThreadPoolExecutor.java:1130) > at java.util.concurrent.ThreadPoolExecutor$Worker.run()V (ThreadPoolExecutor.java:615) > at java.lang.Thread.run()V (Thread.java:745) > at org.jboss.threads.JBossThread.run()V (JBossThread.java:122) > {code} > I have created also another [issue|https://issues.jboss.org/browse/JBTHR-72] to jboss-threads, but looks the problem is not there. > Same for [Jolokia|https://github.com/rhuss/jolokia/issues/401] > Thanks -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11936) Unbound log messages at server startup

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-11936: -------------------------------------- Summary: Unbound log messages at server startup Key: WFLY-11936 URL: https://issues.jboss.org/browse/WFLY-11936 Project: WildFly Issue Type: Bug Components: Naming Affects Versions: 16.0.0.Final Reporter: Eduardo Martins Assignee: Eduardo Martins When server starts there are "Unbound ..." messages incorrectly logged, before related resources are bound. E.g. the following messages may be seen when starting the standalone-full.xml configuration: {code} 07:14:07,656 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default] 07:14:07,674 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] 07:14:07,855 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS] 07:14:08,604 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] 07:14:11,858 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA] 07:14:11,862 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0119: Unbinding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory 07:14:12,131 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-8) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] 07:14:12,131 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9448) Unrecoverable "..DummyTransaction{xid=DummyXid{id=437353}, status=3} is not in a valid state.." after " Unable to acquire lock after 15 seconds"

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-9448?page=com.atlassian.jira.plugin.... ] Paul Ferraro closed WFLY-9448. ------------------------------ Resolution: Out of Date > Unrecoverable "..DummyTransaction{xid=DummyXid{id=437353}, status=3} is not in a valid state.." after " Unable to acquire lock after 15 seconds" > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-9448 > URL: https://issues.jboss.org/browse/WFLY-9448 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Environment: Centos > Reporter: jamie smith > Assignee: Paul Ferraro > Priority: Major > > On our system, after some time we get this: > javax.ejb.EJBTransactionRolledbackException: ISPN000299: Unable to acquire lock after 15 seconds for key UnknownSessionID [4957576549555554536866505268565165695766655070536957516655656852] and requestor GlobalTransaction:<node1>:682146:local. Lock is held by GlobalTransaction:<node1>:681890:local > And then we start getting the following: > ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (default task-2) ISPN000136: Error executing command GetKeyValueCommand, writing keys []: java.lang.IllegalStateException: Transaction DummyTransaction{xid=DummyXid{id=437353}, status=3} is not in a valid state to be invoking cache operations on. > at org.infinispan.interceptors.TxInterceptor.enlist(TxInterceptor.java:395) > ... > ERROR [io.undertow.request] (default task-2) UT005023: Exception handling request to /contextpath/someXYZResource: java.lang.IllegalStateException: Transaction DummyTransaction{xid=DummyXid{id=437353}, status=3} is not in a valid state to be invoking cache operations on. > continouously on most requests without being able to recover. > After restarting, again if at some point the "Unable to acquire lock after 15 seconds" happens, we start getting errors about the DummyTransaction, which never stop. > I believe "Unable to acquire lock after 15 seconds" should not lead to an unrecoverable state. > NOTE: Each node runs with: > `./standalone.sh -c=standalone-full-ha.xml -u=239.255.200.215 -b=$localIp -bmanagement=$localIp -bprivate=$localIp -Djboss.node.name=node1 -Djboss.socket.binding.port-offset=200` . > `jboss.node.name` and `$localIp` only changes between nodes. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5685) Deployment-specific caches do not expose management metrics/operations

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-5685?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-5685: ------------------------------- Summary: Deployment-specific caches do not expose management metrics/operations (was: Register management resources for deployment-specific caches) > Deployment-specific caches do not expose management metrics/operations > ---------------------------------------------------------------------- > > Key: WFLY-5685 > URL: https://issues.jboss.org/browse/WFLY-5685 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR4 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5685) Register management resources for deployment-specific caches

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-5685?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-5685: ------------------------------- Issue Type: Bug (was: Feature Request) > Register management resources for deployment-specific caches > ------------------------------------------------------------ > > Key: WFLY-5685 > URL: https://issues.jboss.org/browse/WFLY-5685 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR4 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3727) [DMN Designer] Quick Silver: Minimal standalone preparation

by Roger Martinez (Jira)

[ https://issues.jboss.org/browse/DROOLS-3727?page=com.atlassian.jira.plugi... ] Roger Martinez edited comment on DROOLS-3727 at 4/2/19 9:11 PM: ---------------------------------------------------------------- Ok great, thanks [~manstis] for the great and fast feedback! :-) Soo trying to summarize what being commented til this point, here are some resulting actions I see: * From my side (BPMN) ** First trying to achieve the BPMN standalone webapp work as the DMN one ** At this point, as I'll have better knowledge on this stuff, I'll be moving to reduce the dependencies as much as possible and identify other next steps, let's keep in touch * From our side (BPMN/DMN) ** What about creating a new branch in [kie-wb-common|https://github.com/kiegroup/kie-wb-common/] for us? (eg: _submarine_, _stunner-submarine_) For now there is no need even to compile it in Jenkins, as some of the dependencies will be still not available, but will be our shared code where both can be commiting and sharing progress. WDYT? Also if the idea is to keep 7.x / 8.x support, I understand we should be manually rebasing this branch with master, right? ** Also yeah would be nice being able to have the complete picture, by being able to deploy locally our editors into VSCode or Che (depends on next point) * From [~porcelli] 's side - PLEASE [~porcelli] can you provide us feedback (code, links...) about how you customize and run the standalone DMN webapp in VSCode, as you shown in last week's presentation? Thanks in advance guys! was (Author: roger600): Ok great, thanks [~manstis] for the great and fast feedback! :-) Soo trying to summarize what being commented til this point, here are some resulting actions I see: * From my side (BPMN) ** First trying to achieve the BPMN standalone webapp work as the DMN one ** At this point, as I'll have better knowledge on this stuff, I'll be moving to reduce the dependencies as much as possible and identify other next steps * From our side (BPMN/DMN) ** What about creating a new branch in [kie-wb-common|https://github.com/kiegroup/kie-wb-common/] for us? (eg: _submarine_, _stunner-submarine_) For now there is no need even to compile it in Jenkins, as some of the dependencies will be still not available, but will be our shared code where both can be commiting and sharing progress. WDYT? Also if the idea is to keep 7.x / 8.x support, I understand we should be manually rebasing this branch with master, right? ** Also yeah would be nice being able to have the complete picture, by being able to deploy locally our editors into VSCode or Che (depends on next point) * From [~porcelli] 's side - PLEASE [~porcelli] can you provide us feedback (code, links...) about how you customize and run the standalone DMN webapp in VSCode, as you shown in last week's presentation? Thanks in advance guys! > [DMN Designer] Quick Silver: Minimal standalone preparation > ----------------------------------------------------------- > > Key: DROOLS-3727 > URL: https://issues.jboss.org/browse/DROOLS-3727 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Critical > Labels: Stunner, drools-tools, submarine > Fix For: 8.0.0.Final > > > Prepare a minimal DMN Designer standalone WAR that only supports _standalone_ mode. > No Home Page, no Library, No preferences, no other editors. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3727) [DMN Designer] Quick Silver: Minimal standalone preparation

by Roger Martinez (Jira)

[ https://issues.jboss.org/browse/DROOLS-3727?page=com.atlassian.jira.plugi... ] Roger Martinez commented on DROOLS-3727: ---------------------------------------- Ok great, thanks [~manstis] for the great and fast feedback! :-) Soo trying to summarize what being commented til this point, here are some resulting actions I see: * From my side (BPMN) ** First trying to achieve the BPMN standalone webapp work as the DMN one ** At this point, as I'll have better knowledge on this stuff, I'll be moving to reduce the dependencies as much as possible and identify other next steps * From our side (BPMN/DMN) ** What about creating a new branch in [kie-wb-common|https://github.com/kiegroup/kie-wb-common/] for us? (eg: _submarine_, _stunner-submarine_) For now there is no need even to compile it in Jenkins, as some of the dependencies will be still not available, but will be our shared code where both can be commiting and sharing progress. WDYT? Also if the idea is to keep 7.x / 8.x support, I understand we should be manually rebasing this branch with master, right? ** Also yeah would be nice being able to have the complete picture, by being able to deploy locally our editors into VSCode or Che (depends on next point) * From [~porcelli] 's side - PLEASE [~porcelli] can you provide us feedback (code, links...) about how you customize and run the standalone DMN webapp in VSCode, as you shown in last week's presentation? Thanks in advance guys! > [DMN Designer] Quick Silver: Minimal standalone preparation > ----------------------------------------------------------- > > Key: DROOLS-3727 > URL: https://issues.jboss.org/browse/DROOLS-3727 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Critical > Labels: Stunner, drools-tools, submarine > Fix For: 8.0.0.Final > > > Prepare a minimal DMN Designer standalone WAR that only supports _standalone_ mode. > No Home Page, no Library, No preferences, no other editors. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

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 April 2019