[ https://jira.jboss.org/jira/browse/JGRP-961?page=com.atlassian.jira.plugi... ] Richard Achmatowicz commented on JGRP-961: ------------------------------------------ A handful of tests are failing in this manner, but two cases which I have been looking at are RpcDispatcherAnycastTest and DisconnectTest. It seems the root cause of the problems is that when we have a situation where a server socket is created and clients are repeatedly connecting to the server socket, some connections cannot be established (even though the server socket is live). Either the Socket.connect() operation blocks indefinitely, or if a timeout is used, the timeout is exceeded and a SocketTimeoutException is raised. In RpcDispatcherAnycastTest, the server socket in question was that used by FD_SOCK to establish connections with neighbors after a view change had occurred. This delay also happened to reveal a deadlock in the FD_SOCK code between the <pinger_thread> thread recreating the link to the new neighbor, and the <main> thread trying to shutdown the pinger_thread.. In DisconnectTest, the socket in question was the GossipRouter server socket which received connections from clients for registering members, unregistering members, and getting lists of members. Tests were failing because clients could not connect. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JGRP-961?page=com.atlassian.jira.plugi... ] Richard Achmatowicz commented on JGRP-961: ------------------------------------------ I've written two small programs, ServerSocketSender and ServerSocketReceiver, which demonstrate the problem. These programs work fine on JDK 4,5,6 with IPv4 addresses: bind_addr = 192.168.0.100 port = 1234 Hello from client!(0) Hello from client!(1) Hello from client!(2) Hello from client!(3) Hello from client!(4) Hello from client!(5) Hello from client!(6) Hello from client!(7) Hello from client!(8) Hello from client!(9) bind_addr = 192.168.0.100 port = 1234 sock_read_timeout = 0 sock_conn_timeout = 5 Connected to host: /192.168.0.100, port: 1234 Hello from client!(0)(bounced by server) Connected to host: /192.168.0.100, port: 1234 Hello from client!(1)(bounced by server) Connected to host: /192.168.0.100, port: 1234 Hello from client!(2)(bounced by server) Connected to host: /192.168.0.100, port: 1234 Hello from client!(3)(bounced by server) Connected to host: /192.168.0.100, port: 1234 Hello from client!(4)(bounced by server) Connected to host: /192.168.0.100, port: 1234 Hello from client!(5)(bounced by server) Connected to host: /192.168.0.100, port: 1234 Hello from client!(6)(bounced by server) Connected to host: /192.168.0.100, port: 1234 Hello from client!(7)(bounced by server) Connected to host: /192.168.0.100, port: 1234 Hello from client!(8)(bounced by server) Connected to host: /192.168.0.100, port: 1234 Hello from client!(9)(bounced by server) The same programs do not work with JDK 4 and 5 (but dow work with JDK 6): bind_addr = fe80::215:58ff:fec8:81a8 port = 1234 Hello from client!(0) bind_addr = fe80::215:58ff:fec8:81a8 port = 1234 sock_read_timeout = 0 sock_conn_timeout = 5 Connected to host: /fe80:0:0:0:215:58ff:fec8:81a8, port: 1234 Hello from client!(0)(bounced by server) exception connecting to host: /fe80:0:0:0:215:58ff:fec8:81a8, port: 1234java.net.SocketTimeoutException: connect timed out exception details = java.net.SocketTimeoutException: connect timed out exception connecting to host: /fe80:0:0:0:215:58ff:fec8:81a8, port: 1234java.net.SocketTimeoutException: connect timed out exception details = java.net.SocketTimeoutException: connect timed out exception connecting to host: /fe80:0:0:0:215:58ff:fec8:81a8, port: 1234java.net.SocketTimeoutException: connect timed out exception details = java.net.SocketTimeoutException: connect timed out exception connecting to host: /fe80:0:0:0:215:58ff:fec8:81a8, port: 1234java.net.SocketTimeoutException: connect timed out exception details = java.net.SocketTimeoutException: connect timed out exception connecting to host: /fe80:0:0:0:215:58ff:fec8:81a8, port: 1234java.net.SocketTimeoutException: connect timed out exception details = java.net.SocketTimeoutException: connect timed out exception connecting to host: /fe80:0:0:0:215:58ff:fec8:81a8, port: 1234java.net.SocketTimeoutException: connect timed out exception details = java.net.SocketTimeoutException: connect timed out exception connecting to host: /fe80:0:0:0:215:58ff:fec8:81a8, port: 1234java.net.SocketTimeoutException: connect timed out exception details = java.net.SocketTimeoutException: connect timed out exception connecting to host: /fe80:0:0:0:215:58ff:fec8:81a8, port: 1234java.net.SocketTimeoutException: connect timed out exception details = java.net.SocketTimeoutException: connect timed out exception connecting to host: /fe80:0:0:0:215:58ff:fec8:81a8, port: 1234java.net.SocketTimeoutException: connect timed out exception details = java.net.SocketTimeoutException: connect timed out -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JGRP-961?page=com.atlassian.jira.plugi... ] Richard Achmatowicz updated JGRP-961: ------------------------------------- Attachment: ServerSocketReceiver.java ServerSocketSender.java Sample programs to reproduce problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JGRP-961?page=com.atlassian.jira.plugi... ] Richard Achmatowicz commented on JGRP-961: ------------------------------------------ Running the sample program on Sun JDK 1.5.0 with wireshark turned on, it seems the problem is that: - the first TCP connection from the client to server attempt succeeds (initial handshake completes OK with SYN, SYN-ACK, ACK , followed by a PSH-ACK, ACK exchange from the client to the server, then a PSH-ACK, ACK exchange from the server, followed by a FIN-ACK, ACK exchange by both ends). - the second TCP connection attempt fails (the initial handshake to set up the connection fails with SYN, SYN-ACK, RST - for some reason, the client resets the connection upon receiving the SYN-ACK). - same for subsequent connections. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JGRP-961?page=com.atlassian.jira.plugi... ] Richard Achmatowicz commented on JGRP-961: ------------------------------------------ Udsing the scoped link-local address with ServerSocketReceiver and ServerSocketSender make the problem go away. Java is smart enough to understand the scoped IPv6 link-local address format and make iuse of the correct zone id. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira