April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3932) [DMN Designer] Replace BPMN specific parsing error message

by Michael Anstis (Jira)

Michael Anstis created DROOLS-3932: -------------------------------------- Summary: [DMN Designer] Replace BPMN specific parsing error message Key: DROOLS-3932 URL: https://issues.jboss.org/browse/DROOLS-3932 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.20.0.Final Reporter: Michael Anstis Assignee: Michael Anstis When opening an invalid DMN file (one that fails parsing) the editor displays the error message "An error was produced during process diagram parsing. There might be bpm nodes not yet supported by current Process Designer version, or the xml content can contain errors. You can try to open the file with the Legacy Process Designer or repair it manually". This needs changing to something more DMN friendly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7189) UT000010: Session not found

by Alpesh Jikadra (Jira)

[ https://issues.jboss.org/browse/WFLY-7189?page=com.atlassian.jira.plugin.... ] Alpesh Jikadra commented on WFLY-7189: -------------------------------------- I was not able to reproduce the same, This is a web application so one suspect could be the client session, My application uses database connection based on the session scope (session maintain which db need to access), I suspect it like a concurrency issue with session and getting db connection, So if client is try to logout, and in some other table if any ajax call is executing with some interval, then I saw the same error, but not always, So I made changes like instead of removing session from server I have just clear the cookie from the client machine, so with this implementation session is still available on server till expiry, so after this implementation I never see this error. > UT000010: Session not found > --------------------------- > > Key: WFLY-7189 > URL: https://issues.jboss.org/browse/WFLY-7189 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 9.0.2.Final > Environment: Production > Reporter: Alpesh Jikadra > Assignee: Jason Greene > Priority: Critical > Labels: wildfly > > In my application I am using 4 different database connection with spring, > Before upgrading to wildfly 9.0.2 Final it was working fine, but yesterday from production I came to know that one database is not able to connect. and giving following exception > {code:java} > Caused by: java.lang.IllegalStateException: UT000010: Session not found ONaa4NC8R3y3WuYRhMjp5kD0__MXIkMtHbginKOx > INFO | jvm 1 | 2016/09/21 05:53:09 | at io.undertow.server.session.InMemorySessionManager$SessionImpl.getAttribute(InMemorySessionManager.java:430) > INFO | jvm 1 | 2016/09/21 05:53:09 | at io.undertow.servlet.spec.HttpSessionImpl.getAttribute(HttpSessionImpl.java:123) > INFO | jvm 1 | 2016/09/21 05:53:09 | at org.springframework.web.util.WebUtils.getSessionMutex(WebUtils.java:328) > INFO | jvm 1 | 2016/09/21 05:53:09 | at org.springframework.web.context.request.ServletRequestAttributes.getSessionMutex(ServletRequestAttributes.java:191) > INFO | jvm 1 | 2016/09/21 05:53:09 | at org.springframework.web.context.request.SessionScope.get(SessionScope.java:88) > INFO | jvm 1 | 2016/09/21 05:53:09 | at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:285) > {code} > While, I was able to connect to other databases through the application, only facing issues for accessing one of the database. > After restart of wildfly server issue is resolved, Even I am not able to reproduce it > [OpenIssue|[#https://developer.jboss.org/message/949465#949465]] -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3883) Add running indicator during test scenario execution

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3883?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3883: --------------------------------- Story Points: 2 > Add running indicator during test scenario execution > ---------------------------------------------------- > > Key: DROOLS-3883 > URL: https://issues.jboss.org/browse/DROOLS-3883 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > > When user runs a test there is no indicator while it runs -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4437) Deprecate RuntimeCapability.fromBaseCapability(String) and buildDynamicCapabilityName(String, String)

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFCORE-4437?page=com.atlassian.jira.plugi... ] Paul Ferraro commented on WFCORE-4437: -------------------------------------- On second look, these methods can't really be deprecated, as they are superseded by vararg methods variants. Thus they can't be deprecated without causing false positive deprecation warnings and can't be removed without breaking binary compatibility. > Deprecate RuntimeCapability.fromBaseCapability(String) and buildDynamicCapabilityName(String, String) > ----------------------------------------------------------------------------------------------------- > > Key: WFCORE-4437 > URL: https://issues.jboss.org/browse/WFCORE-4437 > Project: WildFly Core > Issue Type: Task > Components: Management > Affects Versions: 9.0.0.Beta3 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > These methods predate the dynamic capability name mapping functionality and should be phased out. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3922) Import of external classes in Test Scenario doesn't work until you have a class in your package

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3922?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3922: --------------------------------- Story Points: 3 (was: 5) > Import of external classes in Test Scenario doesn't work until you have a class in your package > ----------------------------------------------------------------------------------------------- > > Key: DROOLS-3922 > URL: https://issues.jboss.org/browse/DROOLS-3922 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > Attachments: Prequalification.dmn > > > Import of external classes in Test Scenario doesn't work until you have a class in your package. > If you import an Integer or similar, you will not find it in the right panel until you create a custom DO in your same package -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3742) Implement Test scenario coverage report for DMN

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3742?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3742: --------------------------------- Story Points: 3 (was: 8) > Implement Test scenario coverage report for DMN > ----------------------------------------------- > > Key: DROOLS-3742 > URL: https://issues.jboss.org/browse/DROOLS-3742 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > > Use this ticket as specs > https://issues.jboss.org/browse/DROOLS-3516 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4437) Deprecate RuntimeCapability.fromBaseCapability(String) and buildDynamicCapabilityName(String, String)

by Paul Ferraro (Jira)

Paul Ferraro created WFCORE-4437: ------------------------------------ Summary: Deprecate RuntimeCapability.fromBaseCapability(String) and buildDynamicCapabilityName(String, String) Key: WFCORE-4437 URL: https://issues.jboss.org/browse/WFCORE-4437 Project: WildFly Core Issue Type: Task Components: Management Affects Versions: 9.0.0.Beta3 Reporter: Paul Ferraro Assignee: Paul Ferraro These methods predate the dynamic capability name mapping functionality and should be phased out. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-721) Try UI Automations with other resolutions

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-721: ------------------------------------ Summary: Try UI Automations with other resolutions Key: SWSQE-721 URL: https://issues.jboss.org/browse/SWSQE-721 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan Currently UI Automations are fixed to run on 1920*1080 resolution. Try to run them in smaller resolutions: 1440 x 900 1280*1080 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3894) Decision Nodes not correctly anchored in Decision Service when using keyboard arrows to move nodes

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3894?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3894: ----------------------------------- Labels: stunner (was: drools-tools stunner) > Decision Nodes not correctly anchored in Decision Service when using keyboard arrows to move nodes > -------------------------------------------------------------------------------------------------- > > Key: DROOLS-3894 > URL: https://issues.jboss.org/browse/DROOLS-3894 > Project: Drools > Issue Type: Bug > Components: Stunner > Affects Versions: 7.18.0.Final, 7.20.0.Final > Environment: RHPAM 7.3.0.GA > Reporter: Duncan Doyle > Assignee: Michael Anstis > Priority: Major > Labels: stunner > > If you use a Decision Service, and put Decision Nodes in the service box, the anchoring of the nodes in that service is messed up when you start moving around the nodes using the arrow keys on your keyboard. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3894) Decision Nodes not correctly anchored in Decision Service when using keyboard arrows to move nodes

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3894?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-3894: -------------------------------------- Assignee: Roger Martinez (was: Michael Anstis) > Decision Nodes not correctly anchored in Decision Service when using keyboard arrows to move nodes > -------------------------------------------------------------------------------------------------- > > Key: DROOLS-3894 > URL: https://issues.jboss.org/browse/DROOLS-3894 > Project: Drools > Issue Type: Bug > Components: Stunner > Affects Versions: 7.18.0.Final, 7.20.0.Final > Environment: RHPAM 7.3.0.GA > Reporter: Duncan Doyle > Assignee: Roger Martinez > Priority: Major > Labels: stunner > > If you use a Decision Service, and put Decision Nodes in the service box, the anchoring of the nodes in that service is messed up when you start moving around the nodes using the arrow keys on your keyboard. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2019