February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3646) [DMN Designer] Updating two files in the editor raises an error

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3646?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3646: -------------------------------- Tester: Jozef Marko > [DMN Designer] Updating two files in the editor raises an error > --------------------------------------------------------------- > > Key: DROOLS-3646 > URL: https://issues.jboss.org/browse/DROOLS-3646 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Guilherme Carreiro > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: 1.gif, 2.gif > > > When users update a DMN file, don't save it, and try to update another DMN file, an error appears. See the following scenarios: > *1* > !1.gif|thumbnail! > *2* > !2.gif|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3515) [DMN Designer] Validation does not check feel expressions.

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3515?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3515: -------------------------------- Tester: Jozef Marko Affects Version/s: 7.18.0.Final > [DMN Designer] Validation does not check feel expressions. > ---------------------------------------------------------- > > Key: DROOLS-3515 > URL: https://issues.jboss.org/browse/DROOLS-3515 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Thomas Mantegazzi > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: image-2019-01-14-09-24-07-415.png, image-2019-01-14-09-25-01-777.png, image-2019-01-14-09-25-16-907.png > > > The "validate" button at the top does nit seem to be validating feel expressions: > !image-2019-01-14-09-24-07-415.png|thumbnail! > The input of this Decision is a "person" object: > !image-2019-01-14-09-25-01-777.png|thumbnail! > and this is the DRG: > !image-2019-01-14-09-25-16-907.png|thumbnail! > The validation should say that this literal expression is not valid. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3651) [DMN Designer] Table input clause generation in a decision service

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3651?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3651: ---------------------------------------- [~jomarko] I have also tested with the latest Business Central on our Jenkins/Docker environment and cannot replicate there either. > [DMN Designer] Table input clause generation in a decision service > ------------------------------------------------------------------ > > Key: DROOLS-3651 > URL: https://issues.jboss.org/browse/DROOLS-3651 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > Attachments: violation.dmn > > > The dmn designer has a feature of autogeneration *input clauses* for a *decision table*, if this one is connected with *input nodes*, however this feature doesn't work if a *decision node* is placed inside a *decision service* node. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11622) Multiple delivery group support for MDBs

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-11622?page=com.atlassian.jira.plugin... ] Miroslav Novak commented on WFLY-11622: --------------------------------------- [~brian.stansberry] All the checks passed. I've started Wildfly test suite with master (after merge) and then Flavia's branch in the morning and did not see any related to this. I think this can be resolved. > Multiple delivery group support for MDBs > ---------------------------------------- > > Key: WFLY-11622 > URL: https://issues.jboss.org/browse/WFLY-11622 > Project: WildFly > Issue Type: Feature Request > Components: EJB, JMS > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Major > > Add support for multiple delivery groups in the same MDB. > For info on delivery groups, see https://docs.jboss.org/author/display/WFLY10/Message+Driven+Beans+Control... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11622) Multiple delivery group support for MDBs

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-11622?page=com.atlassian.jira.plugin... ] Miroslav Novak edited comment on WFLY-11622 at 2/13/19 7:13 AM: ---------------------------------------------------------------- [~brian.stansberry] All the checks passed. I've started Wildfly test suite with master (after merge) and then Flavia's branch in the morning and did not see any issue related to this. I think this can be resolved. was (Author: mnovak): [~brian.stansberry] All the checks passed. I've started Wildfly test suite with master (after merge) and then Flavia's branch in the morning and did not see any related to this. I think this can be resolved. > Multiple delivery group support for MDBs > ---------------------------------------- > > Key: WFLY-11622 > URL: https://issues.jboss.org/browse/WFLY-11622 > Project: WildFly > Issue Type: Feature Request > Components: EJB, JMS > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Major > > Add support for multiple delivery groups in the same MDB. > For info on delivery groups, see https://docs.jboss.org/author/display/WFLY10/Message+Driven+Beans+Control... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4327) Switched order of method arguments - ModuleSpecProcessor

by Rostislav Svoboda (Jira)

Rostislav Svoboda created WFCORE-4327: ----------------------------------------- Summary: Switched order of method arguments - ModuleSpecProcessor Key: WFCORE-4327 URL: https://issues.jboss.org/browse/WFCORE-4327 Project: WildFly Core Issue Type: Bug Components: Server Reporter: Rostislav Svoboda Assignee: Yeray Borges Switched order of method arguments - ModuleSpecProcessor line 287 Introduced in https://github.com/wildfly/wildfly-core/pull/3661 method call {code} return ModuleLoadService.install(phaseContext.getServiceTarget(), moduleIdentifier, dependencies, localDependencies, userDependencies); {code} ModuleLoadService.install signature: {code} public static ServiceName install(final ServiceTarget target, final ModuleIdentifier identifier, final List<ModuleDependency> systemDependencies, final List<ModuleDependency> userDependencies, final List<ModuleDependency> localDependencies) { {code} https://github.com/wildfly/wildfly-core/blob/master/server/src/main/java/... So localDependencies and userDependencies should be switched. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11605) Slave Artemis in Wildfly 10.1.0.Final is starting without Master Shutdown - Split brain

by Srinivas ev (Jira)

[ https://issues.jboss.org/browse/WFLY-11605?page=com.atlassian.jira.plugin... ] Srinivas ev commented on WFLY-11605: ------------------------------------ Is there any way I can simulate the same scenario(Split-brain) in Linux machines. For ex, enabling the firewall, disabling the ports of LiveQ. Please let me know. > Slave Artemis in Wildfly 10.1.0.Final is starting without Master Shutdown - Split brain > --------------------------------------------------------------------------------------- > > Key: WFLY-11605 > URL: https://issues.jboss.org/browse/WFLY-11605 > Project: WildFly > Issue Type: Bug > Components: Clustering, JMS > Affects Versions: 10.1.0.Final > Reporter: Srinivas ev > Assignee: ehsavoie Hugonnet > Priority: Major > Labels: https://developer.jboss.org/thread/279503 > Attachments: Master and Slave logs.txt, Project component log.txt, Wildfly error abrupt failback.txt > > > Scenario - Master, and Slave Running on 2 VM's. > Master Wildfly - <replication-master cluster-name="my-cluster" group-name="srini-queues-cluster-group" check-for-live-server="true"/> > Slave Wildfly - <replication-slave cluster-name="my-cluster" group-name="srini-queues-cluster-group" allow-failback="false" max-saved-replicated-journal-size="1"/> > PFB below 2 errors. > At this time Slave will start deploying Queues even when Master wildfly is not stopped completely. Both management consoles can be reached. > Ideally, the Master server(Wildfly) should completely stop for Slave to start the deployment of queues and start the replication. > 2019/01/16 19:56:21,118+05:30 ERROR [org.apache.activemq.artemis.core.server] (default I/O-2) AMQ224044: error acknowledging message: java.lang.NullPointer > Exception > at org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.removeReferenceByID(ServerConsumerImpl.java:811) > 2019/01/16 19:56:21,121+05:30 ERROR [org.apache.activemq.artemis.core.server] (default I/O-2) AMQ224016: Caught exception: ActiveMQIllegalStateException[er > rorType=ILLEGAL_STATE message=null] > at org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.individualAcknowledge(ServerConsumerImpl.java:772) > at org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.individualAcknowledge(ServerSessionImpl.java:739) > Detailed logs are attached. > At this stage, 1st component in my project pipeline has identified the slave as master now and stick with sending messages to it. Whereas the other components in the pipeline still consuming from Master(based on consumer count). > This caused the break-in message flow. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3647) [DMN Designer] Boxed expressions - Decision Table - Add support for setting constraints on "Input Clausules"

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3647?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3647: -------------------------------- Tester: Jozef Marko Affects Version/s: 7.18.0.Final > [DMN Designer] Boxed expressions - Decision Table - Add support for setting constraints on "Input Clausules" > ------------------------------------------------------------------------------------------------------------ > > Key: DROOLS-3647 > URL: https://issues.jboss.org/browse/DROOLS-3647 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > Users must be able to set constraints on "Input Clausules". -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11292) Legacy EJB Client: High fail rate

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-11292?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFLY-11292: --------------------------------------- [~flavia.rainone] Just to keep the records correct, can you clarify what fixed the issue and what's the fix version? We always set the fix version when resolving issues as "done". > Legacy EJB Client: High fail rate > --------------------------------- > > Key: WFLY-11292 > URL: https://issues.jboss.org/browse/WFLY-11292 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB > Affects Versions: 15.0.0.Beta1 > Reporter: tommaso borgato > Assignee: Flavia Rainone > Priority: Blocker > Attachments: jboss-ejb-client.properties, logs-10clients.zip, logs.zip > > > This bug is being filed as Blocker because we are observing and elevated fail rate: roughly a thousand each run for (about 0.3%). > h2. WildFly Built from master branch on 6 Nov 2018 > With this WildFly version (client org.jboss:jboss-ejb-client-legacy:3.0.2.Final-redhat-1) in a scenario with 4 clustered nodes where nodes are failed via jboss shut-down / restart: after node 1 of 4 is shut-down, a a series of errors start on the client side the yield to 1097 errors on a total of 340218 samples; > find [here|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/EAP7/view/...] the complete logs; > the start of client errors is here: > {noformat} > 2018/11/07 05:28:51:255 EST [INFO ][TestController] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Failing node 0 (perf18) > 2018/11/07 05:28:51:270 EST [INFO ][StatsRunner] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Total: Sessions: 2000, active: 2000, samples: 5118, throughput: 511.7 samples/s, bandwidth: 0.0 MB/s, response min: 1 ms, mean: 1 ms, max: 54 ms, sampling errors: 0, unhealthy samples: 0, valid samples: 5118 (100%) > 2018/11/07 05:28:51:270 EST [INFO ][StatsRunner] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - unknown-node: Sessions: 2000, active: 2000, samples: 5118, throughput: 511.7 samples/s, bandwidth: 0.0 MB/s, response min: 1 ms, mean: 1 ms, max: 54 ms, sampling errors: 0, unhealthy samples: 0, valid samples: 5118 (100%) > 05:28:53,257 INFO [org.jboss.ejb.client.remoting] (Remoting "config-based-ejb-client-endpoint" task-2) EJBCLIENT000016: Channel Channel ID c540daf7 (outbound) of Remoting connection 4ed5523c to perf18/10.16.90.54:8080 of endpoint "config-based-ejb-client-endpoint" <664ac6d5> can no longer process messages > 05:28:53,277 ERROR [org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver] (Remoting "config-based-ejb-client-endpoint" task-2) Failed to open channel for context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@3cd51445, receiver=Remoting connection EJB receiver [connection=org.jboss.ejb.client.remoting.ConnectionPool$PooledConnection(a)302066a5,channel=jboss.ejb,nodename=perf18]} > org.jboss.remoting3.NotOpenException: Cannot open new channel because close was initiated > at org.jboss.remoting3.remote.RemoteConnectionHandler.handleOutboundChannelOpen(RemoteConnectionHandler.java:198) > at org.jboss.remoting3.remote.RemoteConnectionHandler.open(RemoteConnectionHandler.java:335) > at org.jboss.remoting3.ConnectionImpl.openChannel(ConnectionImpl.java:109) > at org.jboss.ejb.client.remoting.ConnectionPool$PooledConnection.openChannel(ConnectionPool.java:292) > at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.associate(RemotingConnectionEJBReceiver.java:180) > at org.jboss.ejb.client.EJBClientContext.registerEJBReceiver(EJBClientContext.java:399) > at org.jboss.ejb.client.EJBClientContext.registerEJBReceiver(EJBClientContext.java:349) > at org.jboss.ejb.client.remoting.EJBClientContextConnectionReconnectHandler.reconnect(EJBClientContextConnectionReconnectHandler.java:67) > at org.jboss.ejb.client.EJBClientContext$ReconnectAttempt.run(EJBClientContext.java:1474) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > {noformat} > h2. WildFly Built from master branch on 7 Nov 2018 > Same situation. > find [here|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/EAP7/view/...] the complete logs; > the start of client errors is here: > {noformat} > 2018/11/07 09:23:22:916 EST [INFO ][TestController] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Failing node 0 (perf18) > 2018/11/07 09:23:22:930 EST [INFO ][StatsRunner] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Total: Sessions: 2000, active: 2000, samples: 5125, throughput: 512.4 samples/s, bandwidth: 0.0 MB/s, response min: 1 ms, mean: 2 ms, max: 32 ms, sampling errors: 0, unhealthy samples: 0, valid samples: 5125 (100%) > 2018/11/07 09:23:22:930 EST [INFO ][StatsRunner] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - unknown-node: Sessions: 2000, active: 2000, samples: 5125, throughput: 512.4 samples/s, bandwidth: 0.0 MB/s, response min: 1 ms, mean: 2 ms, max: 32 ms, sampling errors: 0, unhealthy samples: 0, valid samples: 5125 (100%) > 09:23:24,924 INFO [org.jboss.ejb.client.remoting] (Remoting "config-based-ejb-client-endpoint" task-4) EJBCLIENT000016: Channel Channel ID d940c707 (outbound) of Remoting connection 73cfdf01 to perf18/10.16.90.54:8080 of endpoint "config-based-ejb-client-endpoint" <7501616b> can no longer process messages > 09:23:24,949 ERROR [org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver] (Remoting "config-based-ejb-client-endpoint" task-6) Failed to open channel for context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@56248025, receiver=Remoting connection EJB receiver [connection=org.jboss.ejb.client.remoting.ConnectionPool$PooledConnection(a)5269f48d,channel=jboss.ejb,nodename=perf18]} > org.jboss.remoting3.NotOpenException: Cannot open new channel because close was initiated > at org.jboss.remoting3.remote.RemoteConnectionHandler.handleOutboundChannelOpen(RemoteConnectionHandler.java:198) > at org.jboss.remoting3.remote.RemoteConnectionHandler.open(RemoteConnectionHandler.java:335) > at org.jboss.remoting3.ConnectionImpl.openChannel(ConnectionImpl.java:109) > at org.jboss.ejb.client.remoting.ConnectionPool$PooledConnection.openChannel(ConnectionPool.java:292) > at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.associate(RemotingConnectionEJBReceiver.java:180) > at org.jboss.ejb.client.EJBClientContext.registerEJBReceiver(EJBClientContext.java:399) > at org.jboss.ejb.client.EJBClientContext.registerEJBReceiver(EJBClientContext.java:349) > at org.jboss.ejb.client.remoting.EJBClientContextConnectionReconnectHandler.reconnect(EJBClientContextConnectionReconnectHandler.java:67) > at org.jboss.ejb.client.EJBClientContext$ReconnectAttempt.run(EJBClientContext.java:1474) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3651) [DMN Designer] Table input clause generation in a decision service

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3651?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3651: ---------------------------------------- [~jomarko] I followed your steps but was unable to reproduce. I also tried creating the same diagram from scratch in different ways: *_Add DS and Ds first_* # Add Decision Service to graph # Add Decision 1 to graph # Add Decision 2 to graph # Add InputData to graph # Connect ID and D1 and D2 # Drag D1 into DS # Set both D1 and D2 to Decision Tables # InputClauses were correct *_Add DS and one D directly into DS_* # Add Decision Service to graph # Add Decision 1 to DS # Add Decision 2 to graph # Add InputData # Connect ID and D1 and D2 # Set both D1 and D2 to Decision Tables # InputClauses were correct If there's some other way to replicate please advise! > [DMN Designer] Table input clause generation in a decision service > ------------------------------------------------------------------ > > Key: DROOLS-3651 > URL: https://issues.jboss.org/browse/DROOLS-3651 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > Attachments: violation.dmn > > > The dmn designer has a feature of autogeneration *input clauses* for a *decision table*, if this one is connected with *input nodes*, however this feature doesn't work if a *decision node* is placed inside a *decision service* node. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2019