March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2418) [DMN Designer] New diagram can't be created

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2418?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2418: ------------------------------------- I suspect JBPM-6968 to cause this. > [DMN Designer] New diagram can't be created > ------------------------------------------- > > Key: DROOLS-2418 > URL: https://issues.jboss.org/browse/DROOLS-2418 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Fix For: 7.7.0.Final > > Attachments: Screenshot from 2018-03-26 10-04-20.png, Screenshot from 2018-03-26 10-04-27.png > > > User is unable to create new diagram. Always Create button is hit, some error dialogue appears. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2418) [DMN Designer] New diagram can't be created

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2418?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2418: ----------------------------------- Sprint: 2018 Week 11-12 > [DMN Designer] New diagram can't be created > ------------------------------------------- > > Key: DROOLS-2418 > URL: https://issues.jboss.org/browse/DROOLS-2418 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Fix For: 7.7.0.Final > > Attachments: Screenshot from 2018-03-26 10-04-20.png, Screenshot from 2018-03-26 10-04-27.png > > > User is unable to create new diagram. Always Create button is hit, some error dialogue appears. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2418) [DMN Designer] New diagram can't be created

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2418?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2418: -------------------------------- Fix Version/s: 7.7.0.Final > [DMN Designer] New diagram can't be created > ------------------------------------------- > > Key: DROOLS-2418 > URL: https://issues.jboss.org/browse/DROOLS-2418 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Fix For: 7.7.0.Final > > Attachments: Screenshot from 2018-03-26 10-04-20.png, Screenshot from 2018-03-26 10-04-27.png > > > User is unable to create new diagram. Always Create button is hit, some error dialogue appears. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2418) [DMN Designer] New diagram can't be created

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2418: ----------------------------------- Summary: [DMN Designer] New diagram can't be created Key: DROOLS-2418 URL: https://issues.jboss.org/browse/DROOLS-2418 Project: Drools Issue Type: Bug Components: DMN Editor Reporter: Jozef Marko Assignee: Michael Anstis Priority: Blocker Attachments: Screenshot from 2018-03-26 10-04-20.png, Screenshot from 2018-03-26 10-04-27.png User is unable to create new diagram. Always Create button is hit, some error dialogue appears. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10101) [Artemis 2.x upgrade] Unexptected crash of server in SOAK test

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-10101?page=com.atlassian.jira.plugin... ] Miroslav Novak updated WFLY-10101: ---------------------------------- Description: After ~13 hours there is unexpected crash of one server in SOAK test. There is no error/warning in the logs. Test Scenario: * Start 2 servers * Client sends messages to input queue. Messages then go through: * One server to another through MDB reading and sending them from remote container through resource adapter * Messages are forwarded from one server to another over JMS bridge and back over Core bridge * Messages have JMSReplyTo defined with a temporary queue, that is filled with responses for the client * Messages are read from the destination with stateless EJB and sent back to clients * Client reads the messages after the pass through all the soak modules. Pass Criteria: In the last step receiver consumes all messages sent by producer. Actual Result: After ~13 hours 1st server suddenly crashes. There is no error/warning in server logs. Issue was hit with Artemis 2.5.0 with https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (commit 51dd8102f103ccb0470a3cfc8713d3f9bdb1b65d) was: After ~13 hours there is unexpected crash of one server in SOAK test. There is no error/warning in the logs. Test Scenario: * Start 2 servers * Client sends messages to input queue. Messages then go through: * One server to another through MDB reading and sending them from remote container through resource adapter * Messages are forwarded from one server to another over JMS bridge and back over Core bridge * Messages have JMSReplyTo defined with a temporary queue, that is filled with responses for the client * Messages are read from the destination with stateless EJB and sent back to clients * Client reads the messages after the pass through all the soak modules. Pass Criteria: In the last step receiver consumes all messages sent by producer. Actual Result: After ~13 hours 1st server suddenly crashes. There is no error/warning in server logs. > [Artemis 2.x upgrade] Unexptected crash of server in SOAK test > -------------------------------------------------------------- > > Key: WFLY-10101 > URL: https://issues.jboss.org/browse/WFLY-10101 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Priority: Blocker > > After ~13 hours there is unexpected crash of one server in SOAK test. There is no error/warning in the logs. > Test Scenario: > * Start 2 servers > * Client sends messages to input queue. Messages then go through: > * One server to another through MDB reading and sending them from remote container through resource adapter > * Messages are forwarded from one server to another over JMS bridge and back over Core bridge > * Messages have JMSReplyTo defined with a temporary queue, that is filled with responses for the client > * Messages are read from the destination with stateless EJB and sent back to clients > * Client reads the messages after the pass through all the soak modules. > Pass Criteria: In the last step receiver consumes all messages sent by producer. > Actual Result: > After ~13 hours 1st server suddenly crashes. There is no error/warning in server logs. > Issue was hit with Artemis 2.5.0 with https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (commit 51dd8102f103ccb0470a3cfc8713d3f9bdb1b65d) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10101) [Artemis 2.x upgrade] Unexptected crash of server in SOAK test

by Miroslav Novak (JIRA)

Miroslav Novak created WFLY-10101: ------------------------------------- Summary: [Artemis 2.x upgrade] Unexptected crash of server in SOAK test Key: WFLY-10101 URL: https://issues.jboss.org/browse/WFLY-10101 Project: WildFly Issue Type: Bug Components: JMS Reporter: Miroslav Novak Assignee: Jeff Mesnil Priority: Blocker After ~13 hours there is unexpected crash of one server in SOAK test. There is no error/warning in the logs. Test Scenario: * Start 2 servers * Client sends messages to input queue. Messages then go through: * One server to another through MDB reading and sending them from remote container through resource adapter * Messages are forwarded from one server to another over JMS bridge and back over Core bridge * Messages have JMSReplyTo defined with a temporary queue, that is filled with responses for the client * Messages are read from the destination with stateless EJB and sent back to clients * Client reads the messages after the pass through all the soak modules. Pass Criteria: In the last step receiver consumes all messages sent by producer. Actual Result: After ~13 hours 1st server suddenly crashes. There is no error/warning in server logs. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-67) [QE] SWS-166

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-67?page=com.atlassian.jira.plugin.s... ] Hayk Hovsepyan updated SWSQE-67: -------------------------------- Sprint: SWS QE Sprint 2, Kiali QE Sprint 3 (was: SWS QE Sprint 2) > [QE] SWS-166 > ------------ > > Key: SWSQE-67 > URL: https://issues.jboss.org/browse/SWSQE-67 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > > Select the time span for the Service Graph page > [link title|https://issues.jboss.org/browse/SWS-166] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-58) [QE] - SWS-118 - Show metrics as charts

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-58?page=com.atlassian.jira.plugin.s... ] Hayk Hovsepyan updated SWSQE-58: -------------------------------- Sprint: SWS QE Sprint 2, Kiali QE Sprint 3 (was: SWS QE Sprint 2) > [QE] - SWS-118 - Show metrics as charts > --------------------------------------- > > Key: SWSQE-58 > URL: https://issues.jboss.org/browse/SWSQE-58 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Prachi Yadav > > Take a look into subtasks as well: > https://issues.jboss.org/browse/SWS-118 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-57) [QE] - SWS-170 - Embedded Jaeger UI

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-57?page=com.atlassian.jira.plugin.s... ] Hayk Hovsepyan updated SWSQE-57: -------------------------------- Sprint: SWS QE Sprint 2, Kiali QE Sprint 3 (was: SWS QE Sprint 2) > [QE] - SWS-170 - Embedded Jaeger UI > ----------------------------------- > > Key: SWSQE-57 > URL: https://issues.jboss.org/browse/SWSQE-57 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Michael Foley > > Look into Dev Task/Story https://issues.jboss.org/browse/SWS-170 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10077) [Artemis 2.x upgrade] journal-node-manager-store-table attribute does not preserve its value

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-10077?page=com.atlassian.jira.plugin... ] Miroslav Novak commented on WFLY-10077: --------------------------------------- Thanks [~jmesnil], it's ok now. > [Artemis 2.x upgrade] journal-node-manager-store-table attribute does not preserve its value > --------------------------------------------------------------------------------------------- > > Key: WFLY-10077 > URL: https://issues.jboss.org/browse/WFLY-10077 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Priority: Blocker > > Writing to {{journal-node-manager-store-table}} attribute does not preserver its value and after restart default value is set again. > Output from CLI: > {code} > [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default:read-attribute(name=journal-node-manager-store-table) > { > "outcome" => "success", > "result" => "NODE_MANAGER_STORE_NODE_1", > "response-headers" => {"process-state" => "reload-required"} > } > ...restart server here > [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default:read-attribute(name=journal-node-manager-store-table) > { > "outcome" => "success", > "result" => "NODE_MANAGER_STORE" > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 2018