[JBoss JIRA] (JGRP-1957) S3_PING: Nodes never removed from .list file
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1957?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1957:
--------------------------------
You haven't set {{logical_addr_cache_max_size}} which by default is 2000. So your cache won't get cleaned until it reaches 2000 entries even though most cache entries have expired.
This is by design as I want to minimize trips to a (possibly remote cloud) store.
> S3_PING: Nodes never removed from .list file
> --------------------------------------------
>
> Key: JGRP-1957
> URL: https://issues.jboss.org/browse/JGRP-1957
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.4
> Environment: JGroups client running on Mac OS X - Yosemite
> JDK 1.7.71
> Reporter: Nick Sawadsky
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.6.6
>
>
> I'm not 100% sure, but it seems like there might be a defect here.
> I'm using TCP, S3_PING, and MERGE3.
> I've set logical_addr_cache_max_size to 2 for testing purposes, although I don't think the value of this setting affects my test results.
> I start a single node, node A. Then I start a second node, node B.
> I then repeatedly shutdown and restart node B.
> Each time node B starts, a new row is added to the .list file stored in S3.
> But even if I continue this process for 15 minutes, old rows are never removed from the .list file, so it continues to grow in size.
> I've read the docs and mailing list threads, so I'm aware that the list is not immediately updated as soon as a member leaves. But I was expecting that when a view change occurs, nodes no longer in the view would be marked for removal (line 2193 of TP.java) and then after the logical_addr_cache_expiration has been reached and the reaper kicks in, once a new node joins, the expired cache entries would be purged from the file.
> I dug in to the code a bit, and what seems to be happening is that the MERGE3 protocol periodically generates a FIND_MBRS event. S3_PING retrieves the membership from the .list file, which includes expired nodes. And then all of these members are re-added to the logical address cache (line 157 of S3_PING.java, line 533 of Discovery.java, line 2263 of TP.java).
> So expired nodes are continually re-added to the logical address cache, preventing them from ever being reaped.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (WFCORE-1456) org.jboss.as.cli.scriptsupport.CLI prevents use of embed-server and embed-host-controller
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1456?page=com.atlassian.jira.plugi... ]
Alexey Loubyansky edited comment on WFCORE-1456 at 4/18/16 6:52 AM:
--------------------------------------------------------------------
Re-opening since the original PR had failing tests.
was (Author: aloubyansky):
Re-opening to since the original PR had failing tests.
> org.jboss.as.cli.scriptsupport.CLI prevents use of embed-server and embed-host-controller
> -----------------------------------------------------------------------------------------
>
> Key: WFCORE-1456
> URL: https://issues.jboss.org/browse/WFCORE-1456
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 2.1.0.Final
> Reporter: Brian Stansberry
> Assignee: Jean-Francois Denise
>
> The org.jboss.as.cli.scriptsupport.CLI will throw an exception if the user invokes the cmd method before invoking one of the connect methods. But the connect/disconnect methods are oriented toward remote connections. The result is you can't really use this class with the offline CLI.
> I'm not sure what the best fix is here. Perhaps new method(s) analogous to connect/disconnect that establish a CommandContext but don't call connectController(). Or perhaps the checkNotConnected() call in the cmd method should just be dropped, and an unconnected command context created. But then the existing connect/disconnect methods would need to be reworked to deal with the fact that an unconnected command context may be present.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (WFCORE-1456) org.jboss.as.cli.scriptsupport.CLI prevents use of embed-server and embed-host-controller
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1456?page=com.atlassian.jira.plugi... ]
Alexey Loubyansky reopened WFCORE-1456:
---------------------------------------
Re-opening to since the original PR had failing tests.
> org.jboss.as.cli.scriptsupport.CLI prevents use of embed-server and embed-host-controller
> -----------------------------------------------------------------------------------------
>
> Key: WFCORE-1456
> URL: https://issues.jboss.org/browse/WFCORE-1456
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 2.1.0.Final
> Reporter: Brian Stansberry
> Assignee: Jean-Francois Denise
>
> The org.jboss.as.cli.scriptsupport.CLI will throw an exception if the user invokes the cmd method before invoking one of the connect methods. But the connect/disconnect methods are oriented toward remote connections. The result is you can't really use this class with the offline CLI.
> I'm not sure what the best fix is here. Perhaps new method(s) analogous to connect/disconnect that establish a CommandContext but don't call connectController(). Or perhaps the checkNotConnected() call in the cmd method should just be dropped, and an unconnected command context created. But then the existing connect/disconnect methods would need to be reworked to deal with the fact that an unconnected command context may be present.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JGRP-2041) Getting Socketexception during cluster communication
by Rohit Singh (JIRA)
[ https://issues.jboss.org/browse/JGRP-2041?page=com.atlassian.jira.plugin.... ]
Rohit Singh commented on JGRP-2041:
-----------------------------------
our JVM does not get terminated when we do kill -3, it just creates thread dump and keep running. So was wondering if there is any different behavior with respect to JGroups.
> Getting Socketexception during cluster communication
> ----------------------------------------------------
>
> Key: JGRP-2041
> URL: https://issues.jboss.org/browse/JGRP-2041
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 2.5.2
> Environment: RHEL
> Reporter: Rohit Singh
> Assignee: Bela Ban
> Fix For: 4.0
>
> Attachments: jetty.log.D20160315.T074324.zip, jgroups_cluster.properties
>
>
> We faced issues during our cluster communication which is based on JGroup implementation.
> We got below errors in logs. JGroup does not even put full stacktrace of the SocketException.
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JGRP-2041) Getting Socketexception during cluster communication
by Rohit Singh (JIRA)
[ https://issues.jboss.org/browse/JGRP-2041?page=com.atlassian.jira.plugin.... ]
Rohit Singh commented on JGRP-2041:
-----------------------------------
This issue is not re-producible and happened only twice. I provided you with the configuration file which you have asked earlier.
Can you please confirm if the stack trace is printed completely when this error happens in later version of JGroups ?
Instead of just printing the error as we see below.
[172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed
> Getting Socketexception during cluster communication
> ----------------------------------------------------
>
> Key: JGRP-2041
> URL: https://issues.jboss.org/browse/JGRP-2041
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 2.5.2
> Environment: RHEL
> Reporter: Rohit Singh
> Assignee: Bela Ban
> Fix For: 4.0
>
> Attachments: jetty.log.D20160315.T074324.zip, jgroups_cluster.properties
>
>
> We faced issues during our cluster communication which is based on JGroup implementation.
> We got below errors in logs. JGroup does not even put full stacktrace of the SocketException.
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JGRP-2041) Getting Socketexception during cluster communication
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2041?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2041:
--------------------------------
Yes, kill -3 could also terminate a process.
Unless you give me more information (e.g.how to reproduce this etc), I'm going to close this issue. Also, I don't support older versions (such as 2.5.2) on a community basis.
> Getting Socketexception during cluster communication
> ----------------------------------------------------
>
> Key: JGRP-2041
> URL: https://issues.jboss.org/browse/JGRP-2041
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 2.5.2
> Environment: RHEL
> Reporter: Rohit Singh
> Assignee: Bela Ban
> Fix For: 4.0
>
> Attachments: jetty.log.D20160315.T074324.zip, jgroups_cluster.properties
>
>
> We faced issues during our cluster communication which is based on JGroup implementation.
> We got below errors in logs. JGroup does not even put full stacktrace of the SocketException.
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JGRP-2041) Getting Socketexception during cluster communication
by Rohit Singh (JIRA)
[ https://issues.jboss.org/browse/JGRP-2041?page=com.atlassian.jira.plugin.... ]
Rohit Singh updated JGRP-2041:
------------------------------
Attachment: jgroups_cluster.properties
> Getting Socketexception during cluster communication
> ----------------------------------------------------
>
> Key: JGRP-2041
> URL: https://issues.jboss.org/browse/JGRP-2041
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 2.5.2
> Environment: RHEL
> Reporter: Rohit Singh
> Assignee: Bela Ban
> Fix For: 4.0
>
> Attachments: jetty.log.D20160315.T074324.zip, jgroups_cluster.properties
>
>
> We faced issues during our cluster communication which is based on JGroup implementation.
> We got below errors in logs. JGroup does not even put full stacktrace of the SocketException.
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] ERROR org.jgroups.blocks.ConnectionTable - exception is java.net.SocketException: Socket closed
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated
> [2016-03-15 08:00:29.523] ALL 000000000000 GLOBAL_SCOPE 202575944 [ConnectionTable.Connection.Sender local_addr=172.27.105.93:11060 [172.27.105.93:34535 - 172.27.105.94:11060]] DEBUG org.jgroups.blocks.ConnectionTable - ConnectionTable.Connection.Sender thread terminated
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years