Yes, please group this with JBAS-4963, either as a subtask or as a separate issue that JBAS-4963 depends on. In general, this pooled code looks hacky. PooledInvokerProxy catching any exception and throwing it as a java.rmi.ConnectException? Basically that seems like a manifestation of a decision to not create a full separate set of classes for the Pooled invokers vs. JRMP, so you end up w/ pooled pretending to be JRMP. I'm concerned about your fix, because it extends that problem, by introducing a workaround for the pooled case into a class that's also meant to support JRMP. Looking at JRMPInvokerProxyHA, it's probably OK, but I'd like your thoughts on that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175342#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...