[JBoss JIRA] (WFLY-10087) EJB uses the same remote outbound connection all the time
by Ivan Straka (JIRA)
[ https://issues.jboss.org/browse/WFLY-10087?page=com.atlassian.jira.plugin... ]
Ivan Straka updated WFLY-10087:
-------------------------------
Summary: EJB uses the same remote outbound connection all the time (was: Bean uses the same remote outbound connection all the time)
> EJB uses the same remote outbound connection all the time
> ---------------------------------------------------------
>
> Key: WFLY-10087
> URL: https://issues.jboss.org/browse/WFLY-10087
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Remoting
> Affects Versions: 12.0.0.Final
> Reporter: Ivan Straka
> Attachments: client-side.war, server-side-slave1.jar, server-side-slave2.jar
>
>
> Lets have three servers master, slave1, slave2. Master has two remote outbound connection defined that point to slave1 and slave2.
> When the EJB deployed to master needs to call two EJB (slave1 and slave2), the first call is successful, but the second one is not becaus the EJB uses remote outbound connection that points to slave1 (instead of slave2).
> This results to the followinf exception:
> {code:java}
> 14:28:18,914 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /client-side/: javax.ejb.EJBException: java.lang.RuntimeException: javax.ejb.NoSuchEJBException: No such EJB: /server-side-slave2/WhoAmIBean @ http-remoting://localhost:8180
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:186)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:330)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:238)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
> at org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:72)
> at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438)
> at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:619)
> at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
> at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198)
> at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185)
> at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:81)
> at example.BeanRemote$$$view1.callNext(Unknown Source)
> at example.ClientServlet.doGet(ClientServlet.java:36)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74)
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
> at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:67)
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
> at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
> at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
> at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
> at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
> at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1526)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1526)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1526)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1526)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.RuntimeException: javax.ejb.NoSuchEJBException: No such EJB: /server-side-slave2/WhoAmIBean @ http-remoting://localhost:8180
> at example.Bean.callNext(Bean.java:23)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
> at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:90)
> at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:101)
> at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:40)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
> at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:273)
> ... 78 more
> Caused by: javax.ejb.NoSuchEJBException: No such EJB: /server-side-slave2/WhoAmIBean @ http-remoting://localhost:8180
> at org.jboss.ejb.protocol.remote.EJBClientChannel$MethodInvocation.handleResponse(EJBClientChannel.java:1070)
> at org.jboss.ejb.protocol.remote.EJBClientChannel$MethodInvocation.handleResponse(EJBClientChannel.java:997)
> at org.jboss.remoting3.util.InvocationTracker.signalResponse(InvocationTracker.java:167)
> at org.jboss.ejb.protocol.remote.EJBClientChannel.processMessage(EJBClientChannel.java:186)
> at org.jboss.ejb.protocol.remote.EJBClientChannel.access$100(EJBClientChannel.java:112)
> at org.jboss.ejb.protocol.remote.EJBClientChannel$1$1.handleMessage(EJBClientChannel.java:675)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:926)
> ... 5 more
> Suppressed: javax.ejb.NoSuchEJBException: No such EJB: /server-side-slave2/WhoAmIBean @ http-remoting://localhost:8180
> ... 13 more
> Suppressed: javax.ejb.NoSuchEJBException: No such EJB: /server-side-slave2/WhoAmIBean @ http-remoting://localhost:8180
> ... 13 more
> Suppressed: javax.ejb.NoSuchEJBException: No such EJB: /server-side-slave2/WhoAmIBean @ http-remoting://localhost:8180
> ... 13 more
> Suppressed: javax.ejb.NoSuchEJBException: No such EJB: /server-side-slave2/WhoAmIBean @ http-remoting://localhost:8180
> ... 13 more
> Suppressed: javax.ejb.NoSuchEJBException: No such EJB: /server-side-slave2/WhoAmIBean @ http-remoting://localhost:8180
> ... 13 more
> Suppressed: javax.ejb.NoSuchEJBException: No such EJB: /server-side-slave2/WhoAmIBean @ http-remoting://localhost:8180
> at org.jboss.ejb.protocol.remote.EJBClientChannel$MethodInvocation.handleResponse(EJBClientChannel.java:1070)
> at org.jboss.ejb.protocol.remote.EJBClientChannel$MethodInvocation.handleResponse(EJBClientChannel.java:997)
> at org.jboss.remoting3.util.InvocationTracker.signalResponse(InvocationTracker.java:167)
> at org.jboss.ejb.protocol.remote.EJBClientChannel.processMessage(EJBClientChannel.java:186)
> at org.jboss.ejb.protocol.remote.EJBClientChannel.access$100(EJBClientChannel.java:112)
> at org.jboss.ejb.protocol.remote.EJBClientChannel$1$1.handleMessage(EJBClientChannel.java:675)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$receiveMessage$2(RemoteConnectionChannel.java:361)
> ... 6 more
> Suppressed: javax.ejb.NoSuchEJBException: No such EJB: /server-side-slave2/WhoAmIBean @ http-remoting://localhost:8180
> ... 13 more
> Suppressed: javax.ejb.NoSuchEJBException: No such EJB: /server-side-slave2/WhoAmIBean @ http-remoting://localhost:8180
> ... 13 more
> {code}
> Server side EJB (slave1, slave2) are simple:
> {code:java}
> @Stateless
> public class WhoAmIBean implements WhoAmIBeanRemote {
> @Override
> public String whoAmI() {
> String s = "WhoAmIBean.whoAmI called on server with port-offset " + System.getProperty("jboss.socket.binding.port-offset");
> System.out.println(s);
> return s;
> }
> }
> {code}
> Client side war (master) is simple servlet and EJB that performs calls.
> {code:java}
> @WebServlet(urlPatterns = "/")
> public class ClientServlet extends HttpServlet {
> @EJB
> private BeanRemote bean;
> @Override
> protected void doGet(HttpServletRequest req, HttpServletResponse resp)
> throws ServletException, IOException {
> bean.callNext();
> }
> }
> {code}
> {code:java}
> @Stateless
> public class Bean implements BeanRemote {
> @EJB(lookup = "ejb:/server-side-slave1/WhoAmIBean!example.ejb.WhoAmIBeanRemote")
> private WhoAmIBeanRemote remoteBean1ByInjection;
> @EJB(lookup = "ejb:/server-side-slave2/WhoAmIBean!example.ejb.WhoAmIBeanRemote")
> private WhoAmIBeanRemote remoteBean2ByInjection;
> @Override
> public void callNext() throws RemoteException {
> try {
> StringBuilder sb = new StringBuilder();
> sb.append("WhoAmI from server-side-slave1 returned: ").append(remoteBean1ByInjection.whoAmI()).append("\n");
> sb.append("WhoAmI from server-side-slave2 returned: ").append(remoteBean2ByInjection.whoAmI()).append("\n");
> } catch (Exception e) {
> throw new RuntimeException(e);
> }
> }
> }
> {code}
> If the servlet performs calls (instead of local bean) both calls will be successful.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10087) EJB uses the same remote outbound connection all the time
by Ivan Straka (JIRA)
[ https://issues.jboss.org/browse/WFLY-10087?page=com.atlassian.jira.plugin... ]
Ivan Straka updated WFLY-10087:
-------------------------------
Component/s: (was: EJB)
> EJB uses the same remote outbound connection all the time
> ---------------------------------------------------------
>
> Key: WFLY-10087
> URL: https://issues.jboss.org/browse/WFLY-10087
> Project: WildFly
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 12.0.0.Final
> Reporter: Ivan Straka
> Attachments: client-side.war, server-side-slave1.jar, server-side-slave2.jar
>
>
> Lets have three servers master, slave1, slave2. Master has two remote outbound connection defined that point to slave1 and slave2.
> When the EJB deployed to master needs to call two EJB (slave1 and slave2), the first call is successful, but the second one is not becaus the EJB uses remote outbound connection that points to slave1 (instead of slave2).
> This results to the followinf exception:
> {code:java}
> 14:28:18,914 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /client-side/: javax.ejb.EJBException: java.lang.RuntimeException: javax.ejb.NoSuchEJBException: No such EJB: /server-side-slave2/WhoAmIBean @ http-remoting://localhost:8180
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:186)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:330)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:238)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
> at org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:72)
> at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438)
> at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:619)
> at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
> at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198)
> at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185)
> at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:81)
> at example.BeanRemote$$$view1.callNext(Unknown Source)
> at example.ClientServlet.doGet(ClientServlet.java:36)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74)
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
> at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:67)
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
> at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
> at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
> at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
> at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
> at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1526)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1526)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1526)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1526)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.RuntimeException: javax.ejb.NoSuchEJBException: No such EJB: /server-side-slave2/WhoAmIBean @ http-remoting://localhost:8180
> at example.Bean.callNext(Bean.java:23)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
> at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:90)
> at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:101)
> at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:40)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
> at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:273)
> ... 78 more
> Caused by: javax.ejb.NoSuchEJBException: No such EJB: /server-side-slave2/WhoAmIBean @ http-remoting://localhost:8180
> at org.jboss.ejb.protocol.remote.EJBClientChannel$MethodInvocation.handleResponse(EJBClientChannel.java:1070)
> at org.jboss.ejb.protocol.remote.EJBClientChannel$MethodInvocation.handleResponse(EJBClientChannel.java:997)
> at org.jboss.remoting3.util.InvocationTracker.signalResponse(InvocationTracker.java:167)
> at org.jboss.ejb.protocol.remote.EJBClientChannel.processMessage(EJBClientChannel.java:186)
> at org.jboss.ejb.protocol.remote.EJBClientChannel.access$100(EJBClientChannel.java:112)
> at org.jboss.ejb.protocol.remote.EJBClientChannel$1$1.handleMessage(EJBClientChannel.java:675)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:926)
> ... 5 more
> Suppressed: javax.ejb.NoSuchEJBException: No such EJB: /server-side-slave2/WhoAmIBean @ http-remoting://localhost:8180
> ... 13 more
> Suppressed: javax.ejb.NoSuchEJBException: No such EJB: /server-side-slave2/WhoAmIBean @ http-remoting://localhost:8180
> ... 13 more
> Suppressed: javax.ejb.NoSuchEJBException: No such EJB: /server-side-slave2/WhoAmIBean @ http-remoting://localhost:8180
> ... 13 more
> Suppressed: javax.ejb.NoSuchEJBException: No such EJB: /server-side-slave2/WhoAmIBean @ http-remoting://localhost:8180
> ... 13 more
> Suppressed: javax.ejb.NoSuchEJBException: No such EJB: /server-side-slave2/WhoAmIBean @ http-remoting://localhost:8180
> ... 13 more
> Suppressed: javax.ejb.NoSuchEJBException: No such EJB: /server-side-slave2/WhoAmIBean @ http-remoting://localhost:8180
> at org.jboss.ejb.protocol.remote.EJBClientChannel$MethodInvocation.handleResponse(EJBClientChannel.java:1070)
> at org.jboss.ejb.protocol.remote.EJBClientChannel$MethodInvocation.handleResponse(EJBClientChannel.java:997)
> at org.jboss.remoting3.util.InvocationTracker.signalResponse(InvocationTracker.java:167)
> at org.jboss.ejb.protocol.remote.EJBClientChannel.processMessage(EJBClientChannel.java:186)
> at org.jboss.ejb.protocol.remote.EJBClientChannel.access$100(EJBClientChannel.java:112)
> at org.jboss.ejb.protocol.remote.EJBClientChannel$1$1.handleMessage(EJBClientChannel.java:675)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$receiveMessage$2(RemoteConnectionChannel.java:361)
> ... 6 more
> Suppressed: javax.ejb.NoSuchEJBException: No such EJB: /server-side-slave2/WhoAmIBean @ http-remoting://localhost:8180
> ... 13 more
> Suppressed: javax.ejb.NoSuchEJBException: No such EJB: /server-side-slave2/WhoAmIBean @ http-remoting://localhost:8180
> ... 13 more
> {code}
> Server side EJB (slave1, slave2) are simple:
> {code:java}
> @Stateless
> public class WhoAmIBean implements WhoAmIBeanRemote {
> @Override
> public String whoAmI() {
> String s = "WhoAmIBean.whoAmI called on server with port-offset " + System.getProperty("jboss.socket.binding.port-offset");
> System.out.println(s);
> return s;
> }
> }
> {code}
> Client side war (master) is simple servlet and EJB that performs calls.
> {code:java}
> @WebServlet(urlPatterns = "/")
> public class ClientServlet extends HttpServlet {
> @EJB
> private BeanRemote bean;
> @Override
> protected void doGet(HttpServletRequest req, HttpServletResponse resp)
> throws ServletException, IOException {
> bean.callNext();
> }
> }
> {code}
> {code:java}
> @Stateless
> public class Bean implements BeanRemote {
> @EJB(lookup = "ejb:/server-side-slave1/WhoAmIBean!example.ejb.WhoAmIBeanRemote")
> private WhoAmIBeanRemote remoteBean1ByInjection;
> @EJB(lookup = "ejb:/server-side-slave2/WhoAmIBean!example.ejb.WhoAmIBeanRemote")
> private WhoAmIBeanRemote remoteBean2ByInjection;
> @Override
> public void callNext() throws RemoteException {
> try {
> StringBuilder sb = new StringBuilder();
> sb.append("WhoAmI from server-side-slave1 returned: ").append(remoteBean1ByInjection.whoAmI()).append("\n");
> sb.append("WhoAmI from server-side-slave2 returned: ").append(remoteBean2ByInjection.whoAmI()).append("\n");
> } catch (Exception e) {
> throw new RuntimeException(e);
> }
> }
> }
> {code}
> If the servlet performs calls (instead of local bean) both calls will be successful.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2410) [DMN Designer] Active entries not highlighted correctly when scrolling
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2410?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2410:
--------------------------------
Description:
The behavior described below was spotted during DROOLS-2398 review, however probably not related to that jira.
If context table is so big user has to scroll down to see all entries. then the active entries are not highlighted correctly. Next if user select some cell, then scroll (so the originally selected cell is not visible more) and select another cell, both remains selected. I mean selection without holding any additional key.
h2. Acceptance criteria
- As active entry is highlighted just that context entry that is parent of the selected cell.
- Single cell selection even if scrolling between selection
- Steps to reproduce fixed (/)
was:
The behavior described below was spotted during DROOLS-2398 review, however probably not related to that jira.
If context table is so big user has to scroll down to see all entries. then the active entries are not highlighted correctly. Next if user select some cell, then scroll (so the originally selected cell is not visible more) and select another cell, both remains selected. I mean selection without holding any additional key.
h2. Acceptance criteria
- As active entry is highlighted just that context entry that is parent of the selected cell.
- Single cell selection even if scrolling between selection
> [DMN Designer] Active entries not highlighted correctly when scrolling
> ----------------------------------------------------------------------
>
> Key: DROOLS-2410
> URL: https://issues.jboss.org/browse/DROOLS-2410
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.7.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
>
> The behavior described below was spotted during DROOLS-2398 review, however probably not related to that jira.
> If context table is so big user has to scroll down to see all entries. then the active entries are not highlighted correctly. Next if user select some cell, then scroll (so the originally selected cell is not visible more) and select another cell, both remains selected. I mean selection without holding any additional key.
> h2. Acceptance criteria
> - As active entry is highlighted just that context entry that is parent of the selected cell.
> - Single cell selection even if scrolling between selection
> - Steps to reproduce fixed (/)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2394) [DMN Designer] Rename of output changes back to link
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2394?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-2394:
----------------------------------------
[~jomarko] There are two reported issues:-
1) Updating the Title in either the Properties Panel or "in place" editor does not update the "Back to" link.
This is caused by https://issues.jboss.org/browse/DROOLS-1937
2) Updating the Title in the DMN "grid" editor (table header) does not update the Properties Panel
This is caused by Forms not updating when a change is initiated from somewhere other than the Properties panel itself.
[~pere.fernandez] thinks https://github.com/kiegroup/kie-wb-common/pull/1508 could fix it.
> [DMN Designer] Rename of output changes back to link
> ----------------------------------------------------
>
> Key: DROOLS-2394
> URL: https://issues.jboss.org/browse/DROOLS-2394
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.7.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Optional
> Attachments: Screenshot from 2018-03-16 12-14-13.png, expression_editor_of_decision.png, renamed_in_context_popup.png, renamed_in_proeprties.png
>
>
> Renaming output of decision table changes the {{back to}} link.
> h2. Acceptance tests
> # Three different decisions (x) DROOLS-1937
> ## In DRD declare three different decision (different names)
> ## Check navigation to properties of these decisions
> # One decision
> ## In DRD declare one decision
> ## For each context entry type check
> ## Renaming in DRD -> also top level expression in properties renamed (x) DROOLS-1937
> ## Renaming in decision properties -> also name in DRD changed (/)
> ## Change of expression type preserves name (/)
> ## Undo / Redo changes name both in properties and drd diagram (/)
> ## Diagram where top level expression of decision was renamed can saved, closed and reopened (/)
> # Steps to reproduce fixed (/)
> h3. Acceptance tests result
> Failed due to:
> Rename decision node either as:
> - !renamed_in_context_popup.png|thumbnail!
> - !renamed_in_proeprties.png|thumbnail!
> In both cases above, expression editor of that decision node will look like
> - !expression_editor_of_decision.png|thumbnail!
> The expression editor back to link shouldn't show *My Name*
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2394) [DMN Designer] Rename of output changes back to link
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2394?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2394:
--------------------------------
Description:
Renaming output of decision table changes the {{back to}} link.
h2. Acceptance tests
# Three different decisions (x) DROOLS-1937
## In DRD declare three different decision (different names)
## Check navigation to properties of these decisions
# One decision
## In DRD declare one decision
## For each context entry type check
## Renaming in DRD -> also top level expression in properties renamed (x) DROOLS-1937
## Renaming in decision properties -> also name in DRD changed (/)
## Change of expression type preserves name (/)
## Undo / Redo changes name both in properties and drd diagram (/)
## Diagram where top level expression of decision was renamed can saved, closed and reopened (/)
# Steps to reproduce fixed (/)
h3. Acceptance tests result
Failed due to:
Rename decision node either as:
- !renamed_in_context_popup.png|thumbnail!
- !renamed_in_proeprties.png|thumbnail!
In both cases above, expression editor of that decision node will look like
- !expression_editor_of_decision.png|thumbnail!
The expression editor back to link shouldn't show *My Name*
was:
Renaming output of decision table changes the {{back to}} link.
h2. Acceptance tests
# Three different decisions (x)
## In DRD declare three different decision (different names)
## Check navigation to properties of these decisions
# One decision
## In DRD declare one decision
## For each context entry type check
## Renaming in DRD -> also top level expression in properties renamed (x)
## Renaming in decision properties -> also name in DRD changed (/)
## Change of expression type preserves name (/)
## Undo / Redo changes name both in properties and drd diagram (/)
## Diagram where top level expression of decision was renamed can saved, closed and reopened (/)
# Steps to reproduce fixed (/)
h3. Acceptance tests result
Failed due to:
Rename decision node either as:
- !renamed_in_context_popup.png|thumbnail!
- !renamed_in_proeprties.png|thumbnail!
In both cases above, expression editor of that decision node will look like
- !expression_editor_of_decision.png|thumbnail!
The expression editor back to link shouldn't show *My Name*
> [DMN Designer] Rename of output changes back to link
> ----------------------------------------------------
>
> Key: DROOLS-2394
> URL: https://issues.jboss.org/browse/DROOLS-2394
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.7.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Optional
> Attachments: Screenshot from 2018-03-16 12-14-13.png, expression_editor_of_decision.png, renamed_in_context_popup.png, renamed_in_proeprties.png
>
>
> Renaming output of decision table changes the {{back to}} link.
> h2. Acceptance tests
> # Three different decisions (x) DROOLS-1937
> ## In DRD declare three different decision (different names)
> ## Check navigation to properties of these decisions
> # One decision
> ## In DRD declare one decision
> ## For each context entry type check
> ## Renaming in DRD -> also top level expression in properties renamed (x) DROOLS-1937
> ## Renaming in decision properties -> also name in DRD changed (/)
> ## Change of expression type preserves name (/)
> ## Undo / Redo changes name both in properties and drd diagram (/)
> ## Diagram where top level expression of decision was renamed can saved, closed and reopened (/)
> # Steps to reproduce fixed (/)
> h3. Acceptance tests result
> Failed due to:
> Rename decision node either as:
> - !renamed_in_context_popup.png|thumbnail!
> - !renamed_in_proeprties.png|thumbnail!
> In both cases above, expression editor of that decision node will look like
> - !expression_editor_of_decision.png|thumbnail!
> The expression editor back to link shouldn't show *My Name*
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2394) [DMN Designer] Rename of output changes back to link
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2394?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2394:
--------------------------------
Description:
Renaming output of decision table changes the {{back to}} link.
h2. Acceptance tests
# Three different decisions (x)
## In DRD declare three different decision (different names)
## Check navigation to properties of these decisions
# One decision
## In DRD declare one decision
## For each context entry type check
## Renaming in DRD -> also top level expression in properties renamed (x)
## Renaming in decision properties -> also name in DRD changed (/)
## Change of expression type preserves name (/)
## Undo / Redo changes name both in properties and drd diagram (/)
## Diagram where top level expression of decision was renamed can saved, closed and reopened (/)
# Steps to reproduce fixed (/)
h3. Acceptance tests result
Failed due to:
Rename decision node either as:
- !renamed_in_context_popup.png|thumbnail!
- !renamed_in_proeprties.png|thumbnail!
In both cases above, expression editor of that decision node will look like
- !expression_editor_of_decision.png|thumbnail!
The expression editor back to link shouldn't show *My Name*
was:
Renaming output of decision table changes the {{back to}} link.
h2. Acceptance tests
# Three different decisions (x)
## In DRD declare three different decision (different names)
## Check navigation to properties of these decisions
# One decision
## In DRD declare one decision
## For each context entry type check
## Renaming in DRD -> also top level expression in properties renamed (x)
## Renaming in decision properties -> also name in DRD changed (/)
## Change of expression type preserves name (/)
## Undo / Redo changes name both in properties and drd diagram (/)
## Diagram where top level expression of decision was renamed can saved, closed and reopened (/)
# Steps to reproduce fixed (/)
h3. Acceptance tests result
Failed due to:
Rename decision node either as:
-
> [DMN Designer] Rename of output changes back to link
> ----------------------------------------------------
>
> Key: DROOLS-2394
> URL: https://issues.jboss.org/browse/DROOLS-2394
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.7.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Optional
> Attachments: Screenshot from 2018-03-16 12-14-13.png, expression_editor_of_decision.png, renamed_in_context_popup.png, renamed_in_proeprties.png
>
>
> Renaming output of decision table changes the {{back to}} link.
> h2. Acceptance tests
> # Three different decisions (x)
> ## In DRD declare three different decision (different names)
> ## Check navigation to properties of these decisions
> # One decision
> ## In DRD declare one decision
> ## For each context entry type check
> ## Renaming in DRD -> also top level expression in properties renamed (x)
> ## Renaming in decision properties -> also name in DRD changed (/)
> ## Change of expression type preserves name (/)
> ## Undo / Redo changes name both in properties and drd diagram (/)
> ## Diagram where top level expression of decision was renamed can saved, closed and reopened (/)
> # Steps to reproduce fixed (/)
> h3. Acceptance tests result
> Failed due to:
> Rename decision node either as:
> - !renamed_in_context_popup.png|thumbnail!
> - !renamed_in_proeprties.png|thumbnail!
> In both cases above, expression editor of that decision node will look like
> - !expression_editor_of_decision.png|thumbnail!
> The expression editor back to link shouldn't show *My Name*
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2394) [DMN Designer] Rename of output changes back to link
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2394?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2394:
--------------------------------
Description:
Renaming output of decision table changes the {{back to}} link.
h2. Acceptance tests
# Three different decisions (x)
## In DRD declare three different decision (different names)
## Check navigation to properties of these decisions
# One decision
## In DRD declare one decision
## For each context entry type check
## Renaming in DRD -> also top level expression in properties renamed (x)
## Renaming in decision properties -> also name in DRD changed (/)
## Change of expression type preserves name (/)
## Undo / Redo changes name both in properties and drd diagram (/)
## Diagram where top level expression of decision was renamed can saved, closed and reopened (/)
# Steps to reproduce fixed (/)
h3. Acceptance tests result
Failed due to:
Rename decision node either as:
-
was:
Renaming output of decision table changes the {{back to}} link.
h2. Acceptance tests
# Three different decisions (x)
## In DRD declare three different decision (different names)
## Check navigation to properties of these decisions
# One decision
## In DRD declare one decision
## For each context entry type check
## Renaming in DRD -> also top level expression in properties renamed (x)
## Renaming in decision properties -> also name in DRD changed (/)
## Change of expression type preserves name (/)
## Undo / Redo changes name both in properties and drd diagram (/)
## Diagram where top level expression of decision was renamed can saved, closed and reopened (/)
# Steps to reproduce fixed (/)
> [DMN Designer] Rename of output changes back to link
> ----------------------------------------------------
>
> Key: DROOLS-2394
> URL: https://issues.jboss.org/browse/DROOLS-2394
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.7.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Optional
> Attachments: Screenshot from 2018-03-16 12-14-13.png, expression_editor_of_decision.png, renamed_in_context_popup.png, renamed_in_proeprties.png
>
>
> Renaming output of decision table changes the {{back to}} link.
> h2. Acceptance tests
> # Three different decisions (x)
> ## In DRD declare three different decision (different names)
> ## Check navigation to properties of these decisions
> # One decision
> ## In DRD declare one decision
> ## For each context entry type check
> ## Renaming in DRD -> also top level expression in properties renamed (x)
> ## Renaming in decision properties -> also name in DRD changed (/)
> ## Change of expression type preserves name (/)
> ## Undo / Redo changes name both in properties and drd diagram (/)
> ## Diagram where top level expression of decision was renamed can saved, closed and reopened (/)
> # Steps to reproduce fixed (/)
> h3. Acceptance tests result
> Failed due to:
> Rename decision node either as:
> -
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2394) [DMN Designer] Rename of output changes back to link
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2394?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2394:
--------------------------------
Attachment: renamed_in_proeprties.png
renamed_in_context_popup.png
expression_editor_of_decision.png
> [DMN Designer] Rename of output changes back to link
> ----------------------------------------------------
>
> Key: DROOLS-2394
> URL: https://issues.jboss.org/browse/DROOLS-2394
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.7.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Optional
> Attachments: Screenshot from 2018-03-16 12-14-13.png, expression_editor_of_decision.png, renamed_in_context_popup.png, renamed_in_proeprties.png
>
>
> Renaming output of decision table changes the {{back to}} link.
> h2. Acceptance tests
> # Three different decisions (x)
> ## In DRD declare three different decision (different names)
> ## Check navigation to properties of these decisions
> # One decision
> ## In DRD declare one decision
> ## For each context entry type check
> ## Renaming in DRD -> also top level expression in properties renamed (x)
> ## Renaming in decision properties -> also name in DRD changed (/)
> ## Change of expression type preserves name (/)
> ## Undo / Redo changes name both in properties and drd diagram (/)
> ## Diagram where top level expression of decision was renamed can saved, closed and reopened (/)
> # Steps to reproduce fixed (/)
> h3. Acceptance tests result
> Failed due to:
> Rename decision node either as:
> -
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10077) [Artemis 2.x upgrade] journal-node-manager-store-table attribute does not preserve its value
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-10077?page=com.atlassian.jira.plugin... ]
Jeff Mesnil resolved WFLY-10077.
--------------------------------
Resolution: Done
This issue was caused by an error during a manual conflict resolutoin when I rebased the integration branch on top of WildFly 12.
> [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
[JBoss JIRA] (DROOLS-2394) [DMN Designer] Rename of output changes back to link
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2394?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2394:
--------------------------------
Description:
Renaming output of decision table changes the {{back to}} link.
h2. Acceptance tests
# Three different decisions (x)
## In DRD declare three different decision (different names)
## Check navigation to properties of these decisions
# One decision
## In DRD declare one decision
## For each context entry type check
## Renaming in DRD -> also top level expression in properties renamed (x)
## Renaming in decision properties -> also name in DRD changed (/)
## Change of expression type preserves name (/)
## Undo / Redo changes name both in properties and drd diagram (/)
## Diagram where top level expression of decision was renamed can saved, closed and reopened (/)
# Steps to reproduce fixed (/)
was:
Renaming output of decision table changes the {{back to}} link.
h2. Acceptance tests
# Three different decisions (x)
## In DRD declare three different decision (different names)
## Check navigation to properties of these decisions
# One decision
## In DRD declare one decision
## For each context entry type check
## Renaming in DRD -> also top level expression in properties renamed (x)
## Renaming in decision properties -> also name in DRD changed (/)
## Change of expression type preserves name (/)
## Undo / Redo changes name both in properties and drd diagram (/)
## Diagram where top level expression of decision was renamed can saved, closed and reopened (/)
> [DMN Designer] Rename of output changes back to link
> ----------------------------------------------------
>
> Key: DROOLS-2394
> URL: https://issues.jboss.org/browse/DROOLS-2394
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.7.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Optional
> Attachments: Screenshot from 2018-03-16 12-14-13.png
>
>
> Renaming output of decision table changes the {{back to}} link.
> h2. Acceptance tests
> # Three different decisions (x)
> ## In DRD declare three different decision (different names)
> ## Check navigation to properties of these decisions
> # One decision
> ## In DRD declare one decision
> ## For each context entry type check
> ## Renaming in DRD -> also top level expression in properties renamed (x)
> ## Renaming in decision properties -> also name in DRD changed (/)
> ## Change of expression type preserves name (/)
> ## Undo / Redo changes name both in properties and drd diagram (/)
> ## Diagram where top level expression of decision was renamed can saved, closed and reopened (/)
> # Steps to reproduce fixed (/)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month