[JBoss JIRA] (JGRP-2253) FD_SOCK is not working in AWS environment
by Sibin Karnavar (JIRA)
[ https://issues.jboss.org/browse/JGRP-2253?page=com.atlassian.jira.plugin.... ]
Sibin Karnavar commented on JGRP-2253:
--------------------------------------
Please ignore the above questions. I have opened a new JIRA for it since this is already closed.
> FD_SOCK is not working in AWS environment
> -----------------------------------------
>
> Key: JGRP-2253
> URL: https://issues.jboss.org/browse/JGRP-2253
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.10
> Environment: AWS - EC2
> Reporter: Sibin Karnavar
> Assignee: Bela Ban
>
> We have our failure detection defined like below.
> <FD_SOCK external_port="7804" />
> <FD timeout="3000" max_tries="3" />
> <VERIFY_SUSPECT timeout="3000" />
> Please note that we have used FD instead of FD_ALL in AWS. We will be changing it to FD_ALL later after detailed testing.
> In my local, this is working perfect. As soon as I kill my node, I was able to see that view change was happening immediately with FD_SOCK.
> We were not mentioning the external_port in the FD_SOCK but later I thought it may be an issue with the port and defined it as 7804 and added the same port to the security group that allows to access this port among all the nodes. So no issue with the port.
> Can you please let us know if we need any additional configurations to make FD_SOCK works well in AWS.
> Thanks,
> Sibin
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (SWSQE-52) Automation SWS-QE: Initial Test Framework Setup
by Hayk Hovsepyan (JIRA)
Hayk Hovsepyan created SWSQE-52:
-----------------------------------
Summary: Automation SWS-QE: Initial Test Framework Setup
Key: SWSQE-52
URL: https://issues.jboss.org/browse/SWSQE-52
Project: Swift Sunshine QE
Issue Type: Task
Reporter: Hayk Hovsepyan
Assignee: Hayk Hovsepyan
Should be able to run Selenium tests at least on one supported Browser.
Be able to create first test method on "Services" page by touching only test classes.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JGRP-2256) Connection.Receiver - Failed handling incoming message
by Sibin Karnavar (JIRA)
[ https://issues.jboss.org/browse/JGRP-2256?page=com.atlassian.jira.plugin.... ]
Sibin Karnavar commented on JGRP-2256:
--------------------------------------
Just to add on top of this.
This cluster is working good and i dont see another issues. But just noticed the above error in the log. I dont see any issues with it. That is the reason I have opened this as MINOR.
> Connection.Receiver - Failed handling incoming message
> ------------------------------------------------------
>
> Key: JGRP-2256
> URL: https://issues.jboss.org/browse/JGRP-2256
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.10
> Reporter: Sibin Karnavar
> Assignee: Bela Ban
> Priority: Minor
>
> In AWS environment,
> I have not defined the port {color:red}41493{color} . I have configured TCP bind_port as 7803.
> But I can see from the below stack-trace that,
> Connection.Receiver [10.91.133.210:7803 - 10.91.135.64:{color:red}41493{color}]
> 1) Do I need to open/configure any other port ? I am wondering How 41493 is used when i have configured my bind_port as 7803.
> 2) What is the significance of client_bind_port for TCP. What happens if I dont configure it?
> 2018-03-05 19:07:28.833 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
> 2018-03-05 19:07:29.834 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 1
> 2018-03-05 19:07:32.842 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
> 2018-03-05 19:07:32.889 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 2
> 2018-03-05 19:07:35.944 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 3
> 2018-03-05 19:07:36.848 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
> 2018-03-05 19:07:38.999 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 4
> 2018-03-05 19:07:40.854 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
> 2018-03-05 19:07:42.053 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 5
> 2018-03-05 19:07:44.860 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
> 2018-03-05 19:07:45.108 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 6
> 2018-03-05 19:07:48.163 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 7
> 2018-03-05 19:07:48.866 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
> 2018-03-05 19:07:51.218 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 8
> 2018-03-05 19:07:51.218 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: too many JOIN attempts (8): becoming singleton
> 2018-03-05 19:07:52.041 ERROR 23012 --- [Connection.Receiver [10.91.133.210:7803 - 10.91.135.64:41493]-12,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000030: ip-10-91-133-210-46045: failed handling incoming message
> java.io.IOException: Stream closed
> at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:170)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:269)
> at java.io.DataInputStream.readByte(DataInputStream.java:265)
> at org.jgroups.Message.readFrom(Message.java:724)
> at org.jgroups.util.Util.readMessageBatch(Util.java:1193)
> at org.jgroups.protocols.TP.handleMessageBatch(TP.java:1329)
> at org.jgroups.protocols.TP.receive(TP.java:1321)
> at org.jgroups.blocks.cs.BaseServer.receive(BaseServer.java:171)
> at org.jgroups.blocks.cs.TcpConnection$Receiver.run(TcpConnection.java:290)
> at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JGRP-2256) Connection.Receiver - Failed handling incoming message
by Sibin Karnavar (JIRA)
[ https://issues.jboss.org/browse/JGRP-2256?page=com.atlassian.jira.plugin.... ]
Sibin Karnavar edited comment on JGRP-2256 at 3/5/18 3:09 PM:
--------------------------------------------------------------
Just to add on top of this.
This cluster is working good and i dont see any another issues. But just noticed the above error in the log. That is the reason I have opened this as MINOR.
was (Author: sibin.karnavar):
Just to add on top of this.
This cluster is working good and i dont see another issues. But just noticed the above error in the log. I dont see any issues with it. That is the reason I have opened this as MINOR.
> Connection.Receiver - Failed handling incoming message
> ------------------------------------------------------
>
> Key: JGRP-2256
> URL: https://issues.jboss.org/browse/JGRP-2256
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.10
> Reporter: Sibin Karnavar
> Assignee: Bela Ban
> Priority: Minor
>
> In AWS environment,
> I have not defined the port {color:red}41493{color} . I have configured TCP bind_port as 7803.
> But I can see from the below stack-trace that,
> Connection.Receiver [10.91.133.210:7803 - 10.91.135.64:{color:red}41493{color}]
> 1) Do I need to open/configure any other port ? I am wondering How 41493 is used when i have configured my bind_port as 7803.
> 2) What is the significance of client_bind_port for TCP. What happens if I dont configure it?
> 2018-03-05 19:07:28.833 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
> 2018-03-05 19:07:29.834 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 1
> 2018-03-05 19:07:32.842 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
> 2018-03-05 19:07:32.889 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 2
> 2018-03-05 19:07:35.944 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 3
> 2018-03-05 19:07:36.848 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
> 2018-03-05 19:07:38.999 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 4
> 2018-03-05 19:07:40.854 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
> 2018-03-05 19:07:42.053 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 5
> 2018-03-05 19:07:44.860 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
> 2018-03-05 19:07:45.108 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 6
> 2018-03-05 19:07:48.163 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 7
> 2018-03-05 19:07:48.866 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
> 2018-03-05 19:07:51.218 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 8
> 2018-03-05 19:07:51.218 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: too many JOIN attempts (8): becoming singleton
> 2018-03-05 19:07:52.041 ERROR 23012 --- [Connection.Receiver [10.91.133.210:7803 - 10.91.135.64:41493]-12,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000030: ip-10-91-133-210-46045: failed handling incoming message
> java.io.IOException: Stream closed
> at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:170)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:269)
> at java.io.DataInputStream.readByte(DataInputStream.java:265)
> at org.jgroups.Message.readFrom(Message.java:724)
> at org.jgroups.util.Util.readMessageBatch(Util.java:1193)
> at org.jgroups.protocols.TP.handleMessageBatch(TP.java:1329)
> at org.jgroups.protocols.TP.receive(TP.java:1321)
> at org.jgroups.blocks.cs.BaseServer.receive(BaseServer.java:171)
> at org.jgroups.blocks.cs.TcpConnection$Receiver.run(TcpConnection.java:290)
> at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JGRP-2256) Connection.Receiver - Failed handling incoming message
by Sibin Karnavar (JIRA)
[ https://issues.jboss.org/browse/JGRP-2256?page=com.atlassian.jira.plugin.... ]
Sibin Karnavar commented on JGRP-2256:
--------------------------------------
I have not configured port_range but I can see that the default value for port range is 50. {color:red}41493{color} , not sure if port_range has anything to do with this port?
> Connection.Receiver - Failed handling incoming message
> ------------------------------------------------------
>
> Key: JGRP-2256
> URL: https://issues.jboss.org/browse/JGRP-2256
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.10
> Reporter: Sibin Karnavar
> Assignee: Bela Ban
> Priority: Minor
>
> In AWS environment,
> I have not defined the port {color:red}41493{color} . I have configured TCP bind_port as 7803.
> But I can see from the below stack-trace that,
> Connection.Receiver [10.91.133.210:7803 - 10.91.135.64:{color:red}41493{color}]
> 1) Do I need to open/configure any other port ? I am wondering How 41493 is used when i have configured my bind_port as 7803.
> 2) What is the significance of client_bind_port for TCP. What happens if I dont configure it?
> 2018-03-05 19:07:28.833 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
> 2018-03-05 19:07:29.834 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 1
> 2018-03-05 19:07:32.842 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
> 2018-03-05 19:07:32.889 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 2
> 2018-03-05 19:07:35.944 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 3
> 2018-03-05 19:07:36.848 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
> 2018-03-05 19:07:38.999 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 4
> 2018-03-05 19:07:40.854 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
> 2018-03-05 19:07:42.053 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 5
> 2018-03-05 19:07:44.860 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
> 2018-03-05 19:07:45.108 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 6
> 2018-03-05 19:07:48.163 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 7
> 2018-03-05 19:07:48.866 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
> 2018-03-05 19:07:51.218 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 8
> 2018-03-05 19:07:51.218 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: too many JOIN attempts (8): becoming singleton
> 2018-03-05 19:07:52.041 ERROR 23012 --- [Connection.Receiver [10.91.133.210:7803 - 10.91.135.64:41493]-12,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000030: ip-10-91-133-210-46045: failed handling incoming message
> java.io.IOException: Stream closed
> at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:170)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:269)
> at java.io.DataInputStream.readByte(DataInputStream.java:265)
> at org.jgroups.Message.readFrom(Message.java:724)
> at org.jgroups.util.Util.readMessageBatch(Util.java:1193)
> at org.jgroups.protocols.TP.handleMessageBatch(TP.java:1329)
> at org.jgroups.protocols.TP.receive(TP.java:1321)
> at org.jgroups.blocks.cs.BaseServer.receive(BaseServer.java:171)
> at org.jgroups.blocks.cs.TcpConnection$Receiver.run(TcpConnection.java:290)
> at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JGRP-2256) Connection.Receiver - Failed handling incoming message
by Sibin Karnavar (JIRA)
Sibin Karnavar created JGRP-2256:
------------------------------------
Summary: Connection.Receiver - Failed handling incoming message
Key: JGRP-2256
URL: https://issues.jboss.org/browse/JGRP-2256
Project: JGroups
Issue Type: Bug
Affects Versions: 4.0.10
Reporter: Sibin Karnavar
Assignee: Bela Ban
Priority: Minor
In AWS environment,
I have not defined the port {color:red}41493{color} . I have configured TCP bind_port as 7803.
But I can see from the below stack-trace that,
Connection.Receiver [10.91.133.210:7803 - 10.91.135.64:{color:red}41493{color}]
1) Do I need to open/configure any other port ? I am wondering How 41493 is used when i have configured my bind_port as 7803.
2) What is the significance of client_bind_port for TCP. What happens if I dont configure it?
2018-03-05 19:07:28.833 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
2018-03-05 19:07:29.834 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 1
2018-03-05 19:07:32.842 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
2018-03-05 19:07:32.889 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 2
2018-03-05 19:07:35.944 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 3
2018-03-05 19:07:36.848 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
2018-03-05 19:07:38.999 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 4
2018-03-05 19:07:40.854 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
2018-03-05 19:07:42.053 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 5
2018-03-05 19:07:44.860 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
2018-03-05 19:07:45.108 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 6
2018-03-05 19:07:48.163 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 7
2018-03-05 19:07:48.866 ERROR 23012 --- [TQ-Bundler-9,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000034: ip-10-91-133-210-46045: failure sending message to ip-10-91-135-64-18021: java.net.SocketTimeoutException: connect timed out
2018-03-05 19:07:51.218 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: JOIN(ip-10-91-133-210-46045) sent to ip-10-91-135-64-18021 timed out (after 3000 ms), on try 8
2018-03-05 19:07:51.218 WARN 23012 --- [localhost-startStop-1] org.jgroups.protocols.pbcast.GMS : - - ip-10-91-133-210-46045: too many JOIN attempts (8): becoming singleton
2018-03-05 19:07:52.041 ERROR 23012 --- [Connection.Receiver [10.91.133.210:7803 - 10.91.135.64:41493]-12,ABC-SKS-stage_SJX_040320181613_XSJ,ip-10-91-133-210-46045] org.jgroups.protocols.TCP : - - JGRP000030: ip-10-91-133-210-46045: failed handling incoming message
java.io.IOException: Stream closed
at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:170)
at java.io.BufferedInputStream.read(BufferedInputStream.java:269)
at java.io.DataInputStream.readByte(DataInputStream.java:265)
at org.jgroups.Message.readFrom(Message.java:724)
at org.jgroups.util.Util.readMessageBatch(Util.java:1193)
at org.jgroups.protocols.TP.handleMessageBatch(TP.java:1329)
at org.jgroups.protocols.TP.receive(TP.java:1321)
at org.jgroups.blocks.cs.BaseServer.receive(BaseServer.java:171)
at org.jgroups.blocks.cs.TcpConnection$Receiver.run(TcpConnection.java:290)
at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JGRP-2253) FD_SOCK is not working in AWS environment
by Sibin Karnavar (JIRA)
[ https://issues.jboss.org/browse/JGRP-2253?page=com.atlassian.jira.plugin.... ]
Sibin Karnavar commented on JGRP-2253:
--------------------------------------
I have a quick question. I can open an another JIRA id required.
What is port_range configuration for TCP? In AWS environment, Can I define it as 0?
Also
What is diagnostics_port? Do I need to really configure that port in AWS as part of my security group open ports?
Thanks,
Sibin
> FD_SOCK is not working in AWS environment
> -----------------------------------------
>
> Key: JGRP-2253
> URL: https://issues.jboss.org/browse/JGRP-2253
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.10
> Environment: AWS - EC2
> Reporter: Sibin Karnavar
> Assignee: Bela Ban
>
> We have our failure detection defined like below.
> <FD_SOCK external_port="7804" />
> <FD timeout="3000" max_tries="3" />
> <VERIFY_SUSPECT timeout="3000" />
> Please note that we have used FD instead of FD_ALL in AWS. We will be changing it to FD_ALL later after detailed testing.
> In my local, this is working perfect. As soon as I kill my node, I was able to see that view change was happening immediately with FD_SOCK.
> We were not mentioning the external_port in the FD_SOCK but later I thought it may be an issue with the port and defined it as 7804 and added the same port to the security group that allows to access this port among all the nodes. So no issue with the port.
> Can you please let us know if we need any additional configurations to make FD_SOCK works well in AWS.
> Thanks,
> Sibin
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months