[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][~karreiro] In recent mocks, I've included an option to have the preview map show/reveal using a check box control, as a means to save space.
!Screen Shot 2019-02-01 at 10.52.51 AM.png|thumbnail!
Just wanted to see what you thought about this. Related to this, is there any way we could suppress showing the old "explorer" tree in the right pane? It seems redundant with our "Navigator" explorer.
!Screen Shot 2019-01-31 at 9.45.39 AM.png|thumbnail!
> 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, Screen Shot 2019-02-01 at 10.52.51 AM.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)
6 years, 11 months
[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 updated DROOLS-3565:
--------------------------------
Attachment: Screen Shot 2019-02-01 at 10.52.51 AM.png
> 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, Screen Shot 2019-01-31 at 9.45.39 AM.png, Screen Shot 2019-02-01 at 10.52.51 AM.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)
6 years, 11 months
[JBoss JIRA] (WFLY-11664) EJB client is unable to discover EJB after WildFly crash during previous call and reboot
by Ivan Straka (Jira)
[ https://issues.jboss.org/browse/WFLY-11664?page=com.atlassian.jira.plugin... ]
Ivan Straka updated WFLY-11664:
-------------------------------
Description:
Lets have two WildFly servers and same EJB on both. They have nothing to do with each other.
*Scenario*
# client invoke method on both beans and the first called server crash during invocation
# 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.
*Client side*
{code:java}
public static void main(String[] args)
throws Exception {
call("server-2", true);
call("server-1", true);
for (int i = 30; i > 0; i--) {
System.out.println(i);
Thread.sleep(1000);
}
call("server-1", false);
}
public static Properties getCtxProperties() {
Properties props = new Properties();
props.put(Context.INITIAL_CONTEXT_FACTORY, "org.wildfly.naming.client.WildFlyInitialContextFactory");
return props;
}
public static void call(String container, boolean exceptedFailure) {
try {
InitialContext ctx = new InitialContext(getCtxProperties());
String lookupName = "ejb:/" + container + "/HelloBean!ejb.HelloBeanRemote";
HelloBeanRemote bean = (HelloBeanRemote) ctx.lookup(lookupName);
System.out.println(bean.hello());
} catch (Exception e) {
if (exceptedFailure) {
System.out.println("EXPECTED FAILURE");
e.printStackTrace();
} else {
throw new RuntimeException(e);
}
}
}
{code}
*Server side*
{code:java}
@Stateless
@Remote(HelloBeanRemote.class)
public class HelloBean {
private static Logger log = Logger.getLogger(HelloBean.class);
public String hello() throws RemoteException {
log.info("hello called with message");
return "Hello there";
}
}
{code}
was:
Lets have two WildFly servers and same EJB on both. They have nothing to do with each other.
*Scenario*
# client invoke method on both beans and the first called server crash during invocation
# 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.
> 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: 14.0.0.Final, 15.0.0.Final
> Reporter: Ivan Straka
> Priority: Blocker
> 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 beans and the first called server crash during invocation
> # 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.
> *Client side*
> {code:java}
> public static void main(String[] args)
> throws Exception {
> call("server-2", true);
> call("server-1", true);
> for (int i = 30; i > 0; i--) {
> System.out.println(i);
> Thread.sleep(1000);
> }
> call("server-1", false);
> }
> public static Properties getCtxProperties() {
> Properties props = new Properties();
> props.put(Context.INITIAL_CONTEXT_FACTORY, "org.wildfly.naming.client.WildFlyInitialContextFactory");
> return props;
> }
> public static void call(String container, boolean exceptedFailure) {
> try {
> InitialContext ctx = new InitialContext(getCtxProperties());
> String lookupName = "ejb:/" + container + "/HelloBean!ejb.HelloBeanRemote";
> HelloBeanRemote bean = (HelloBeanRemote) ctx.lookup(lookupName);
> System.out.println(bean.hello());
> } catch (Exception e) {
> if (exceptedFailure) {
> System.out.println("EXPECTED FAILURE");
> e.printStackTrace();
> } else {
> throw new RuntimeException(e);
> }
> }
> }
> {code}
> *Server side*
> {code:java}
> @Stateless
> @Remote(HelloBeanRemote.class)
> public class HelloBean {
> private static Logger log = Logger.getLogger(HelloBean.class);
> public String hello() throws RemoteException {
> log.info("hello called with message");
> return "Hello there";
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-11664) EJB client is unable to discover EJB after WildFly crash during previous call and reboot
by Ivan Straka (Jira)
[ https://issues.jboss.org/browse/WFLY-11664?page=com.atlassian.jira.plugin... ]
Ivan Straka updated WFLY-11664:
-------------------------------
Description:
Lets have two WildFly servers and same EJB on both. They have nothing to do with each other.
*Scenario*
# client invoke method on both beans and the first called server crash during invocation
# 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.
was:
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.
> 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: 14.0.0.Final, 15.0.0.Final
> Reporter: Ivan Straka
> Priority: Blocker
> 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 beans and the first called server crash during invocation
> # 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)
6 years, 11 months
[JBoss JIRA] (WFLY-11664) EJB client is unable to discover EJB after WildFly crash during previous call and reboot
by Ivan Straka (Jira)
[ https://issues.jboss.org/browse/WFLY-11664?page=com.atlassian.jira.plugin... ]
Ivan Straka updated WFLY-11664:
-------------------------------
Steps to Reproduce:
# Download & unzip reproducer
# unzip 2x WildFly distribution
# build server
# deploy server-side app as server-1.jar to the first server and run:
{code:bash}
export JAVA_OPTS="-Djboss.modules.system.pkgs=path-to-byteman.jar=script:path-to-HelloBeanCrash.btm"
./bin/standalone.sh -c standalone-full.xml
{code}
# deploy server-side app as server-2.jar to the second server and run:
{code:bash}
./bin/standalone.sh -c standalone-full.xml -Djboss.socket.binding.port-offset=100
{code}
# run client-side app side
{code:bash}
mvn package exec:exec
{code}
# during countdown (you have 30 seconds) run on the first:
{code:bash}
unset JAVA_OPTS
./bin/standalone.sh -c standalone-full.xml
{code}
was:
# Download & unzip reproducer
# unzip 2x WildFly distribution
# build server
# run on the first :
{code:bash}
export JAVA_OPTS="-Djboss.modules.system.pkgs=path-to-byteman.jar=script:path-to-HelloBeanCrash.btm"
./bin/standalone.sh -c standalone-full.xml
deploy server-side app as server-1.jar
{code}
# run on the second:
{code:bash}
./bin/standalone.sh -c standalone-full.xml -Djboss.socket.binding.port-offset=100
deploy server-side app as server-2.jar
{code}
# run client-side app side using mvn package exec:exec
# during countdown (you have 30 seconds) run on the first:
{code:bash}
unset JAVA_OPTS
./bin/standalone.sh -c standalone-full.xml
{code}
> 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: 14.0.0.Final, 15.0.0.Final
> Reporter: Ivan Straka
> Priority: Blocker
> 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)
6 years, 11 months
[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)
6 years, 11 months
[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)
6 years, 11 months
[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)
6 years, 11 months
[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)
6 years, 11 months