[JBoss-user] [JBossCache] - Re: ad infinitum: both corr and transport are null, cannot s

You were able to reproduce this, and fix it by doubling the FD timeout? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3902381#3902381 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3902381 -

[JBoss-user] [JBossCache] - Re: ad infinitum: both corr and transport are null, cannot s

This issue went away after I upgraded all of my servers to RHEL4 with Linux kernel 2.6.9, and we changed the access pattern a bit, removing one frequent deep tree graph access. Unfortunately there is no way to know what fixed the problem. View the original post : http://www.jboss.com/index.htm

[JBoss-user] [JBossCache] - Re: ad infinitum: both corr and transport are null, cannot s

Unfortunately the org.jgroups.blocks.GroupRequest:178 - both corr and transport are null, cannot send group request problem still bites our production systems after about a day. Are there any known good configurations we could go to which you could post here? View the original post : http://ww

[JBoss-user] [JBossCache] - Re: ad infinitum: both corr and transport are null, cannot s

Thank you for the advice. I did this and restarted. I will report back tomorrow on whether it fixed the problem. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3880861#3880861 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply

[JBoss-user] [JBossCache] - Re: ad infinitum: both corr and transport are null, cannot s

Yes, the problem still persists after changing the TCP1_4 transport to TCP. Any ideas? JBossCache is being used on top of Hibernate here. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3880818#3880818 Reply to the post : http://www.jboss.org/index.html?module

[JBoss-user] [JBossCache] - Re: ad infinitum: both corr and transport are null, cannot s

I changed TCP1_4 to TCP. The problem should manifest by the end of the day, again. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3880732#3880732 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3880732 -

[JBoss-user] [JBossCache] - Re: ad infinitum: both corr and transport are null, cannot s

TCP1_4 was described in some JBossCache document or discussion I read as a faster alternative to the TCP transport, this is why. This problem originally started manifesting when we were using the standard UDP multicast stack. View the original post : http://www.jboss.org/index.html?module=bb&op

[JBoss-user] [JBossCache] - ad infinitum: both corr and transport are null, cannot send

Hi, we have a problem with JBossCache cluster members leaving the cluster and never coming back. Anyone seen (and hopefully fixed) similar symptoms? Our protocol stack: The error log is as follows: 2005-05-25 17:59:48,842 ERROR org.jgroups.protocols.pbca