November 2018 - jboss-jira - Jboss List Archives

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

by tommaso borgato (Jira)

[ https://issues.jboss.org/browse/WFLY-11292?page=com.atlassian.jira.plugin... ] tommaso borgato updated WFLY-11292: ----------------------------------- Attachment: logs.zip > 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.Alpha1 > Reporter: tommaso borgato > Assignee: Flavia Rainone > Priority: Blocker > Attachments: 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)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3248) [DMN Designer] QName: Default to be 'Any' not 'string'

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3248?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3248: ----------------------------------- Priority: Blocker (was: Major) > [DMN Designer] QName: Default to be 'Any' not 'string' > ------------------------------------------------------ > > Key: DROOLS-3248 > URL: https://issues.jboss.org/browse/DROOLS-3248 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Michael Anstis > Assignee: Daniel José dos Santos > Priority: Blocker > Labels: drools-tools > > At the moment the _default_ {{QName}} is {{string}} however [~tirelli] has requested it be changed to {{Any}}. Please also note that the the _name_ for {{Any}} should be "*A*ny" and not "*a*ny" as we currently have. See: > https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-dmn/k... > https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-dmn/k... > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3279) DMN DRGElement typeRef to allow FEEL Any

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3279?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3279: ----------------------------------- Priority: Blocker (was: Major) > DMN DRGElement typeRef to allow FEEL Any > ---------------------------------------- > > Key: DROOLS-3279 > URL: https://issues.jboss.org/browse/DROOLS-3279 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Blocker > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3248) [DMN Designer] QName: Default to be 'Any' not 'string'

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3248?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3248: ----------------------------------- Priority: Major (was: Critical) > [DMN Designer] QName: Default to be 'Any' not 'string' > ------------------------------------------------------ > > Key: DROOLS-3248 > URL: https://issues.jboss.org/browse/DROOLS-3248 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Michael Anstis > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > At the moment the _default_ {{QName}} is {{string}} however [~tirelli] has requested it be changed to {{Any}}. Please also note that the the _name_ for {{Any}} should be "*A*ny" and not "*a*ny" as we currently have. See: > https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-dmn/k... > https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-dmn/k... > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3268) [DMN Designer] Data-types: Check for use of built-in-type should be case sensitive

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3268?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3268: ----------------------------------- Priority: Major (was: Blocker) > [DMN Designer] Data-types: Check for use of built-in-type should be case sensitive > ---------------------------------------------------------------------------------- > > Key: DROOLS-3268 > URL: https://issues.jboss.org/browse/DROOLS-3268 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Michael Anstis > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > On the Data Types dialog, creating a type/field called "Number" with an uppercase "N" should be allowed. FEEL/DMN is type sensitive, and only "number" lower case is reserved word. Check if the problem also happens for other types, except for "Any" and "Null" that have an upper case initial. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3287) [DMN Designer] Enable DMN editor by default in distributions

by Michael Anstis (Jira)

Michael Anstis created DROOLS-3287: -------------------------------------- Summary: [DMN Designer] Enable DMN editor by default in distributions Key: DROOLS-3287 URL: https://issues.jboss.org/browse/DROOLS-3287 Project: Drools Issue Type: Feature Request Components: DMN Editor Affects Versions: 7.14.0.Final Reporter: Michael Anstis Assignee: Michael Anstis The DMN Editor needs to be _enabled_ by default in the workbench distributions. This needs to be accomplished for _product_ 7.4. Priority set to _critical_ so we don't loose sight of it! See https://issues.jboss.org/browse/DROOLS-2748 (and reverse it!) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3286) [DMN Designer] FunctionGrid: Move F, J, P selector to header

by Michael Anstis (Jira)

Michael Anstis created DROOLS-3286: -------------------------------------- Summary: [DMN Designer] FunctionGrid: Move F, J, P selector to header Key: DROOLS-3286 URL: https://issues.jboss.org/browse/DROOLS-3286 Project: Drools Issue Type: Feature Request Components: DMN Editor Affects Versions: 7.14.0.Final Reporter: Michael Anstis Assignee: Michael Anstis The {{FunctionGrid}} allows switching between FEEL, Java and PMML function definitions using the context menu. [~tirelli] has requested this be changed to a selector in the header. A new column needs to be added with the F, J, P selector in the new column header. The header should display F, J or P accordingly. Do not include row numbers (i.e. don't just add a {{RowNumberColumn}}! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3285) [DMN Designer] UndefinedExpressionGrid: Change '--' to '<select expression>' in grey italics

by Michael Anstis (Jira)

Michael Anstis created DROOLS-3285: -------------------------------------- Summary: [DMN Designer] UndefinedExpressionGrid: Change '--' to '<select expression>' in grey italics Key: DROOLS-3285 URL: https://issues.jboss.org/browse/DROOLS-3285 Project: Drools Issue Type: Enhancement Components: DMN Editor Affects Versions: 7.14.0.Final Reporter: Michael Anstis Assignee: Michael Anstis [~tirelli] requested the text shown in the "Undefined expression grid" be changed from "--" to "<select expression>" and shown in a grey italicised font. Also check that the default column width for columns that can hold an Undefined Expression grid are suitably wide to ensure the text is shown in full. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3284) [DMN Designer] ContextGrid: Change 'default' to '<result>' in grey italics

by Michael Anstis (Jira)

Michael Anstis created DROOLS-3284: -------------------------------------- Summary: [DMN Designer] ContextGrid: Change 'default' to '<result>' in grey italics Key: DROOLS-3284 URL: https://issues.jboss.org/browse/DROOLS-3284 Project: Drools Issue Type: Enhancement Components: DMN Editor Affects Versions: 7.14.0.Final Reporter: Michael Anstis Assignee: Michael Anstis [~tirelli] requested that the "default" text in a {{ContextEntry}} for the _default result_ row be renamed "<result>" and be shown in a grey italicised font. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3281) [DMN Designer] The output name is valorized for single output decision table

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3281?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-3281: ----------------------------------- Priority: Blocker (was: Major) > [DMN Designer] The output name is valorized for single output decision table > ---------------------------------------------------------------------------- > > Key: DROOLS-3281 > URL: https://issues.jboss.org/browse/DROOLS-3281 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Blocker > Labels: drools-tools > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2018