February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11664) EJB client is unable to discover EJB after WildFly crash during previous call and reboot

by Ivan Straka (Jira)

Ivan Straka created WFLY-11664: ---------------------------------- Summary: EJB client is unable to discover EJB after WildFly crash during previous call and reboot Key: WFLY-11664 URL: https://issues.jboss.org/browse/WFLY-11664 Project: WildFly Issue Type: Bug Components: EJB, Remoting Affects Versions: 15.0.0.Final, 14.0.0.Final Reporter: Ivan Straka Attachments: reproducer.zip Lets have two WildFly servers and same EJB on both. They have nothing to do with each other. *Scenario* # client invoke method on both EJB and the first called server crash during invokation # after the server reboots, client is unable to discover EJB on the server {code:java}Exception in thread "main" java.lang.RuntimeException: javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "/server-1/HelloBean", view is interface ejb.HelloBeanRemote, affinity is None at client.Client.call(Client.java:41) at client.Client.main(Client.java:21) Caused by: javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "/server-1/HelloBean", view is interface ejb.HelloBeanRemote, affinity is None at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:592) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528) at org.jboss.ejb.protocol.remote.RemotingEJBClientInterceptor.handleInvocationResult(RemotingEJBClientInterceptor.java:56) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:594) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528) at org.jboss.ejb.client.TransactionPostDiscoveryInterceptor.handleInvocationResult(TransactionPostDiscoveryInterceptor.java:133) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:594) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528) at org.jboss.ejb.client.DiscoveryEJBClientInterceptor.handleInvocationResult(DiscoveryEJBClientInterceptor.java:115) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:594) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528) at org.jboss.ejb.client.NamingEJBClientInterceptor.handleInvocationResult(NamingEJBClientInterceptor.java:79) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:594) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528) at org.jboss.ejb.client.TransactionInterceptor.handleInvocationResult(TransactionInterceptor.java:172) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:594) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528) at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:938) at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:177) at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:112) at com.sun.proxy.$Proxy0.hello(Unknown Source) at client.Client.call(Client.java:35) ... 1 more {code} I hit this issue with 15.0.0.Final, 14.0.0.Final but not with 12.0.0.Final. If client try to invoke bean on the first server before it reboots, there is no problem after. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3565) DMN: Navigator panel UX updates

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3565?page=com.atlassian.jira.plugi... ] Liz Clayton edited comment on DROOLS-3565 at 2/1/19 9:25 AM: ------------------------------------------------------------- [~manstis] Thanks for the info., my take-away is that for dev code recycling isn't worthwhile with this? From my end, I'd just like to use the visual styling for the Components menu list items, because I think they convey drag-n-drop interactivity plus replicating that style would offer some visual consistency. [~karreiro] would you be able to pick up the visual styles for the list items, or replicate them? Let me know, thanks. was (Author: uxdlc): [~manstis] Thanks for the info., my take-away is that for dev code recycling isn't worthwhile with this? From my end, I'd just like to use the visual styling for the Components menu list items, because I think they convey drag-n-drop interactivity plus replicating that style would offer some visual consistency. [~karreiro] would you be able to pick up the visual styles for the list items, or replicate them? Thanks > DMN: Navigator panel UX updates > ------------------------------- > > Key: DROOLS-3565 > URL: https://issues.jboss.org/browse/DROOLS-3565 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UXTeam, drools-tools > Attachments: Screen Shot 2019-01-28 at 1.38.21 PM.png, Screen Shot 2019-01-28 at 2.35.00 PM.png > > > As a user I want to be able to be able to view and use imported nodes and decision logic in the diagram that I am authoring. > Based on card view design (see linked jira), detail new Navigator elements required to support this workflow including: > - Import components panel: Filter components by BKMs, decisions..., badge count > - Graph panel with checkbox option to view map. > - Single scrolling navigator. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3565) DMN: Navigator panel UX updates

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3565?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3565: ------------------------------------- [~manstis] Thanks for the info., my take-away is that for dev code recycling isn't worthwhile with this? From my end, I'd just like to use the visual styling for the Components menu list items, because I think they convey drag-n-drop interactivity plus replicating that style would offer some visual consistency. [~karreiro] would you be able to pick up the visual styles for the list items, or replicate them? Thanks > DMN: Navigator panel UX updates > ------------------------------- > > Key: DROOLS-3565 > URL: https://issues.jboss.org/browse/DROOLS-3565 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UXTeam, drools-tools > Attachments: Screen Shot 2019-01-28 at 1.38.21 PM.png, Screen Shot 2019-01-28 at 2.35.00 PM.png > > > As a user I want to be able to be able to view and use imported nodes and decision logic in the diagram that I am authoring. > Based on card view design (see linked jira), detail new Navigator elements required to support this workflow including: > - Import components panel: Filter components by BKMs, decisions..., badge count > - Graph panel with checkbox option to view map. > - Single scrolling navigator. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3566) Contextual menus for canvas nodes - imported.

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3566?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3566: ------------------------------------- [~manstis] Yes exactly! Glad the canvas option is viable, thanks. > Contextual menus for canvas nodes - imported. > ---------------------------------------------- > > Key: DROOLS-3566 > URL: https://issues.jboss.org/browse/DROOLS-3566 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UXTeam, drools-tools > Attachments: contextual-menu.png > > > Canvas node actions related to imported components. > As a user I want to easily select and group nodes on the canvas so that I can add them to a DRD or to create a new DRD. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3000) Design data type constraints UX

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3000?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3000: -------------------------------- Attachment: General_specs.pdf > Design data type constraints UX > -------------------------------- > > Key: DROOLS-3000 > URL: https://issues.jboss.org/browse/DROOLS-3000 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: General_specs.pdf, pop-overc.png, pop-overcSpecs.png, select.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E... > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3000) Design data type constraints UX

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3000?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3000: -------------------------------- Attachment: (was: General_specs.pdf) > Design data type constraints UX > -------------------------------- > > Key: DROOLS-3000 > URL: https://issues.jboss.org/browse/DROOLS-3000 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: General_specs.pdf, pop-overc.png, pop-overcSpecs.png, select.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E... > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-575) UI automation - Modify test_about to support Maistra

by Sunil kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-575?page=com.atlassian.jira.plugin.... ] Sunil kondkar resolved SWSQE-575. --------------------------------- Resolution: Done PR merged > UI automation - Modify test_about to support Maistra > ---------------------------------------------------- > > Key: SWSQE-575 > URL: https://issues.jboss.org/browse/SWSQE-575 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Sunil kondkar > Priority: Major > > Currently 'test_about' is designed for Istio upstream versions only. > Modify it to support also running on Maistra projects, so do not fail in both cases. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-575) UI automation - Modify test_about to support Maistra

by Sunil kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-575?page=com.atlassian.jira.plugin.... ] Sunil kondkar commented on SWSQE-575: ------------------------------------- PR: https://github.com/Kiali-QE/kiali-qe-python/pull/137 > UI automation - Modify test_about to support Maistra > ---------------------------------------------------- > > Key: SWSQE-575 > URL: https://issues.jboss.org/browse/SWSQE-575 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Sunil kondkar > Priority: Major > > Currently 'test_about' is designed for Istio upstream versions only. > Modify it to support also running on Maistra projects, so do not fail in both cases. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-575) UI automation - Modify test_about to support Maistra

by Sunil kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-575?page=com.atlassian.jira.plugin.... ] Sunil kondkar reassigned SWSQE-575: ----------------------------------- Assignee: Sunil kondkar (was: Michael Foley) > UI automation - Modify test_about to support Maistra > ---------------------------------------------------- > > Key: SWSQE-575 > URL: https://issues.jboss.org/browse/SWSQE-575 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Sunil kondkar > Priority: Major > > Currently 'test_about' is designed for Istio upstream versions only. > Modify it to support also running on Maistra projects, so do not fail in both cases. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-581) Add PQI Filter To QE Jira Board

by Matt Mahoney (Jira)

Matt Mahoney created SWSQE-581: ---------------------------------- Summary: Add PQI Filter To QE Jira Board Key: SWSQE-581 URL: https://issues.jboss.org/browse/SWSQE-581 Project: Kiali QE Issue Type: QE Task Reporter: Matt Mahoney Assignee: Michael Foley -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 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 February 2019