Re: [javagroups-users] Socket closed

[Bela B. <be...@ya...>]

Your FD timeout is way too short. In combination with FD_SOCK, FD's 
timeout can be much higher (e.g. timeout="5000" max_tries="5"), so you 
have 25 seconds to detect a failure in case of a failure scenario that 
FD_SOCK doesn't immediately detect (e.g. a crashed switch).

Hmm, if this nevertheless does happen, you might have run into 
http://jira.jboss.com/jira/browse/JGRP-130, which is fixed in CVS head 
(2.6), but may not work well for automatic reconnects. I'll create a 
JIRA to investigate this in 2.6

Dima Gutzeit wrote:
> Here is my config :
>
> <config>
>         <TCP
>                 bind_addr="212.143.248.98"
>                 start_port="7900"
>          loopback="true"
>          recv_buf_size="20000000"
>          send_buf_size="640000"
>          discard_incompatible_packets="true"
>          max_bundle_size="64000"
>          max_bundle_timeout="30"
>          use_incoming_packet_handler="true"
>          enable_bundling="true"
>          use_send_queues="false"
>          sock_conn_timeout="300"
>          skip_suspected_members="true"
>
>          use_concurrent_stack="true"
>
>          thread_pool.enabled="true"
>          thread_pool.min_threads="1"
>          thread_pool.max_threads="25"
>          thread_pool.keep_alive_time="5000"
>          thread_pool.queue_enabled="false"
>          thread_pool.queue_max_size="100"
>          thread_pool.rejection_policy="Run"
>
>          oob_thread_pool.enabled="true"
>          oob_thread_pool.min_threads="1"
>          oob_thread_pool.max_threads="8"
>          oob_thread_pool.keep_alive_time="5000"
>          oob_thread_pool.queue_enabled="false"
>          oob_thread_pool.queue_max_size="100"
>          oob_thread_pool.rejection_policy="Run"/>
>         <MPING timeout="4000" bind_addr="212.143.248.98" 
> mcast_addr="228.8.8.9"
>         mcast_port="60666" ip_ttl="8" num_initial_members="2" 
> num_ping_requests="1" receive_on_all_interfaces="true"/>
>         <MERGE2 max_interval="10000" min_interval="5000"/>
>         <FD_SOCK/>
>         <FD timeout="1000" max_tries="2" shun="true"/>
>         <VERIFY_SUSPECT timeout="500"/>
>         <pbcast.NAKACK max_xmit_size="8192" use_mcast_xmit="false" 
> gc_lag="50" retransmit_timeout="600,1200,2400,4800" 
> discard_delivered_msgs="true"/>
>         <UNICAST timeout="1200,2400,3600"/>
>         <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" 
> join_retry_timeout="2000" shun="false"/>
>         <FC max_credits="2000000" min_threshold="0.10"/>
>         <FRAG2 frag_size="60000"/>
>         <pbcast.STATE_TRANSFER/>
> </config>
>
> I've added the method info in the logger and next time it happens I will 
> let you know.
>
> Thanks.
>
> Regards,
> Dima Gutzeit.
>
> Bela Ban wrote:
>   
>> Can you configure log4j such that the method is shown, so I can trace 
>> where this happens ?
>> log4j.appender.console.layout=org.apache.log4j.PatternLayout
>> log4j.appender.console.layout.ConversionPattern=%-7d{HH:mm:ss,SSS} [%p] 
>> [%t] %C{1}.%M(): %m%n
>>
>> I also need your config (make sure you have FD *and* FD_SOCK in there), 
>> and steps to reproduce this (if you can).
>>
>> Dima Gutzeit wrote:
>>   
>>     
>>> I am running a cluster based on TCP stack (2.5). My channels are 
>>> configured with AUTO_RECONNECT.
>>>  
>>> Once in a while I get the following in my logs and after that the 
>>> channel does not reconnect.
>>>  
>>> [ConnectionTable] ERROR 2007-08-08 23:30:42,352 exception is 
>>> java.net.SocketException: Socket closed
>>> [ConnectionTable] ERROR 2007-08-08 23:36:41,667 exception is 
>>> java.net.SocketException: Socket closed
>>> [ConnectionTable] ERROR 2007-08-09 12:49:51,685 exception is 
>>> java.net.SocketException: Socket closed
>>> [ConnectionTable] ERROR 2007-08-09 16:28:24,272 exception is 
>>> java.net.SocketException: Socket closed
>>> [ConnectionTable] ERROR 2007-08-09 18:12:12,584 exception is 
>>> java.net.SocketException: Socket closed
>>> [ConnectionTable] ERROR 2007-08-12 19:47:18,143 exception is 
>>> java.net.SocketException: Socket closed
>>> [ConnectionTable] ERROR 2007-08-14 16:51:21,200 exception is 
>>> java.net.SocketException: Socket closed
>>> [ConnectionTable] ERROR 2007-08-14 16:57:34,211 exception is 
>>> java.net.SocketException: Socket closed
>>> [ConnectionTable] ERROR 2007-08-21 12:36:47,130 exception is 
>>> java.net.SocketException: Socket closed
>>>  
>>> What am I doing wrong ?
>>>  
>>> Thanks in advance.
>>>  
>>> Regards,
>>> Dima Gutzeit.
>>> ------------------------------------------------------------------------
>>>
>>> -------------------------------------------------------------------------
>>> This SF.net email is sponsored by: Splunk Inc.
>>> Still grepping through log files to find problems?  Stop.
>>> Now Search log events and configuration files using AJAX and a browser.
>>> Download your FREE copy of Splunk now >>  http://get.splunk.com/
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> javagroups-users mailing list
>>> jav...@li...
>>> https://lists.sourceforge.net/lists/listinfo/javagroups-users
>>>   
>>>     
>>>       
>>   
>>     
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> javagroups-users mailing list
> jav...@li...
> https://lists.sourceforge.net/lists/listinfo/javagroups-users
>
>   

-- 
Bela Ban
Lead JGroups / Clustering Team
JBoss - a division of Red Hat