Hi Ron, A few questions 1) Is the default destruction delay being maintained programatically within Remoting? I don't see this delay being added within the EJB3 remoting configurations 2) From what i understand in those threads, the issue was a socket being created on every method invocation on a remote EJB3 proxy. The destruction delay tries to fix this by delaying the destruction of the socket (and the subsequent creation of a new one). Did i understand this right? anonymous wrote : I've been informally suggesting 5 seconds as a reasonable default delay, but I'm wondering if anyone from the EJB3 team has any better intuition. Assuming, i understood the issue correctly, i guess the ideal timeout really depends on how the end users use the EJB3 proxies. Some users might have this: someClientMethod() | { | // lookup remote bean | Bean bean = ctx.lookup(...); | // invoke method | bean.doSomething(); // creates a socket | | // do something that takes a really long time | waitForUserInputOrSomeOtherTimeConsumingOperation(); | | // use the earlier proxy again | bean.doSomeOtherThing(); // creates a socket (again) | } | | | Although if the proxy is being used for multiple method invocations within that default timeout then the performance improvement is going to be noticeable. 3) What is the (performance) impact of specifying a very long destruction delay? Does it degrade the performance or introduce any other issues? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4246373#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...