RE: [jboss-dev] Change to use pooled invoker as default invoker forJBossAS 4.2.0

-----Original Message----- From: jboss-development-bounces(a)lists.jboss.org [mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Tom Elrod Sent: Tuesday, November 28, 2006 5:14 AM To: JBoss.org development list Subject: Re: [jboss-dev] Change to use pooled invoker as default invoker forJBossAS 4.2.0 Guess Dimitris would the best person to answer that since he entered the issue, but think it came out of discussion with Andy Oliver and myself. Some of the points made where that it can handle server bounces better (which is no longer true with the retry interceptor logic Brian added) and that performance is better based on casual testing (however I think Clebert and Phillip found unified invoker with jboss serialization to be the fastest?). I personally don't know if is worth the change on the 4.x branch since already have change to unified invokers for jbossas 5. Scott M Stark wrote: > Depends on what the driving motivation for switching to the pooled > invoker is. > > Tom Elrod wrote: >> For JBossAS 4.2.0.CR1, pooled invoker needs to be set to be the >> default detached invoker (per >> http://jira.jboss.com/jira/browse/JBAS-3733). This is pretty straight >> forward as far as standardjboss.xml is concerned, but there are many >> other places the jrmp invoker is referenced such as the >> 'jboss:service=ClientUserTransaction' service, the jmx invoker adaptor, and sprinkled throughout the testsuite and other places. >> >> So is a blanket change to pooled invoker required or just for the >> standardjboss.xml? > > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development > _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development