[JBoss JIRA] (DROOLS-3260) [DMN Designer] UX documentation: Grid cell editing interactions (single/dbl click)
by Liz Clayton (Jira)
Liz Clayton created DROOLS-3260:
-----------------------------------
Summary: [DMN Designer] UX documentation: Grid cell editing interactions (single/dbl click)
Key: DROOLS-3260
URL: https://issues.jboss.org/browse/DROOLS-3260
Project: Drools
Issue Type: Feature Request
Components: DMN Editor
Affects Versions: 7.10.0.Final
Reporter: Liz Clayton
Assignee: Michael Anstis
Following from a discussion about https://issues.jboss.org/browse/DROOLS-2874 it was agreed that editing cells (header or body) in the grids should respond to single-click and not double-click.
h2. Manual Acceptance Test
- Not possible edit multiple cells by hold CTRL and click on multiple cells
- Click column/row leading cell discard edit dialog
- Edit can be discarded by escape
- Edit can be discarded by click to canvas
- Invoke edit of cell, return do DRG
- Save and reopen
- Undo redo of editation
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3260) [DMN Designer] UX documentation: Grid cell editing interactions (single/dbl click)
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3260?page=com.atlassian.jira.plugi... ]
Liz Clayton reassigned DROOLS-3260:
-----------------------------------
Assignee: Liz Clayton (was: Michael Anstis)
> [DMN Designer] UX documentation: Grid cell editing interactions (single/dbl click)
> -----------------------------------------------------------------------------------
>
> Key: DROOLS-3260
> URL: https://issues.jboss.org/browse/DROOLS-3260
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Affects Versions: 7.10.0.Final
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> Following from a discussion about https://issues.jboss.org/browse/DROOLS-2874 it was agreed that editing cells (header or body) in the grids should respond to single-click and not double-click.
> h2. Manual Acceptance Test
> - Not possible edit multiple cells by hold CTRL and click on multiple cells
> - Click column/row leading cell discard edit dialog
> - Edit can be discarded by escape
> - Edit can be discarded by click to canvas
> - Invoke edit of cell, return do DRG
> - Save and reopen
> - Undo redo of editation
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3259) [DMN Designer] `inputData` and `variable` must have the same name value
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3259?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3259:
---------------------------------------
Summary: [DMN Designer] `inputData` and `variable` must have the same name value (was: [DMN Designer] `inputData` and `variable` must have the name value in the attribute `name`)
> [DMN Designer] `inputData` and `variable` must have the same name value
> -----------------------------------------------------------------------
>
> Key: DROOLS-3259
> URL: https://issues.jboss.org/browse/DROOLS-3259
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: diagram.png, dtable.png
>
>
> When the user persists the following diagram:
> !diagram.png|thumbnail!
> ..with the following Decision Table:
> !dtable.png|thumbnail!
> .. the {{inputData}} and {{variable}} tags don't have the same {{name}} value in the attribute {{name}}, see:
> {quote}<dmn:inputData id="_67412B2F-A661-48C6-971C-6E184A519592" name="Country">
> <dmn:variable id="_8F4476AB-1BEB-4FDB-8192-73BB0A520236" name="" typeRef="string"></dmn:variable>{quote}
> The expected behaviour is this:
> {quote}<dmn:inputData id="_67412B2F-A661-48C6-971C-6E184A519592" name="Country">
> <dmn:variable id="_8F4476AB-1BEB-4FDB-8192-73BB0A520236" name="Country" typeRef="string"></dmn:variable>{quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3259) [DMN Designer] `inputData` and `variable` must have the name value in the attribute `name`
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3259?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3259:
---------------------------------------
Description:
When the user persists the following diagram:
!diagram.png|thumbnail!
..with the following Decision Table:
!dtable.png|thumbnail!
.. the {{inputData}} and {{variable}} tags don't have the same {{name}} value in the attribute {{name}}, see:
{quote}<dmn:inputData id="_67412B2F-A661-48C6-971C-6E184A519592" name="Country">
<dmn:variable id="_8F4476AB-1BEB-4FDB-8192-73BB0A520236" name="" typeRef="string"></dmn:variable>{quote}
The expected behaviour is this:
{quote}<dmn:inputData id="_67412B2F-A661-48C6-971C-6E184A519592" name="Country">
<dmn:variable id="_8F4476AB-1BEB-4FDB-8192-73BB0A520236" name="Country" typeRef="string"></dmn:variable>{quote}
was:
When the user persists the following diagram:
!diagram.png|thumbnail!
..with the following Decision Table:
!dtable.png|thumbnail!
.. the `inputData` and `variable` don't have the same name value in the attribute `name`, see:
{quote}<dmn:inputData id="_67412B2F-A661-48C6-971C-6E184A519592" name="Country">
<dmn:variable id="_8F4476AB-1BEB-4FDB-8192-73BB0A520236" name="" typeRef="string"></dmn:variable>{quote}
The expected behaviour is this:
{quote}<dmn:inputData id="_67412B2F-A661-48C6-971C-6E184A519592" name="Country">
<dmn:variable id="_8F4476AB-1BEB-4FDB-8192-73BB0A520236" name="Country" typeRef="string"></dmn:variable>{quote}
> [DMN Designer] `inputData` and `variable` must have the name value in the attribute `name`
> ------------------------------------------------------------------------------------------
>
> Key: DROOLS-3259
> URL: https://issues.jboss.org/browse/DROOLS-3259
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: diagram.png, dtable.png
>
>
> When the user persists the following diagram:
> !diagram.png|thumbnail!
> ..with the following Decision Table:
> !dtable.png|thumbnail!
> .. the {{inputData}} and {{variable}} tags don't have the same {{name}} value in the attribute {{name}}, see:
> {quote}<dmn:inputData id="_67412B2F-A661-48C6-971C-6E184A519592" name="Country">
> <dmn:variable id="_8F4476AB-1BEB-4FDB-8192-73BB0A520236" name="" typeRef="string"></dmn:variable>{quote}
> The expected behaviour is this:
> {quote}<dmn:inputData id="_67412B2F-A661-48C6-971C-6E184A519592" name="Country">
> <dmn:variable id="_8F4476AB-1BEB-4FDB-8192-73BB0A520236" name="Country" typeRef="string"></dmn:variable>{quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3259) [DMN Designer] `inputData` and `variable` must have the name value in the attribute `name`
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3259?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3259:
---------------------------------------
Attachment: dtable.png
> [DMN Designer] `inputData` and `variable` must have the name value in the attribute `name`
> ------------------------------------------------------------------------------------------
>
> Key: DROOLS-3259
> URL: https://issues.jboss.org/browse/DROOLS-3259
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: diagram.png, dtable.png
>
>
> When the user persists the following diagram:
> ..with the following Decision Table:
> .. the `inputData` and `variable` don't have the same name value in the attribute `name`, see:
> {{
> <dmn:inputData id="_67412B2F-A661-48C6-971C-6E184A519592" name="Country">
> <dmn:variable id="_8F4476AB-1BEB-4FDB-8192-73BB0A520236" name="" typeRef="string"></dmn:variable>
> }}
> The expected behaviour is this:
> {{
> {{
> <dmn:inputData id="_67412B2F-A661-48C6-971C-6E184A519592" name="Country">
> <dmn:variable id="_8F4476AB-1BEB-4FDB-8192-73BB0A520236" name="Country" typeRef="string"></dmn:variable>
> }}
> }}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3259) [DMN Designer] `inputData` and `variable` must have the name value in the attribute `name`
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3259?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3259:
---------------------------------------
Description:
When the user persists the following diagram:
!diagram.png|thumbnail!
..with the following Decision Table:
!dtable.png|thumbnail!
.. the `inputData` and `variable` don't have the same name value in the attribute `name`, see:
{quote}<dmn:inputData id="_67412B2F-A661-48C6-971C-6E184A519592" name="Country">
<dmn:variable id="_8F4476AB-1BEB-4FDB-8192-73BB0A520236" name="" typeRef="string"></dmn:variable>{quote}
The expected behaviour is this:
{quote}<dmn:inputData id="_67412B2F-A661-48C6-971C-6E184A519592" name="Country">
<dmn:variable id="_8F4476AB-1BEB-4FDB-8192-73BB0A520236" name="Country" typeRef="string"></dmn:variable>{quote}
was:
When the user persists the following diagram:
..with the following Decision Table:
.. the `inputData` and `variable` don't have the same name value in the attribute `name`, see:
{{
<dmn:inputData id="_67412B2F-A661-48C6-971C-6E184A519592" name="Country">
<dmn:variable id="_8F4476AB-1BEB-4FDB-8192-73BB0A520236" name="" typeRef="string"></dmn:variable>
}}
The expected behaviour is this:
{{
{{
<dmn:inputData id="_67412B2F-A661-48C6-971C-6E184A519592" name="Country">
<dmn:variable id="_8F4476AB-1BEB-4FDB-8192-73BB0A520236" name="Country" typeRef="string"></dmn:variable>
}}
}}
> [DMN Designer] `inputData` and `variable` must have the name value in the attribute `name`
> ------------------------------------------------------------------------------------------
>
> Key: DROOLS-3259
> URL: https://issues.jboss.org/browse/DROOLS-3259
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: diagram.png, dtable.png
>
>
> When the user persists the following diagram:
> !diagram.png|thumbnail!
> ..with the following Decision Table:
> !dtable.png|thumbnail!
> .. the `inputData` and `variable` don't have the same name value in the attribute `name`, see:
> {quote}<dmn:inputData id="_67412B2F-A661-48C6-971C-6E184A519592" name="Country">
> <dmn:variable id="_8F4476AB-1BEB-4FDB-8192-73BB0A520236" name="" typeRef="string"></dmn:variable>{quote}
> The expected behaviour is this:
> {quote}<dmn:inputData id="_67412B2F-A661-48C6-971C-6E184A519592" name="Country">
> <dmn:variable id="_8F4476AB-1BEB-4FDB-8192-73BB0A520236" name="Country" typeRef="string"></dmn:variable>{quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3259) [DMN Designer] `inputData` and `variable` must have the name value in the attribute `name`
by Guilherme Carreiro (Jira)
Guilherme Carreiro created DROOLS-3259:
------------------------------------------
Summary: [DMN Designer] `inputData` and `variable` must have the name value in the attribute `name`
Key: DROOLS-3259
URL: https://issues.jboss.org/browse/DROOLS-3259
Project: Drools
Issue Type: Bug
Components: DMN Editor
Reporter: Guilherme Carreiro
Assignee: Michael Anstis
Attachments: diagram.png
When the user persists the following diagram:
..with the following Decision Table:
.. the `inputData` and `variable` don't have the same name value in the attribute `name`, see:
{{
<dmn:inputData id="_67412B2F-A661-48C6-971C-6E184A519592" name="Country">
<dmn:variable id="_8F4476AB-1BEB-4FDB-8192-73BB0A520236" name="" typeRef="string"></dmn:variable>
}}
The expected behaviour is this:
{{
{{
<dmn:inputData id="_67412B2F-A661-48C6-971C-6E184A519592" name="Country">
<dmn:variable id="_8F4476AB-1BEB-4FDB-8192-73BB0A520236" name="Country" typeRef="string"></dmn:variable>
}}
}}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFCORE-4115) JDK11 - GC logging format needs to be reviewed
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFCORE-4115?page=com.atlassian.jira.plugi... ]
James Perkins updated WFCORE-4115:
----------------------------------
Attachment: java-8-gc.log
java-11-gc.log
> JDK11 - GC logging format needs to be reviewed
> ----------------------------------------------
>
> Key: WFCORE-4115
> URL: https://issues.jboss.org/browse/WFCORE-4115
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts, Server
> Reporter: Marek Kopecký
> Assignee: James Perkins
> Priority: Major
> Labels: Java11, jdk11
> Attachments: java-11-gc.log, java-8-gc.log
>
>
> * Weird naming of gc log files
> ** I test this with JDK11
> ** I start standalone and stop standalone
> ** JDK10 creates JBOSS_HOME/standalone/log/gc.log (with detailed information) and JBOSS_HOME/standalone/log/gc.log.0 (with brief summary of gc logging)
> ** I start standalone and stop standalone again
> ** JDK10 moves original gc.log to gc.log.1
> ** JDK10 keep original gc.log.0
> ** JDK10 creates new gc.log (with detailed information) and gc.log.2 (with brief summary of gc logging)
> ** Can this be changed by GC settings?
> * GC logs are much more verbose against jdk8 gc logs. Can this be fixed by some JDK10 gc settings?
> This is follow up for WFCORE-3996
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFCORE-4115) JDK11 - GC logging format needs to be reviewed
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFCORE-4115?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-4115:
---------------------------------------
[~aogburn] I've attached a Java 8 and Java 11 GC log file so you can see the difference.
> JDK11 - GC logging format needs to be reviewed
> ----------------------------------------------
>
> Key: WFCORE-4115
> URL: https://issues.jboss.org/browse/WFCORE-4115
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts, Server
> Reporter: Marek Kopecký
> Assignee: James Perkins
> Priority: Major
> Labels: Java11, jdk11
> Attachments: java-11-gc.log, java-8-gc.log
>
>
> * Weird naming of gc log files
> ** I test this with JDK11
> ** I start standalone and stop standalone
> ** JDK10 creates JBOSS_HOME/standalone/log/gc.log (with detailed information) and JBOSS_HOME/standalone/log/gc.log.0 (with brief summary of gc logging)
> ** I start standalone and stop standalone again
> ** JDK10 moves original gc.log to gc.log.1
> ** JDK10 keep original gc.log.0
> ** JDK10 creates new gc.log (with detailed information) and gc.log.2 (with brief summary of gc logging)
> ** Can this be changed by GC settings?
> * GC logs are much more verbose against jdk8 gc logs. Can this be fixed by some JDK10 gc settings?
> This is follow up for WFCORE-3996
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (JGRP-2300) DNS_PING in AWS ECS cannot cluster with dynamic port mappings
by Eric Thompson (Jira)
[ https://issues.jboss.org/browse/JGRP-2300?page=com.atlassian.jira.plugin.... ]
Eric Thompson commented on JGRP-2300:
-------------------------------------
[~sebastian.laskawiec] and [~belaban] Sorry! My management has asked that I not put anymore work into this at this time. We are just running ECS with small instances and only one container per instance until this is resolved. It is not ideal, but I have other priorities I need to get on with.
I do look forward to testing any fixes that you might come up with. And when it is fixed we will use the fix in Production, if it works for our needs.
> DNS_PING in AWS ECS cannot cluster with dynamic port mappings
> -------------------------------------------------------------
>
> Key: JGRP-2300
> URL: https://issues.jboss.org/browse/JGRP-2300
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.16
> Environment: AWS ECS Cluster with DNS based service discovery using jboss/keycloak:latest containers
> Reporter: Eric Thompson
> Assignee: Sebastian Łaskawiec
> Priority: Critical
> Fix For: 4.0.16
>
>
> When running an ECS cluster with jboss/keycloak:latest containers dynamic port mapping of all ports is required to allow more than one container to run per EC2 instance. Using SRV based service discovery records will allow each node to find the rest of the nodes, but when a discovery request is sent the receiving node sees the sender as IP:7600 instead of the dynamic port. It then sees this as a "new" node and tries to send discovery requests to it. And somehow it is also getting node IDs and trying to send requests to those!
> See the following log, there are only 4 actual nodes and the each have a different 5 digit port number:
> {code}
> ### Service discovery with dynamic port mapping
> 2018-10-10 20:17:44,178 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-240,ejb,17081c624290) Performing discovery of the following hosts [10.42.3.44:7600, 10.42.3.56:32949, 10.42.3.56:32951, 10.42.3.44:32954, c5b479b7b6d5, 10.42.3.44:32952, 10.42.3.56:7600, 17081c624290, 63976b7fae70, 557cbd7891a2]
> 2018-10-10 20:17:44,178 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-240,ejb,17081c624290) 17081c624290: sending discovery request to 10.42.3.44:7600
> 2018-10-10 20:17:44,179 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-240,ejb,17081c624290) 17081c624290: sending discovery request to 10.42.3.56:32949
> 2018-10-10 20:17:44,179 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-240,ejb,17081c624290) 17081c624290: sending discovery request to 10.42.3.56:32951
> 2018-10-10 20:17:44,180 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-240,ejb,17081c624290) 17081c624290: sending discovery request to 10.42.3.44:32954
> 2018-10-10 20:17:44,181 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-240,ejb,17081c624290) 17081c624290: sending discovery request to c5b479b7b6d5
> 2018-10-10 20:17:44,181 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-240,ejb,17081c624290) 17081c624290: sending discovery request to 10.42.3.44:32952
> 2018-10-10 20:17:44,181 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-240,ejb,17081c624290) 17081c624290: sending discovery request to 10.42.3.56:7600
> 2018-10-10 20:17:44,182 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-237,ejb,17081c624290) Received discovery from: 17081c624290, IP: 10.42.3.56:7600
> 2018-10-10 20:17:44,182 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-240,ejb,17081c624290) 17081c624290: sending discovery request to 17081c624290
> 2018-10-10 20:17:44,182 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-238,ejb,17081c624290) Received discovery from: 17081c624290, IP: 10.42.3.56:7600
> 2018-10-10 20:17:44,182 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-240,ejb,17081c624290) 17081c624290: sending discovery request to 63976b7fae70
> 2018-10-10 20:17:44,183 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-240,ejb,17081c624290) 17081c624290: sending discovery request to 557cbd7891a2
> 2018-10-10 20:17:44,187 WARN [org.jgroups.protocols.TCP] (TQ-Bundler-7,ejb,17081c624290) JGRP000032: 17081c624290: no physical address for c5b479b7b6d5, dropping message
> {code}
> This code seems to be part of the problem in this case: https://github.com/belaban/JGroups/blob/87d15ec848aa3d482ae792ef152f7e36e...
> See that code uses the incoming address and adds it to the discocvered_hosts, but those addresses are ALWAYS inaccurate in this case.
> Because this is what the recipient of the service discovery request sees (ie: all the ports are the default 7600):
> {code}
> 2018-10-10 20:35:15,229 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-350,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:15,231 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-350,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:15,232 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-397,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:15,233 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-350,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:17,234 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-350,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:17,236 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-350,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:17,238 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-397,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:17,238 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-350,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:19,239 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-350,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:19,240 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-350,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:19,242 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-237,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:19,243 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-350,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:21,246 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-350,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:21,247 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-350,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:21,253 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-237,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:21,253 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-350,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:23,247 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-350,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:23,249 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-350,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:23,251 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-237,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:23,251 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-350,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:25,252 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-237,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:25,253 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-237,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:25,255 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-237,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> 2018-10-10 20:35:25,256 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-237,ejb,17081c624290) Received discovery from: 63976b7fae70, IP: 10.42.3.44:7600
> {code}
> In this state the cluster never seems to work properly and the Keycloak interface breaks in many frustrating ways.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months