March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4984) Enable the executable model in Optaplanner

by Lukáš Petrovický (Jira)

[ https://issues.redhat.com/browse/DROOLS-4984?page=com.atlassian.jira.plug... ] Lukáš Petrovický updated DROOLS-4984: ------------------------------------- Sprint: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23) (was: 2020 Week 10-12 (from Mar 2)) > Enable the executable model in Optaplanner > ------------------------------------------ > > Key: DROOLS-4984 > URL: https://issues.redhat.com/browse/DROOLS-4984 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > Fix For: 7.35.0.Final > > > Currently it's disabled -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4575) Test Scenario: unsaved changes warning appears even if file has not been changed

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4575?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-4575: ------------------------------------- I tried on 7.36.0-SNAPHSOT - Import sample Traffic Violation project - Open its Test Scenario - Close its Test Scenario I was not prompted to discard/save changes. Can we close this jira? > Test Scenario: unsaved changes warning appears even if file has not been changed > -------------------------------------------------------------------------------- > > Key: DROOLS-4575 > URL: https://issues.redhat.com/browse/DROOLS-4575 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: CustomerFocus, drools-tools > > If user opens a scesim file and then close it, no confirmation message should be opened > h2. Manual Acceptance Test > - Opening and closing without changes > - Open, change data in cell, close > - Open, add column, remove column, change column binding, close > - Open, Change settings on the settings panel (e.g. ruleflow group, kie session), close -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4575) Test Scenario: unsaved changes warning appears even if file has not been changed

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4575?page=com.atlassian.jira.plug... ] Jozef Marko edited comment on DROOLS-4575 at 3/24/20 3:51 AM: -------------------------------------------------------------- I tried on 7.36.0-SNAPSHOT - Import sample Traffic Violation project - Open its Test Scenario - Close its Test Scenario I was not prompted to discard/save changes. Can we close this jira? was (Author: jomarko): I tried on 7.36.0-SNAPHSOT - Import sample Traffic Violation project - Open its Test Scenario - Close its Test Scenario I was not prompted to discard/save changes. Can we close this jira? > Test Scenario: unsaved changes warning appears even if file has not been changed > -------------------------------------------------------------------------------- > > Key: DROOLS-4575 > URL: https://issues.redhat.com/browse/DROOLS-4575 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: CustomerFocus, drools-tools > > If user opens a scesim file and then close it, no confirmation message should be opened > h2. Manual Acceptance Test > - Opening and closing without changes > - Open, change data in cell, close > - Open, add column, remove column, change column binding, close > - Open, Change settings on the settings panel (e.g. ruleflow group, kie session), close -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBAS-9587) IdleRemover internalRegisterPool thread blocked

by chang ys (Jira)

chang ys created JBAS-9587: ------------------------------ Summary: IdleRemover internalRegisterPool thread blocked Key: JBAS-9587 URL: https://issues.redhat.com/browse/JBAS-9587 Project: Application Server 3 4 5 and 6 Issue Type: Bug Components: JCA service Affects Versions: JBossAS-4.2.3.GA Reporter: chang ys Assignee: Jesper Pedersen Attachments: jBoss-ThreadDump.txt Thread: http-0.0.0.0-8080-3 : priority:5, demon:true, threadId:609, threadState:BLOCKED, lockName:java.util.ArrayList@13f73ff5 org.jboss.resource.connectionmanager.IdleRemover.internalRegisterPool(IdleRemover.java:92) org.jboss.resource.connectionmanager.IdleRemover.registerPool(IdleRemover.java:53) org.jboss.resource.connectionmanager.InternalManagedConnectionPool.initialize(InternalManagedConnectionPool.java:141) org.jboss.resource.connectionmanager.JBossManagedConnectionPool$SubPoolContext.initialize(JBossManagedConnectionPool.java:477) org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getSubPool(JBossManagedConnectionPool.java:889) org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:565) org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:347) org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:330) org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:402) org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:849) org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89) sun.reflect.GeneratedMethodAccessor141.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:191) com.star.osgi.ServiceLazyReferenceFactoryBean.invoke(ServiceLazyReferenceFactoryBean.java:79) $Proxy1743.getConnection(Unknown Source) org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:111) org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:77) org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:575) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13275) Quickstart README documentation should not promote usage of using background jobs

by James Perkins (Jira)

James Perkins created WFLY-13275: ------------------------------------ Summary: Quickstart README documentation should not promote usage of using background jobs Key: WFLY-13275 URL: https://issues.redhat.com/browse/WFLY-13275 Project: WildFly Issue Type: Bug Components: Quickstarts Reporter: James Perkins Assignee: Radoslav Husar I noticed in the {{microprofile-fault-tolerance}} README there is a line that says to use {{mvn wildfly:run &}}. The {{&}} should really be removed as that will keep the maven process running in the background until the server is shutdown. That doesn't seem right to me. >From reading the instructions it does seem like the reason for this is because there are follow commands used to provision the server. There seems to be two options for this: # We use the {{standalone-microprofile.xml}} for the config file # We upgrade, I can release a final if needed, the maven plugin to 2.1.0.Beta1. * This would allow CLI commands to be executed before the deployment is deployed. [~rhusar] I've only assigned this to you as it looks to be a quickstart you created. I don't necessarily think you need to fix it, but your input would be helpful. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13275) Quickstart README documentation should not promote usage of using background jobs

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-13275?page=com.atlassian.jira.plugi... ] James Perkins updated WFLY-13275: --------------------------------- Description: I noticed in the {{microprofile-fault-tolerance}} README there is a line that says to use {{mvn wildfly:run &}}. The {{&}} should really be removed as that will keep the maven process running in the background until the server is shutdown. That doesn't seem right to me. >From reading the instructions it does seem like the reason for this is because there are follow commands used to provision the server. There seems to be two options for this: # -We use the {{standalone-microprofile.xml}} for the config file- Actually it's already doing this so maybe just the README needs to be updated. # We upgrade, I can release a final if needed, the maven plugin to 2.1.0.Beta1. * This would allow CLI commands to be executed before the deployment is deployed. [~rhusar] I've only assigned this to you as it looks to be a quickstart you created. I don't necessarily think you need to fix it, but your input would be helpful. was: I noticed in the {{microprofile-fault-tolerance}} README there is a line that says to use {{mvn wildfly:run &}}. The {{&}} should really be removed as that will keep the maven process running in the background until the server is shutdown. That doesn't seem right to me. >From reading the instructions it does seem like the reason for this is because there are follow commands used to provision the server. There seems to be two options for this: # We use the {{standalone-microprofile.xml}} for the config file # We upgrade, I can release a final if needed, the maven plugin to 2.1.0.Beta1. * This would allow CLI commands to be executed before the deployment is deployed. [~rhusar] I've only assigned this to you as it looks to be a quickstart you created. I don't necessarily think you need to fix it, but your input would be helpful. > Quickstart README documentation should not promote usage of using background jobs > --------------------------------------------------------------------------------- > > Key: WFLY-13275 > URL: https://issues.redhat.com/browse/WFLY-13275 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: James Perkins > Assignee: Radoslav Husar > Priority: Major > > I noticed in the {{microprofile-fault-tolerance}} README there is a line that says to use {{mvn wildfly:run &}}. The {{&}} should really be removed as that will keep the maven process running in the background until the server is shutdown. That doesn't seem right to me. > From reading the instructions it does seem like the reason for this is because there are follow commands used to provision the server. There seems to be two options for this: > # -We use the {{standalone-microprofile.xml}} for the config file- Actually it's already doing this so maybe just the README needs to be updated. > # We upgrade, I can release a final if needed, the maven plugin to 2.1.0.Beta1. > * This would allow CLI commands to be executed before the deployment is deployed. > [~rhusar] I've only assigned this to you as it looks to be a quickstart you created. I don't necessarily think you need to fix it, but your input would be helpful. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5139) [DMN Designer] Decision Navigator does not update Diagram name

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-5139?page=com.atlassian.jira.plug... ] Guilherme Gomes reassigned DROOLS-5139: --------------------------------------- Assignee: Yeser Amer (was: Guilherme Gomes) > [DMN Designer] Decision Navigator does not update Diagram name > -------------------------------------------------------------- > > Key: DROOLS-5139 > URL: https://issues.redhat.com/browse/DROOLS-5139 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.34.0.Final > Reporter: Michael Anstis > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > > Following changes for https://issues.redhat.com/browse/DROOLS-5137 it became evident that the Decision Navigator does not show updated Diagram names. > This pre-exists DROOLS-5137 and DROOLS-5060 (i.e. it is not a regression), so this new JIRA has been created. > * Create a new DMN Diagram > * Expand Decision Navigator > * Expand Properties Panel > * Select _background_ i.e. _diagram_ > * Change name in Properties Panel > * Decision Navigator does not update > * Saving, closing and re-opening diagram shows updated name -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13268) MP Fault Tolerance quickstart cannot resolve dependencies with wildfly-microprofile BOM

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13268?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13268: ---------------------------------- Summary: MP Fault Tolerance quickstart cannot resolve dependencies with wildfly-microprofile BOM (was: MP Fault Tolerance quickstart cannot resolve dependencies with wildlfy-microprofile BOM) > MP Fault Tolerance quickstart cannot resolve dependencies with wildfly-microprofile BOM > --------------------------------------------------------------------------------------- > > Key: WFLY-13268 > URL: https://issues.redhat.com/browse/WFLY-13268 > Project: WildFly > Issue Type: Bug > Components: BOM, MP Fault Tolerance, Quickstarts > Affects Versions: 19.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Fix For: 19.0.1.Final, 20.0.0.Beta1 > > > [~tterem] discovered that MP FT QS guide is followed from its README, it wont be able to resolve some dependencies. This is because we switched last minute to microprofile BOM which does not contain common dependencies. > For example, the microprofile-fault-tolerance QS will fails with > {code} > [ERROR] The project org.wildfly.quickstart.microprofile.faulttolerance:microprofile-fault-tolerance:1.0-SNAPSHOT (/Users/rhusar/Desktop/REAL_QS/microprofile-fault-tolerance/pom.xml) has 2 errors > [ERROR] 'dependencies.dependency.version' for org.jboss.resteasy:resteasy-jaxrs:jar is missing. @ line 34, column 21 > [ERROR] 'dependencies.dependency.version' for org.jboss.logging:jboss-logging:jar is missing. @ line 39, column 21 > {code} > We need to either continue the disucssion what needs to be in the microprofile BOM or import the other BOM into QS-s. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5056) [DMN Designer] Sometimes the nodes inside Decision Service are wrong positioned

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5056?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-5056: ----------------------------------- Story Points: 5 > [DMN Designer] Sometimes the nodes inside Decision Service are wrong positioned > ------------------------------------------------------------------------------- > > Key: DROOLS-5056 > URL: https://issues.redhat.com/browse/DROOLS-5056 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniel José dos Santos > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: issue.mp4, taxRate.dmn > > > Sometimes the nodes inside the Decision Service are positioned outside from the Decision Service when the .DMN is saved an open again. > I was unable to map exact when this happen, but I noticed that this happens depending on the changes you do in the position and size of the Decision Service and its inner nodes. > I recorded a video with 2 minutes when the issue happens in the last seconds. > As it can be notice it takes lots of trials to reproduce the issue. > Also I was unable to reproduce the issue in the Business Central, so I'm not sure if it is related to DMN Editor in VS Code or DMN Editor itself. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13269) The org.wildfly:wildfly-client-all artefact incorrectly contains the Elytron CDI extension

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13269?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-13269: ----------------------------------------- [~dlofthouse] This seems like a good candidate for 19.0.1 as well. > The org.wildfly:wildfly-client-all artefact incorrectly contains the Elytron CDI extension > ------------------------------------------------------------------------------------------ > > Key: WFLY-13269 > URL: https://issues.redhat.com/browse/WFLY-13269 > Project: WildFly > Issue Type: Bug > Components: Build System, MP JWT, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 20.0.0.Beta1 > > > This means if the artefact is included in a deployment the JWT activation is incorrectly triggered but with some dependencies missing leading to an error such as the following. > {code} > 09:46:44,391 WARN [org.jboss.modules.define] (MSC service thread 1-1) Failed to define class org.wildfly.security.mp.jwt.JWTCDIExtension in Module "deployment.XXXX.ear" from Service Module Loader: java.lang.NoClassDefFoundError: Failed to link org/wildfly/security/mp/jwt/JWTCDIExtension (Module "deployment.XXXX.ear" from Service Module Loader): io/smallrye/jwt/auth/cdi/SmallRyeJWTAuthCDIExtension > at java.lang.ClassLoader.defineClass1(ClassLoader.java) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 March 2020