"golubec" wrote : The problem is when application tries to talk by jacorb with host that isn't accessible - it takes a lot of time (probably ~ 20secs). So I've edited jacorb.properties file and changed number of retries to zero (It takes about 1 minute when retries was 5). But 20 secs is still not acceptible :(. | So I guess that i can't affect on this timeout by changing only jacorb.properies timeouts.
You certainly can change the timeouts for various client-side aspects, but I am not sure what you want to solve given your post above. Is the issue that you wish JacORB to figure out the server is not available in less than 20 seconds? Depending on your version of JBoss (and subsequently the version of JacORB), you may have the ability to set the following property, and it may be of some help to you. Which version of JBoss are you using? # Initial timeout for establishing a connection. | #jacorb.connection.client.connect_timeout=0 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3935854#3935854 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3935854 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
