Java does allow setting the keep-alive parameter programatically on a socket.
It appears from the Javadocs, however, that this value is binary (set to 2
hours or nothing).
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4221062#4221062
Reply to the post :
So how do I check out 1.4.2 even pre-release? I can see the labeled and
released versions in SubVersion, but I can't see how to check out 1.4.2 (even
though it's in-progress ...).
What label / branch do I use to check out this version? And what is the
dependent remoting version?
View the
Ron,
Looks like someone else ran across the exact same bug (but thinks it will fix
the situation for all client parameters, not just the ping timeout. This was
posted to the JBM forums today.
http://www.jboss.com/index.html?module=bbop=viewtopicp=4193633#4193633
I may make this code change
Ron,
Attempting to follow the remoting / messaging code that is quite new to me, I
think I follow what you have said. However, attempting to backtrack through the
call chain to see where the URI is passed from server to client I quickly get
lost.
I think I have discovered the appropriate
Ron,
Yes it does appear these settings are propagated to the client as you
indicated.
2008-11-19 01:15:47,389 DEBUG [org.jboss.remoting.ServerInvoker]
SocketServerInvoker[Serenity.local:11457] started for locator InvokerLocator
Ron,
I can see this message on both sides of the connection:
2008-11-19 12:36:11,934 DEBUG [org.jboss.remoting.Client] starting callback
Connector: InvokerLocator
OK, here's a juicy tid-bit I missed:
12:58:33,275 DEBUG [ConnectionValidator] ConnectionValidator[null,
pingPeriod=2000 ms] created
12:58:33,275 TRACE [ConnectionValidator] config timeout: null
12:58:33,275 DEBUG [ConnectionValidator] ConnectionValidator[null,
pingPeriod=2000 ms] timeout: 1000
Ron,
Among all the debug entries I posted, I realized I was missing the one line you
asked for. Client side again:
13:11:58,759 DEBUG [Client] starting callback Connector: InvokerLocator
[bisocket://10.101.110.64:1878752913/callback
server-side locator entry:
2008-11-19 13:05:30,933 DEBUG [org.jboss.remoting.ServerInvoker]
SocketServerInvoker[serenity.solarworldusa.net:11457] started for locator
InvokerLocator [bisoc
The correct link appears to be:
http://www.jbossworld.com/2008/downloads/presentations/
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4190722#4190722
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4190722
I have put a nearly identical snippet of code in my
remoting-bisocket-service.xml file, but these values remain unused. I can
enable TRACE logging for the remoting and messaging packages, and see in the
output that the original (default) connection timeout values of 1000 and period
of 2000ms
Oh, one more tidbit. I did NOT change NumberOfCallRetries because a warning
at JBoss startup indicated that I should not, and that I had to put a
disableRemotingChecks entry in JBM somewhere, so I left that one item out. Do
I need the disableRemotingChecks to enable my other changes as well,
Shantanu
Did you ever find the cause of this? We are currently experiencing this very
phenomenon. I'm pretty much stuck after extensive research. I'd really
appreciate any solution you might have found. If I run across anything, I'll
let you know.
Thanks
Mark
View the original post :
Dan,
I'd be interested in what needed to be changed to pass in a defaults file. I
am working on embedding MySQL into JBoss as well, and I need to ensure it (and
JBoss) runs on a non-default port, to peacefully co-exist with another
potential MySQL installation. A defaults file is the only
14 matches
Mail list logo
