[JBoss JIRA] Created: (JGRP-1144) AUTH: X.509 issue with keystore
by Bela Ban (JIRA)
AUTH: X.509 issue with keystore
-------------------------------
Key: JGRP-1144
URL: https://jira.jboss.org/jira/browse/JGRP-1144
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 2.10
Draw with JGroups/conf/auth_x509.xml doesn't work:
[linux]/home/bela$ draw -props JGroups/conf/auth_X509.xml
fatal error: unable to setup the protocol stack, cause:
java.io.IOException: Invalid keystore format
at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:633)
at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:38)
at java.security.KeyStore.load(KeyStore.java:1185)
at org.jgroups.auth.X509Token.setCertificate(X509Token.java:177)
at org.jgroups.protocols.AUTH.init(AUTH.java:58)
at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:647)
at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:457)
at org.jgroups.JChannel.init(JChannel.java:1702)
at org.jgroups.JChannel.<init>(JChannel.java:243)
at org.jgroups.JChannel.<init>(JChannel.java:226)
at org.jgroups.demos.Draw.<init>(Draw.java:56)
at org.jgroups.demos.Draw.main(Draw.java:154)
Perhaps this is caused by our changes in the Bouncycastle JAR ?
--
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
15 years, 7 months
[JBoss JIRA] Created: (JGRP-1155) Socket Exceptions on Coordinator after adding start_port in FD_SOCK
by Ken Michie (JIRA)
Socket Exceptions on Coordinator after adding start_port in FD_SOCK
-------------------------------------------------------------------
Key: JGRP-1155
URL: https://jira.jboss.org/jira/browse/JGRP-1155
Project: JGroups
Issue Type: Bug
Affects Versions: 2.6.13, 2.6.10
Environment: RHEL 5.2.
135.9.147.170 is coordinator, 135.9.147.158 is other member
Connection is over TCP
Jgroup Channel is over port 7802
FD_SOCK is over port 7803
iptables is running, which is why I need to specify a port; the random port selection gets blocked otherwise
Reporter: Ken Michie
Assignee: Bela Ban
I was able to reproduce it with Draw program on both 2.6.10.GA and 2.6.13.GA. Here is my command:
java -cp .:log4j.properties:log4j.jar:jgroups-all.jar:commons-logging.jar org.jgroups.demos.Draw -props kenTcp.xml
log4j.properties was on WARN and above for org.jgroups.
I would tail the jgroups.log file and ONLY on the coordinator I would eventually see these messages printing every so often:
2010-02-16 15:49:43,144 [ConnectionTable.Connection.Sender local_addr=135.9.147.170:7802 [135.9.147.170:50167 - 135.9.147.158:7803],DrawGroupDemo,135.9.147.170:7802] ERROR org.jgroups.blocks.ConnectionTable - failed sending data to 135.9.147.158:7803: java.net.SocketException: Broken pipe
2010-02-16 15:49:43,144 [ConnectionTable.Connection.Sender local_addr=135.9.147.170:7802 [135.9.147.170:50167 - 135.9.147.158:7803],DrawGroupDemo,135.9.147.170:7802] ERROR org.jgroups.blocks.ConnectionTable - failed sending data to 135.9.147.158:7803: java.net.SocketException: Broken pipe
2010-02-16 15:50:07,624 [ConnectionTable.Connection.Sender local_addr=135.9.147.170:7802 [135.9.147.170:38803 - 135.9.147.158:7803],DrawGroupDemo,135.9.147.170:7802] ERROR org.jgroups.blocks.ConnectionTable - failed sending data to 135.9.147.158:7803: java.net.SocketException: Socket closed
2010-02-16 15:50:07,624 [ConnectionTable.Connection.Sender local_addr=135.9.147.170:7802 [135.9.147.170:38803 - 135.9.147.158:7803],DrawGroupDemo,135.9.147.170:7802] ERROR org.jgroups.blocks.ConnectionTable - failed sending data to 135.9.147.158:7803: java.net.SocketException: Socket closed
2010-02-16 15:50:33,608 [ConnectionTable.Connection.Sender local_addr=135.9.147.170:7802 [135.9.147.170:44940 - 135.9.147.158:7803],DrawGroupDemo,135.9.147.170:7802] ERROR org.jgroups.blocks.ConnectionTable - failed sending data to 135.9.147.158:7803: java.net.SocketException: Socket closed
2010-02-16 15:50:33,608 [ConnectionTable.Connection.Sender local_addr=135.9.147.170:7802 [135.9.147.170:44940 - 135.9.147.158:7803],DrawGroupDemo,135.9.147.170:7802] ERROR org.jgroups.blocks.ConnectionTable - failed sending data to 135.9.147.158:7803: java.net.SocketException: Socket closed
2010-02-16 15:50:33,611 [ConnectionTable.Connection.Sender local_addr=135.9.147.170:7802 [135.9.147.170:55279 - 135.9.147.158:7803],DrawGroupDemo,135.9.147.170:7802] ERROR org.jgroups.blocks.ConnectionTable - failed sending data to 135.9.147.158:7803: java.net.SocketException: Broken pipe
2010-02-16 15:50:33,611 [ConnectionTable.Connection.Sender local_addr=135.9.147.170:7802 [135.9.147.170:55279 - 135.9.147.158:7803],DrawGroupDemo,135.9.147.170:7802] ERROR org.jgroups.blocks.ConnectionTable - failed sending data to 135.9.147.158:7803: java.net.SocketException: Broken pipe
2010-02-16 15:50:35,115 [ConnectionTable.Connection.Sender local_addr=135.9.147.170:7802 [135.9.147.170:42406 - 135.9.147.158:7803],DrawGroupDemo,135.9.147.170:7802] ERROR org.jgroups.blocks.ConnectionTable - failed sending data to 135.9.147.158:7803: java.net.SocketException: Broken pipe
2010-02-16 15:50:35,115 [ConnectionTable.Connection.Sender local_addr=135.9.147.170:7802 [135.9.147.170:42406 - 135.9.147.158:7803],DrawGroupDemo,135.9.147.170:7802] ERROR org.jgroups.blocks.ConnectionTable - failed sending data to 135.9.147.158:7803: java.net.SocketException: Broken pipe
You can see it is trying to use some different ephemeral port each time, but from "netstat -an | grep 780" (FD_SOCK is on 7803, and channel is on 7802), you can see it is using the wrong socket, where 158 is the other client:
tcp 0 0 ::ffff:135.9.147.170:7802 :::* LISTEN
tcp 0 0 ::ffff:135.9.147.170:7803 :::* LISTEN
tcp 0 0 ::ffff:135.9.147.170:7803 ::ffff:135.9.147.158:41549 ESTABLISHED
tcp 0 0 ::ffff:135.9.147.170:57478 ::ffff:135.9.147.158:7802 ESTABLISHED
tcp 0 0 ::ffff:135.9.147.170:46929 ::ffff:135.9.147.158:7803 ESTABLISHED
Protocol stack in XML (the TCPPING initial_hosts value is of the other member for the other JGroups member):
<config>
<TCP start_port="7802"
loopback="false"
recv_buf_size="20000000"
send_buf_size="640000"
discard_incompatible_packets="false"
max_bundle_size="128000"
max_bundle_timeout="100"
use_incoming_packet_handler="true"
enable_bundling="true"
use_send_queues="true"
sock_conn_timeout="300"
skip_suspected_members="true"
use_concurrent_stack="true"
thread_pool.enabled="true"
thread_pool.min_threads="2"
thread_pool.max_threads="10"
thread_pool.keep_alive_time="5000"
thread_pool.queue_enabled="false"
thread_pool.queue_max_size="1000"
thread_pool.rejection_policy="run"
oob_thread_pool.enabled="true"
oob_thread_pool.min_threads="2"
oob_thread_pool.max_threads="10"
oob_thread_pool.keep_alive_time="5000"
oob_thread_pool.queue_enabled="false"
oob_thread_pool.queue_max_size="1000"
oob_thread_pool.rejection_policy="run"/>
<TCPPING timeout="3000"
initial_hosts="135.9.147.170[7800]}"
port_range="4"/>
<MERGE2 max_interval="100000"
min_interval="20000"/>
<FD_SOCK start_port="7803"/>
<FD timeout="10000" max_tries="5" shun="true"/>
<VERIFY_SUSPECT timeout="1500" />
<BARRIER />
<pbcast.NAKACK
use_mcast_xmit="false" gc_lag="0"
retransmit_timeout="300,600,1200,2400,4800"
discard_delivered_msgs="true"/>
<UNICAST timeout="300,600,1200" />
<pbcast.STABLE stability_delay="1000" desired_avg_gossip="50000"
max_bytes="400000"/>
<VIEW_SYNC avg_send_interval="60000"/>
<pbcast.GMS print_local_addr="true" join_timeout="3000"
shun="true"
view_bundling="true"/>
<FC max_credits="2000000"
min_threshold="0.10"/>
<FRAG2 frag_size="60000" />
<pbcast.STREAMING_STATE_TRANSFER/>
<!-- <pbcast.STATE_TRANSFER/> -->
</config>
--
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
15 years, 7 months
[JBoss JIRA] Created: (JGRP-1183) TCPPING fails to discover initial members if port-range is greater than 8
by Karthik Abram (JIRA)
TCPPING fails to discover initial members if port-range is greater than 8
-------------------------------------------------------------------------
Key: JGRP-1183
URL: https://jira.jboss.org/jira/browse/JGRP-1183
Project: JGroups
Issue Type: Bug
Affects Versions: 2.8
Reporter: Karthik Abram
Assignee: Bela Ban
I also tested this with 2.10.0.ALPHA4
I have TCPPING configured this way:
<TCPPING timeout="3000"
initial_hosts="localhost[11000],localhost[12000]"
port_range="3"
num_initial_members="1"/>
I notice that if I start up a process on port 11000 and then a second process that binds to 11001, if the port-range is set to 3 (it seems any port-range less than 8) the processes successfully find each other. When I set the port-range to 9 or higher, I see GET_MBRS_RSP responses from the processes with each other's information but nothing is discovered. I suspect some issue with threading/race-condition. Here is the trace log for TCPPING with port-range = 50:
2010-04-02 09:34:50,219 TRACE TCPPING - - received GET_MBRS_REQ from windowbox-64914, sending response [PING: type=GET_MBRS_RSP, arg=own_addr=windowbox-64914, view id=[windowbox-32305|0], is_server=true, is_coord=false, logical_name=windowbox-64914, physical_addrs=0.0.0.0:11001]
2010-04-02 09:34:52,222 TRACE TCPPING - - received GET_MBRS_REQ from windowbox-64914, sending response [PING: type=GET_MBRS_RSP, arg=own_addr=windowbox-32305, view id=[windowbox-32305|0], is_server=true, is_coord=true, logical_name=windowbox-32305, physical_addrs=0.0.0.0:11000]
2010-04-02 09:34:54,724 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11010
2010-04-02 09:34:54,724 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11011
2010-04-02 09:34:54,724 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11008
2010-04-02 09:34:54,724 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11009
2010-04-02 09:34:54,724 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11006
2010-04-02 09:34:54,724 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11007
2010-04-02 09:34:54,724 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11004
2010-04-02 09:34:54,724 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11005
2010-04-02 09:34:54,724 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11002
2010-04-02 09:34:54,724 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11003
2010-04-02 09:34:54,724 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11000
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11001
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11027
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11026
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11025
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11024
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11023
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11022
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11021
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11020
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11019
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11018
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11017
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11016
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11015
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11014
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11013
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11012
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12043
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12042
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12041
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11048
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12040
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11049
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12039
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11046
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12038
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11047
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12037
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11044
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12036
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11045
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12049
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12048
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12047
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12046
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12045
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12044
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12026
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11035
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12027
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11034
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12024
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11033
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12025
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11032
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12022
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11031
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12023
2010-04-02 09:34:54,727 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11030
2010-04-02 09:34:54,729 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12020
2010-04-02 09:34:54,729 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11029
2010-04-02 09:34:54,729 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12021
2010-04-02 09:34:54,729 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11028
2010-04-02 09:34:54,729 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12034
2010-04-02 09:34:54,729 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11043
2010-04-02 09:34:54,729 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12035
2010-04-02 09:34:54,729 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11042
2010-04-02 09:34:54,729 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12032
2010-04-02 09:34:54,729 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11041
2010-04-02 09:34:54,729 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12033
2010-04-02 09:34:54,729 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11040
2010-04-02 09:34:54,729 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12030
2010-04-02 09:34:54,729 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11039
2010-04-02 09:34:54,729 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12031
2010-04-02 09:34:54,729 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11038
2010-04-02 09:34:54,729 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12028
2010-04-02 09:34:54,729 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11037
2010-04-02 09:34:54,729 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12029
2010-04-02 09:34:54,729 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:11036
2010-04-02 09:34:54,729 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12009
2010-04-02 09:34:54,730 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12008
2010-04-02 09:34:54,730 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12011
2010-04-02 09:34:54,730 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12010
2010-04-02 09:34:54,730 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12005
2010-04-02 09:34:54,730 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12004
2010-04-02 09:34:54,730 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12007
2010-04-02 09:34:54,730 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12006
2010-04-02 09:34:54,730 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12017
2010-04-02 09:34:54,730 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12016
2010-04-02 09:34:54,730 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12019
2010-04-02 09:34:54,730 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12018
2010-04-02 09:34:54,730 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12013
2010-04-02 09:34:54,730 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12012
2010-04-02 09:34:54,730 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12015
2010-04-02 09:34:54,730 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12014
2010-04-02 09:34:54,730 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12000
2010-04-02 09:34:54,730 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12001
2010-04-02 09:34:54,730 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12002
2010-04-02 09:34:54,730 TRACE TCPPING - - [FIND_INITIAL_MBRS] sending PING request to 10.3.10.236:12003
2010-04-02 09:34:56,236 TRACE TCPPING - - discovery took 3003 ms: responses: 0 total (0 servers (0 coord), 0 clients)
2010-04-02 09:34:59,728 TRACE TCPPING - - received GET_MBRS_REQ from windowbox-32305, sending response [PING: type=GET_MBRS_RSP, arg=own_addr=windowbox-32305, view id=[windowbox-32305|0], is_server=true, is_coord=true, logical_name=windowbox-32305]
2010-04-02 09:34:59,728 TRACE TCPPING - - received GET_MBRS_RSP from windowbox-32305: own_addr=windowbox-32305, view id=[windowbox-32305|0], is_server=true, is_coord=true, logical_name=windowbox-32305
--
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
15 years, 7 months
[JBoss JIRA] Created: (JGRP-1161) Repeated ERROR logging from MPING PingSenderTask on Solaris
by Brian Stansberry (JIRA)
Repeated ERROR logging from MPING PingSenderTask on Solaris
-----------------------------------------------------------
Key: JGRP-1161
URL: https://jira.jboss.org/jira/browse/JGRP-1161
Project: JGroups
Issue Type: Bug
Affects Versions: 2.6.10
Environment: Solaris server (not sure what release), JBoss 5.1.0.GA
Reporter: Brian Stansberry
Assignee: Bela Ban
AS 5.1.0.GA user (see forum thread) reports repeated logging of java.io.InterruptedIOException from MPING, coming from the task thread that's running Discovery$PingSenderTask. The thread is interrupted during the send of the discovery packet. From the pattern of logging (repeated, and after initial cluster formation) my assumption is the task is triggered by MERGE2. My assumption is also that the thread is interrupted because Discovery.findInitialMembers() has timed out waiting for a response, and has called PingSenderTask.stop(), which ultimately interrupts the task thread. The MPING discovery timeout is 2 secs; the unusual thing here is the discovery packet hasn't been sent w/ in 2 seconds.
There are really two aspects to this JIRA:
1) See if there is any problem with the way JGroups is scheduling the task, or configuring the multicast socket etc. It looks OK to me, and quite possibly this is due to an environmental issue on the user's system. Would be good to understand though, as this is the second report I've had of this general problem.
2) Change MPING.sendMcastDiscoveryRequest to handle InterruptedIOException or let it propagate. I see PingSenderTask.run() is coded to handle InterruptedIOException by logging a WARN, but MPING.sendMcastDiscoveryRequest doesn't let it propagate and instead logs it as an ERROR with a stack trace.
--
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
15 years, 7 months
[JBoss JIRA] Created: (JASSIST-42) Proxy serialization looses inner data objects
by Damien Lecan (JIRA)
Proxy serialization looses inner data objects
---------------------------------------------
Key: JASSIST-42
URL: http://jira.jboss.com/jira/browse/JASSIST-42
Project: Javassist
Issue Type: Bug
Reporter: Damien Lecan
Assigned To: Shigeru Chiba
Priority: Blocker
I working with proxies build with ProxyFactory method.
When I want to serialize/deserialize it, everything seems to be ok except that only proxy instance is serialized, not inner objects.
Eg.
Object "A" contains an instance of "B"
After serialization/deserialization of a proxy of A, instance of "B" in "A" is null
When I look at this code :
public static SerializedProxy makeSerializedProxy(Object proxy)
throws java.io.InvalidClassException
{
Class clazz = proxy.getClass();
return new SerializedProxy(clazz, ProxyFactory.getFilter(clazz),
ProxyFactory.getHandler(clazz));
}
I don't understand how serialization can keep inner objects ...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 7 months
