[JBoss JIRA] (WFLY-10917) Server fails to shutdown
by tommaso borgato (JIRA)
[ https://issues.jboss.org/browse/WFLY-10917?page=com.atlassian.jira.plugin... ]
tommaso borgato updated WFLY-10917:
-----------------------------------
Description:
Affected scenario is {{[perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt/]}}: it is a 4 nodes fail-over scenario where JGroups communication is encrypted asymmetrically:
{noformat}
<subsystem xmlns="urn:jboss:domain:jgroups:6.0" default-stack="udp">
<channels default="ee">
<channel name="ee" stack="udp" cluster="ejb"/>
</channels>
<stacks>
<stack name="udp">
<transport type="UDP" socket-binding="jgroups-udp"/>
<protocol type="PING"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="ASYM_ENCRYPT" xmlns="">
<property name="encrypt_entire_message">true</property>
<property name="sym_keylength">128</property>
<property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
<property name="asym_keylength">512</property>
<property name="asym_algorithm">RSA</property>
</protocol>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="AUTH" xmlns="">
<property name="auth_class">org.jgroups.auth.MD5Token</property>
<property name="auth_value">MyPassword</property>
<property name="token_hash">MD5</property>
</protocol>
<protocol type="pbcast.GMS"/>
<protocol type="UFC"/>
<protocol type="MFC"/>
<protocol type="FRAG3"/>
</stack>
<stack name="tcp">
<transport type="TCP" socket-binding="jgroups-tcp"/>
<socket-protocol type="MPING" socket-binding="jgroups-mping"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG3"/>
</stack>
</stacks>
</subsystem>
{noformat}
The problem is that, after one node of the cluster is shut down and restarted, the remaining nodes fail to shut-down gracefully and their JVM has to be killed.
The default shut-down waiting time is 1 minute: it has been extended to 5 but the nodes still fail to shut-down even in 5 minutes.
Find attached:
- the complete log of one node failing to shut-down (17293.log)
- the thread dump of this node just before being killed (after a 5 minutes time-out) (perf20-consoleText.txt)
The server logs messages like the following (as in JGRP-2282):
{noformat}
[JBossINF] [0m[31m05:36:35,687 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-14,ejb,perf20) perf20: received message without encrypt header from perf21; dropping it
[JBossINF] [0m[31m05:36:36,668 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-14,ejb,perf20) perf20: received message without encrypt header from perf21; dropping it
[JBossINF] [0m[31m05:36:36,879 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-14,ejb,perf20) perf20: received message without encrypt header from perf18; dropping it
{noformat}
before failing to shut-down.
was:
Affected scenario is {{[perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt/]}}: it is a 4 nodes fail-over scenario where JGroups communication is encrypted asymmetrically:
{noformat}
<subsystem xmlns="urn:jboss:domain:jgroups:6.0" default-stack="udp">
<channels default="ee">
<channel name="ee" stack="udp" cluster="ejb"/>
</channels>
<stacks>
<stack name="udp">
<transport type="UDP" socket-binding="jgroups-udp"/>
<protocol type="PING"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="ASYM_ENCRYPT" xmlns="">
<property name="encrypt_entire_message">true</property>
<property name="sym_keylength">128</property>
<property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
<property name="asym_keylength">512</property>
<property name="asym_algorithm">RSA</property>
</protocol>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="AUTH" xmlns="">
<property name="auth_class">org.jgroups.auth.MD5Token</property>
<property name="auth_value">MyPassword</property>
<property name="token_hash">MD5</property>
</protocol>
<protocol type="pbcast.GMS"/>
<protocol type="UFC"/>
<protocol type="MFC"/>
<protocol type="FRAG3"/>
</stack>
<stack name="tcp">
<transport type="TCP" socket-binding="jgroups-tcp"/>
<socket-protocol type="MPING" socket-binding="jgroups-mping"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG3"/>
</stack>
</stacks>
</subsystem>
{noformat}
The problem is that, after one node of the cluster is shut down and restarted, the remaining nodes fail to shut-down gracefully and their JVM has to be killed.
The default shut-down waiting time is 1 minute: it has been extended to 5 but the nodes still fail to shut-down even in 5 minutes.
Find attached:
- the complete log of one node failing to shut-down (17293.log)
- the thread dump of this node just before being killed (after a 5 minutes time-out) (perf20-consoleText.txt)
The logs show many messages like the following (as in JGRP-2282):
{noformat}
[JBossINF] [0m[31m05:36:35,687 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-14,ejb,perf20) perf20: received message without encrypt header from perf21; dropping it
[JBossINF] [0m[31m05:36:36,668 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-14,ejb,perf20) perf20: received message without encrypt header from perf21; dropping it
[JBossINF] [0m[31m05:36:36,879 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-14,ejb,perf20) perf20: received message without encrypt header from perf18; dropping it
{noformat}
> Server fails to shutdown
> -------------------------
>
> Key: WFLY-10917
> URL: https://issues.jboss.org/browse/WFLY-10917
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 14.0.0.CR1
> Reporter: tommaso borgato
> Assignee: Paul Ferraro
> Priority: Critical
> Attachments: 17293.log, perf20-consoleText.txt
>
>
> Affected scenario is {{[perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt/]}}: it is a 4 nodes fail-over scenario where JGroups communication is encrypted asymmetrically:
> {noformat}
> <subsystem xmlns="urn:jboss:domain:jgroups:6.0" default-stack="udp">
> <channels default="ee">
> <channel name="ee" stack="udp" cluster="ejb"/>
> </channels>
> <stacks>
> <stack name="udp">
> <transport type="UDP" socket-binding="jgroups-udp"/>
> <protocol type="PING"/>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD_ALL"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="ASYM_ENCRYPT" xmlns="">
> <property name="encrypt_entire_message">true</property>
> <property name="sym_keylength">128</property>
> <property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
> <property name="asym_keylength">512</property>
> <property name="asym_algorithm">RSA</property>
> </protocol>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="AUTH" xmlns="">
> <property name="auth_class">org.jgroups.auth.MD5Token</property>
> <property name="auth_value">MyPassword</property>
> <property name="token_hash">MD5</property>
> </protocol>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG3"/>
> </stack>
> <stack name="tcp">
> <transport type="TCP" socket-binding="jgroups-tcp"/>
> <socket-protocol type="MPING" socket-binding="jgroups-mping"/>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD_ALL"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="MFC"/>
> <protocol type="FRAG3"/>
> </stack>
> </stacks>
> </subsystem>
> {noformat}
> The problem is that, after one node of the cluster is shut down and restarted, the remaining nodes fail to shut-down gracefully and their JVM has to be killed.
> The default shut-down waiting time is 1 minute: it has been extended to 5 but the nodes still fail to shut-down even in 5 minutes.
> Find attached:
> - the complete log of one node failing to shut-down (17293.log)
> - the thread dump of this node just before being killed (after a 5 minutes time-out) (perf20-consoleText.txt)
> The server logs messages like the following (as in JGRP-2282):
> {noformat}
> [JBossINF] [0m[31m05:36:35,687 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-14,ejb,perf20) perf20: received message without encrypt header from perf21; dropping it
> [JBossINF] [0m[31m05:36:36,668 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-14,ejb,perf20) perf20: received message without encrypt header from perf21; dropping it
> [JBossINF] [0m[31m05:36:36,879 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-14,ejb,perf20) perf20: received message without encrypt header from perf18; dropping it
> {noformat}
> before failing to shut-down.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-10917) Server fails to shutdown
by tommaso borgato (JIRA)
[ https://issues.jboss.org/browse/WFLY-10917?page=com.atlassian.jira.plugin... ]
tommaso borgato updated WFLY-10917:
-----------------------------------
Description:
Affected scenario is {{[perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt/]}}: it is a 4 nodes fail-over scenario where JGroups communication is encrypted asymmetrically:
{noformat}
<subsystem xmlns="urn:jboss:domain:jgroups:6.0" default-stack="udp">
<channels default="ee">
<channel name="ee" stack="udp" cluster="ejb"/>
</channels>
<stacks>
<stack name="udp">
<transport type="UDP" socket-binding="jgroups-udp"/>
<protocol type="PING"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="ASYM_ENCRYPT" xmlns="">
<property name="encrypt_entire_message">true</property>
<property name="sym_keylength">128</property>
<property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
<property name="asym_keylength">512</property>
<property name="asym_algorithm">RSA</property>
</protocol>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="AUTH" xmlns="">
<property name="auth_class">org.jgroups.auth.MD5Token</property>
<property name="auth_value">MyPassword</property>
<property name="token_hash">MD5</property>
</protocol>
<protocol type="pbcast.GMS"/>
<protocol type="UFC"/>
<protocol type="MFC"/>
<protocol type="FRAG3"/>
</stack>
<stack name="tcp">
<transport type="TCP" socket-binding="jgroups-tcp"/>
<socket-protocol type="MPING" socket-binding="jgroups-mping"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG3"/>
</stack>
</stacks>
</subsystem>
{noformat}
The problem is that, after one node of the cluster is shut down and restarted, the remaining nodes fail to shut-down gracefully and their JVM has to be killed.
The default shut-down waiting time is 1 minute: it has been extended to 5 but the nodes still fail to shut-down even in 5 minutes.
Find attached:
- the complete log of one node failing to shut-down (17293.log)
- the thread dump of this node just before being killed (after a 5 minutes time-out) (perf20-consoleText.txt)
The logs show many messages like the following (as in JGRP-2282):
{noformat}
[JBossINF] [0m[31m05:36:35,687 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-14,ejb,perf20) perf20: received message without encrypt header from perf21; dropping it
[JBossINF] [0m[31m05:36:36,668 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-14,ejb,perf20) perf20: received message without encrypt header from perf21; dropping it
[JBossINF] [0m[31m05:36:36,879 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-14,ejb,perf20) perf20: received message without encrypt header from perf18; dropping it
{noformat}
was:
Affected scenario is {{[perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt/]}}: it is a 4 nodes fail-over scenario where JGroups communication is encrypted asymmetrically:
{noformat}
<subsystem xmlns="urn:jboss:domain:jgroups:6.0" default-stack="udp">
<channels default="ee">
<channel name="ee" stack="udp" cluster="ejb"/>
</channels>
<stacks>
<stack name="udp">
<transport type="UDP" socket-binding="jgroups-udp"/>
<protocol type="PING"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="ASYM_ENCRYPT" xmlns="">
<property name="encrypt_entire_message">true</property>
<property name="sym_keylength">128</property>
<property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
<property name="asym_keylength">512</property>
<property name="asym_algorithm">RSA</property>
</protocol>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="AUTH" xmlns="">
<property name="auth_class">org.jgroups.auth.MD5Token</property>
<property name="auth_value">MyPassword</property>
<property name="token_hash">MD5</property>
</protocol>
<protocol type="pbcast.GMS"/>
<protocol type="UFC"/>
<protocol type="MFC"/>
<protocol type="FRAG3"/>
</stack>
<stack name="tcp">
<transport type="TCP" socket-binding="jgroups-tcp"/>
<socket-protocol type="MPING" socket-binding="jgroups-mping"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG3"/>
</stack>
</stacks>
</subsystem>
{noformat}
The problem is that, after one node of the cluster is shut down and restarted, the remaining nodes fail to shut-down gracefully and their JVM has to be killed.
The default shut-down waiting time is 1 minute: it has been extended to 5 but the nodes still fail to shut-down even in 5 minutes.
Find attached:
- the complete log of one node failing to shut-down (17293.log)
- the thread dump of this node just before being killed (after a 5 minutes time-out) (perf20-consoleText.txt)
> Server fails to shutdown
> -------------------------
>
> Key: WFLY-10917
> URL: https://issues.jboss.org/browse/WFLY-10917
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 14.0.0.CR1
> Reporter: tommaso borgato
> Assignee: Paul Ferraro
> Priority: Critical
> Attachments: 17293.log, perf20-consoleText.txt
>
>
> Affected scenario is {{[perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt/]}}: it is a 4 nodes fail-over scenario where JGroups communication is encrypted asymmetrically:
> {noformat}
> <subsystem xmlns="urn:jboss:domain:jgroups:6.0" default-stack="udp">
> <channels default="ee">
> <channel name="ee" stack="udp" cluster="ejb"/>
> </channels>
> <stacks>
> <stack name="udp">
> <transport type="UDP" socket-binding="jgroups-udp"/>
> <protocol type="PING"/>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD_ALL"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="ASYM_ENCRYPT" xmlns="">
> <property name="encrypt_entire_message">true</property>
> <property name="sym_keylength">128</property>
> <property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
> <property name="asym_keylength">512</property>
> <property name="asym_algorithm">RSA</property>
> </protocol>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="AUTH" xmlns="">
> <property name="auth_class">org.jgroups.auth.MD5Token</property>
> <property name="auth_value">MyPassword</property>
> <property name="token_hash">MD5</property>
> </protocol>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG3"/>
> </stack>
> <stack name="tcp">
> <transport type="TCP" socket-binding="jgroups-tcp"/>
> <socket-protocol type="MPING" socket-binding="jgroups-mping"/>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD_ALL"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="MFC"/>
> <protocol type="FRAG3"/>
> </stack>
> </stacks>
> </subsystem>
> {noformat}
> The problem is that, after one node of the cluster is shut down and restarted, the remaining nodes fail to shut-down gracefully and their JVM has to be killed.
> The default shut-down waiting time is 1 minute: it has been extended to 5 but the nodes still fail to shut-down even in 5 minutes.
> Find attached:
> - the complete log of one node failing to shut-down (17293.log)
> - the thread dump of this node just before being killed (after a 5 minutes time-out) (perf20-consoleText.txt)
> The logs show many messages like the following (as in JGRP-2282):
> {noformat}
> [JBossINF] [0m[31m05:36:35,687 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-14,ejb,perf20) perf20: received message without encrypt header from perf21; dropping it
> [JBossINF] [0m[31m05:36:36,668 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-14,ejb,perf20) perf20: received message without encrypt header from perf21; dropping it
> [JBossINF] [0m[31m05:36:36,879 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-14,ejb,perf20) perf20: received message without encrypt header from perf18; dropping it
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-10917) Server fails to shutdown
by tommaso borgato (JIRA)
[ https://issues.jboss.org/browse/WFLY-10917?page=com.atlassian.jira.plugin... ]
tommaso borgato updated WFLY-10917:
-----------------------------------
Priority: Critical (was: Major)
> Server fails to shutdown
> -------------------------
>
> Key: WFLY-10917
> URL: https://issues.jboss.org/browse/WFLY-10917
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 14.0.0.CR1
> Reporter: tommaso borgato
> Assignee: Paul Ferraro
> Priority: Critical
> Attachments: 17293.log, perf20-consoleText.txt
>
>
> Affected scenario is {{[perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt/]}}: it is a 4 nodes fail-over scenario where JGroups communication is encrypted asymmetrically:
> {noformat}
> <subsystem xmlns="urn:jboss:domain:jgroups:6.0" default-stack="udp">
> <channels default="ee">
> <channel name="ee" stack="udp" cluster="ejb"/>
> </channels>
> <stacks>
> <stack name="udp">
> <transport type="UDP" socket-binding="jgroups-udp"/>
> <protocol type="PING"/>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD_ALL"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="ASYM_ENCRYPT" xmlns="">
> <property name="encrypt_entire_message">true</property>
> <property name="sym_keylength">128</property>
> <property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
> <property name="asym_keylength">512</property>
> <property name="asym_algorithm">RSA</property>
> </protocol>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="AUTH" xmlns="">
> <property name="auth_class">org.jgroups.auth.MD5Token</property>
> <property name="auth_value">MyPassword</property>
> <property name="token_hash">MD5</property>
> </protocol>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG3"/>
> </stack>
> <stack name="tcp">
> <transport type="TCP" socket-binding="jgroups-tcp"/>
> <socket-protocol type="MPING" socket-binding="jgroups-mping"/>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD_ALL"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="MFC"/>
> <protocol type="FRAG3"/>
> </stack>
> </stacks>
> </subsystem>
> {noformat}
> The problem is that, after one node of the cluster is shut down and restarted, the remaining nodes fail to shut-down gracefully and their JVM has to be killed.
> The default shut-down waiting time is 1 minute: it has been extended to 5 but the nodes still fail to shut-down even in 5 minutes.
> Find attached:
> - the complete log of one node failing to shut-down (17293.log)
> - the thread dump of this node just before being killed (after a 5 minutes time-out) (perf20-consoleText.txt)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFCORE-3976) service.bat script add support for environment variables
by Florent Amaridon (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3976?page=com.atlassian.jira.plugi... ]
Florent Amaridon commented on WFCORE-3976:
------------------------------------------
Thank you I will make the pull request.
> service.bat script add support for environment variables
> --------------------------------------------------------
>
> Key: WFCORE-3976
> URL: https://issues.jboss.org/browse/WFCORE-3976
> Project: WildFly Core
> Issue Type: Feature Request
> Environment: All windows OS
> Reporter: Florent Amaridon
> Assignee: Jason Greene
> Priority: Minor
> Attachments: service.bat
>
>
> Hello,
> I'm using wildly as my application server. To provide customizable configuration I want to use STANDALONE_CONF environement variable.
> This works fine with stanalone.bat but when I try to install wildfly as a service I can't set this environment variable to service.bat.
> I wrote an unpdate to service.bat to handle environment variables.
> Can I make a pull request on github?
> Best regards
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2874) Select a data type, inline, from DMN decision tables.
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2874?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-2874:
----------------------------------------
[~uxdlc] Yes, when the edit/pencil button is removed the "Name" {{TextBox}} and "Data type" selector will be aligned on the Y-axis.
> Select a data type, inline, from DMN decision tables.
> -----------------------------------------------------
>
> Key: DROOLS-2874
> URL: https://issues.jboss.org/browse/DROOLS-2874
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, pop-overc.png, select.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to *select* a data type inline from a decision table.
> *
> Functional considerations/ pre conditions:
> * Actions will be offered or spawned inline within the cells of decision tables.
> * Design needs to be consistent with Stunner and PF components.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-10917) Server fails to shutdown
by tommaso borgato (JIRA)
[ https://issues.jboss.org/browse/WFLY-10917?page=com.atlassian.jira.plugin... ]
tommaso borgato updated WFLY-10917:
-----------------------------------
Description:
Affected scenario is {{[perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt/]}}: it is a 4 nodes fail-over scenario where JGroups communication is encrypted asymmetrically:
{noformat}
<subsystem xmlns="urn:jboss:domain:jgroups:6.0" default-stack="udp">
<channels default="ee">
<channel name="ee" stack="udp" cluster="ejb"/>
</channels>
<stacks>
<stack name="udp">
<transport type="UDP" socket-binding="jgroups-udp"/>
<protocol type="PING"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="ASYM_ENCRYPT" xmlns="">
<property name="encrypt_entire_message">true</property>
<property name="sym_keylength">128</property>
<property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
<property name="asym_keylength">512</property>
<property name="asym_algorithm">RSA</property>
</protocol>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="AUTH" xmlns="">
<property name="auth_class">org.jgroups.auth.MD5Token</property>
<property name="auth_value">MyPassword</property>
<property name="token_hash">MD5</property>
</protocol>
<protocol type="pbcast.GMS"/>
<protocol type="UFC"/>
<protocol type="MFC"/>
<protocol type="FRAG3"/>
</stack>
<stack name="tcp">
<transport type="TCP" socket-binding="jgroups-tcp"/>
<socket-protocol type="MPING" socket-binding="jgroups-mping"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG3"/>
</stack>
</stacks>
</subsystem>
{noformat}
The problem is that, after one node of the cluster is shut down and restarted, the remaining nodes fail to shut-down gracefully and their JVM has to be killed.
The default shut-down waiting time is 1 minute: it has been extended to 5 but the nodes still fail to shut-down even in 5 minutes.
Find attached:
- the complete log of one node failing to shut-down (17293.log)
- the thread dump of this node just before being killed (after a 5 minutes time-out) (perf20-consoleText.txt)
was:
Affected scenario is {{[perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt/]}}: it is a 4 nodes fail-over scenario where JGroups communication is encrypted asymmetrically:
{noformat}
<subsystem xmlns="urn:jboss:domain:jgroups:6.0" default-stack="udp">
<channels default="ee">
<channel name="ee" stack="udp" cluster="ejb"/>
</channels>
<stacks>
<stack name="udp">
<transport type="UDP" socket-binding="jgroups-udp"/>
<protocol type="PING"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="ASYM_ENCRYPT" xmlns="">
<property name="encrypt_entire_message">true</property>
<property name="sym_keylength">128</property>
<property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
<property name="asym_keylength">512</property>
<property name="asym_algorithm">RSA</property>
</protocol>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="AUTH" xmlns="">
<property name="auth_class">org.jgroups.auth.MD5Token</property>
<property name="auth_value">MyPassword</property>
<property name="token_hash">MD5</property>
</protocol>
<protocol type="pbcast.GMS"/>
<protocol type="UFC"/>
<protocol type="MFC"/>
<protocol type="FRAG3"/>
</stack>
<stack name="tcp">
<transport type="TCP" socket-binding="jgroups-tcp"/>
<socket-protocol type="MPING" socket-binding="jgroups-mping"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG3"/>
</stack>
</stacks>
</subsystem>
{noformat}
The problem is that, after one node of the cluster is shut down and restarted, the remaining nodes fail to shut-down gracefully and their JVM has to be killed.
The default shut-down is 1 minute: it has been extended to 5 but the nodes still fail to shut-down.
Find attached:
- the complete log of one node failing to shut-down (17293.log)
- the thread dump of this node just before being killed (after a 5 minutes time-out) (perf20-consoleText.txt)
> Server fails to shutdown
> -------------------------
>
> Key: WFLY-10917
> URL: https://issues.jboss.org/browse/WFLY-10917
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 14.0.0.CR1
> Reporter: tommaso borgato
> Assignee: Paul Ferraro
> Attachments: 17293.log, perf20-consoleText.txt
>
>
> Affected scenario is {{[perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt/]}}: it is a 4 nodes fail-over scenario where JGroups communication is encrypted asymmetrically:
> {noformat}
> <subsystem xmlns="urn:jboss:domain:jgroups:6.0" default-stack="udp">
> <channels default="ee">
> <channel name="ee" stack="udp" cluster="ejb"/>
> </channels>
> <stacks>
> <stack name="udp">
> <transport type="UDP" socket-binding="jgroups-udp"/>
> <protocol type="PING"/>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD_ALL"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="ASYM_ENCRYPT" xmlns="">
> <property name="encrypt_entire_message">true</property>
> <property name="sym_keylength">128</property>
> <property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
> <property name="asym_keylength">512</property>
> <property name="asym_algorithm">RSA</property>
> </protocol>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="AUTH" xmlns="">
> <property name="auth_class">org.jgroups.auth.MD5Token</property>
> <property name="auth_value">MyPassword</property>
> <property name="token_hash">MD5</property>
> </protocol>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG3"/>
> </stack>
> <stack name="tcp">
> <transport type="TCP" socket-binding="jgroups-tcp"/>
> <socket-protocol type="MPING" socket-binding="jgroups-mping"/>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD_ALL"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="MFC"/>
> <protocol type="FRAG3"/>
> </stack>
> </stacks>
> </subsystem>
> {noformat}
> The problem is that, after one node of the cluster is shut down and restarted, the remaining nodes fail to shut-down gracefully and their JVM has to be killed.
> The default shut-down waiting time is 1 minute: it has been extended to 5 but the nodes still fail to shut-down even in 5 minutes.
> Find attached:
> - the complete log of one node failing to shut-down (17293.log)
> - the thread dump of this node just before being killed (after a 5 minutes time-out) (perf20-consoleText.txt)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-10917) Server fails to shutdown
by tommaso borgato (JIRA)
[ https://issues.jboss.org/browse/WFLY-10917?page=com.atlassian.jira.plugin... ]
tommaso borgato updated WFLY-10917:
-----------------------------------
Description:
Affected scenario is {{[perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt/]}}: it is a 4 nodes fail-over scenario where JGroups communication is encrypted asymmetrically:
{noformat}
<subsystem xmlns="urn:jboss:domain:jgroups:6.0" default-stack="udp">
<channels default="ee">
<channel name="ee" stack="udp" cluster="ejb"/>
</channels>
<stacks>
<stack name="udp">
<transport type="UDP" socket-binding="jgroups-udp"/>
<protocol type="PING"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="ASYM_ENCRYPT" xmlns="">
<property name="encrypt_entire_message">true</property>
<property name="sym_keylength">128</property>
<property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
<property name="asym_keylength">512</property>
<property name="asym_algorithm">RSA</property>
</protocol>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="AUTH" xmlns="">
<property name="auth_class">org.jgroups.auth.MD5Token</property>
<property name="auth_value">MyPassword</property>
<property name="token_hash">MD5</property>
</protocol>
<protocol type="pbcast.GMS"/>
<protocol type="UFC"/>
<protocol type="MFC"/>
<protocol type="FRAG3"/>
</stack>
<stack name="tcp">
<transport type="TCP" socket-binding="jgroups-tcp"/>
<socket-protocol type="MPING" socket-binding="jgroups-mping"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG3"/>
</stack>
</stacks>
</subsystem>
{noformat}
The problem is that, after one node of the cluster is shut down and restarted, the remaining nodes fail to shut-down gracefully and their JVM has to be killed.
The default shut-down is 1 minute: it has been extended to 5 but the nodes still fail to shut-down.
Find attached:
- the complete log of one node failing to shut-down (17293.log)
- the thread dump of this node just before being killed (after a 5 minutes time-out) (perf20-consoleText.txt)
was:
Affected scenario is {{[perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt/]}}: it is a 4 nodes fail-over scenario where JGroups communication is encrypted asymmetrically:
{noformat}
<subsystem xmlns="urn:jboss:domain:jgroups:6.0" default-stack="udp">
<channels default="ee">
<channel name="ee" stack="udp" cluster="ejb"/>
</channels>
<stacks>
<stack name="udp">
<transport type="UDP" socket-binding="jgroups-udp"/>
<protocol type="PING"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="ASYM_ENCRYPT" xmlns="">
<property name="encrypt_entire_message">true</property>
<property name="sym_keylength">128</property>
<property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
<property name="asym_keylength">512</property>
<property name="asym_algorithm">RSA</property>
</protocol>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="AUTH" xmlns="">
<property name="auth_class">org.jgroups.auth.MD5Token</property>
<property name="auth_value">MyPassword</property>
<property name="token_hash">MD5</property>
</protocol>
<protocol type="pbcast.GMS"/>
<protocol type="UFC"/>
<protocol type="MFC"/>
<protocol type="FRAG3"/>
</stack>
<stack name="tcp">
<transport type="TCP" socket-binding="jgroups-tcp"/>
<socket-protocol type="MPING" socket-binding="jgroups-mping"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG3"/>
</stack>
</stacks>
</subsystem>
{noformat}
The problem is that, after one node of the cluster fails and restart, the remaining nodes fail to shut-down gracefully and their JVM has to be killed.
The default shut-down is 1 minute: it has been extended to 5 but the nodes still fail to shut-down.
Find attached:
- the complete log of one node failing to shut-down (17293.log)
- the thread dump of this node just before being killed (after a 5 minutes time-out) (perf20-consoleText.txt)
> Server fails to shutdown
> -------------------------
>
> Key: WFLY-10917
> URL: https://issues.jboss.org/browse/WFLY-10917
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 14.0.0.CR1
> Reporter: tommaso borgato
> Assignee: Paul Ferraro
> Attachments: 17293.log, perf20-consoleText.txt
>
>
> Affected scenario is {{[perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt/]}}: it is a 4 nodes fail-over scenario where JGroups communication is encrypted asymmetrically:
> {noformat}
> <subsystem xmlns="urn:jboss:domain:jgroups:6.0" default-stack="udp">
> <channels default="ee">
> <channel name="ee" stack="udp" cluster="ejb"/>
> </channels>
> <stacks>
> <stack name="udp">
> <transport type="UDP" socket-binding="jgroups-udp"/>
> <protocol type="PING"/>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD_ALL"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="ASYM_ENCRYPT" xmlns="">
> <property name="encrypt_entire_message">true</property>
> <property name="sym_keylength">128</property>
> <property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
> <property name="asym_keylength">512</property>
> <property name="asym_algorithm">RSA</property>
> </protocol>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="AUTH" xmlns="">
> <property name="auth_class">org.jgroups.auth.MD5Token</property>
> <property name="auth_value">MyPassword</property>
> <property name="token_hash">MD5</property>
> </protocol>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG3"/>
> </stack>
> <stack name="tcp">
> <transport type="TCP" socket-binding="jgroups-tcp"/>
> <socket-protocol type="MPING" socket-binding="jgroups-mping"/>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD_ALL"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="MFC"/>
> <protocol type="FRAG3"/>
> </stack>
> </stacks>
> </subsystem>
> {noformat}
> The problem is that, after one node of the cluster is shut down and restarted, the remaining nodes fail to shut-down gracefully and their JVM has to be killed.
> The default shut-down is 1 minute: it has been extended to 5 but the nodes still fail to shut-down.
> Find attached:
> - the complete log of one node failing to shut-down (17293.log)
> - the thread dump of this node just before being killed (after a 5 minutes time-out) (perf20-consoleText.txt)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-10917) Server fails to shutdown
by tommaso borgato (JIRA)
tommaso borgato created WFLY-10917:
--------------------------------------
Summary: Server fails to shutdown
Key: WFLY-10917
URL: https://issues.jboss.org/browse/WFLY-10917
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 14.0.0.CR1
Reporter: tommaso borgato
Assignee: Paul Ferraro
Attachments: 17293.log, perf20-consoleText.txt
Affected scenario is {{[perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt/]}}: it is a 4 nodes fail-over scenario where JGroups communication is encrypted asymmetrically:
{noformat}
<subsystem xmlns="urn:jboss:domain:jgroups:6.0" default-stack="udp">
<channels default="ee">
<channel name="ee" stack="udp" cluster="ejb"/>
</channels>
<stacks>
<stack name="udp">
<transport type="UDP" socket-binding="jgroups-udp"/>
<protocol type="PING"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="ASYM_ENCRYPT" xmlns="">
<property name="encrypt_entire_message">true</property>
<property name="sym_keylength">128</property>
<property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
<property name="asym_keylength">512</property>
<property name="asym_algorithm">RSA</property>
</protocol>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="AUTH" xmlns="">
<property name="auth_class">org.jgroups.auth.MD5Token</property>
<property name="auth_value">MyPassword</property>
<property name="token_hash">MD5</property>
</protocol>
<protocol type="pbcast.GMS"/>
<protocol type="UFC"/>
<protocol type="MFC"/>
<protocol type="FRAG3"/>
</stack>
<stack name="tcp">
<transport type="TCP" socket-binding="jgroups-tcp"/>
<socket-protocol type="MPING" socket-binding="jgroups-mping"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG3"/>
</stack>
</stacks>
</subsystem>
{noformat}
The problem is that, after one node of the cluster fails and restart, the remaining nodes fail to shut-down gracefully and their JVM has to be killed.
The default shut-down is 1 minute: it has been extended to 5 but the nodes still fail to shut-down.
Find attached:
- the complete log of one node failing to shut-down (17293.log)
- the thread dump of this node just before being killed (after a 5 minutes time-out) (perf20-consoleText.txt)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2874) Select a data type, inline, from DMN decision tables.
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2874?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2874:
-------------------------------------
[~manstis] ok, thanks I understand. I'm principally interested in the alignment of dropdown input with the dropdown list. Once the Edit button to the left of the selector is removed, will the two elements left align along the same axis?
!Screen Shot 2018-08-24 at 8.38.37 AM.png|thumbnail!
> Select a data type, inline, from DMN decision tables.
> -----------------------------------------------------
>
> Key: DROOLS-2874
> URL: https://issues.jboss.org/browse/DROOLS-2874
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, pop-overc.png, select.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to *select* a data type inline from a decision table.
> *
> Functional considerations/ pre conditions:
> * Actions will be offered or spawned inline within the cells of decision tables.
> * Design needs to be consistent with Stunner and PF components.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months