------------------------------------------------------------------------ *From:* Jaroslaw Kijanowski *Sent:* Tue 2006-08-29 22:34 *To:* Clebert Suconic *Subject:* RE: [Fwd: Re: [JBoss-dev] jrmp invoker issue] I've found the needed invoker definition in testsuite\src\resources\test-configs\jrmp-invoker\conf So maybe it's not necessary to modify standardjboss.xml, but use somehow this in testsuite\src\resources\test-configs\jrmp-invoker\conf.. Just copying it into pooled.jar (this is deployed during the test which fails) doesn't work. ------------------------------------------------------------------------ *From:* Clebert Suconic *Sent:* Tue 2006-08-29 22:26 *To:* Tom Elrod *Cc:* Tom Elrod; QA Internal *Subject:* Re: [Fwd: Re: [JBoss-dev] jrmp invoker issue] The problem is, stadardjboss.xml on jboss-head doesn't have any of the legacy invokers defined, and Jaroslaw has some failures because of that. We need to understand if we are supposed to support JRMP and PooledInvokers on jboss-5 or not. If we are supposed, we would need to add these configurations back on standardjboss.xml, then we would have an additional invokers instead of replacing it. On Tue, 2006-08-29 at 22:52 -0400, Tom Elrod wrote: > Yes, but need to understand it better first. IIRC, only JBossAS 5 has > any config for UnifiedInvokers in the config files. They can be added > to JBossAS 4, but is a manual process. I guessed I missed something > here. Has this changed? > > I am not sure what the intersection with what Jaroslaw is saying is with > UnifiedInvoker. > > Clebert Suconic wrote: > > Tom, > > > > Can you please provide some comment on this (@ dev-list)? > > > > > > > > -------- Forwarded Message -------- > >> From: Clebert Suconic <clebert.suconic(a)jboss.com&gt; > >> Reply-To: clebert.suconic(a)jboss.com, JBoss.org development list > >> <jboss-development(a)lists.jboss.org&gt; > >> To: JBoss.org development list <jboss-development(a)lists.jboss.org&gt; > >> Subject: Re: [JBoss-dev] jrmp invoker issue > >> Date: Tue, 29 Aug 2006 15:28:34 -0500 > >> > >> It looks like we removed everything was not using UnifiedINvokers from > >> standard-jboss.xml while we still have legacy invokers defined on > >> jboss-service.xml. > >> > >> I know we want to have the setup taking control of this, but as we still > >> have a testsuite working on this, shouldn't we put these definitions > >> back on standardjboss.xml, or should we convert every test we have to > >> use UnifiedInvokers and treat everything else a legacy code an keep then > >> being tested in a separate testsuite? > >> > >> > >> Clebert > >> On Tue, 2006-08-29 at 12:41 -0500, Jaroslaw Kijanowski wrote: > >>> Hello, > >>> there's a test, org.jboss.test.pooled.test.BeanStressTestCase, which > >>> fails because StatelessSession isn't bound. The original > >>> testsuite/src/resources/pooled/META-INF/jboss.xml file looks like > >>> this: > >>> **************************** > >>> <jboss> > >>> <enterprise-beans> > >>> <session> > >>> <ejb-name>StatelessSession</ejb-name> > >>> <jndi-name>StatelessSession</jndi-name> > >>> <invoker-bindings> > >>> <invoker> > >>> > >>> <invoker-proxy-binding-name>stateless-pooled-invoker</invoker-proxy-binding-name> > >>> <jndi-name>PooledStatelessSession</jndi-name> > >>> </invoker> > >>> </invoker-bindings> > >>> </session> > >>> . > >>> . > >>> . > >>> <invoker-proxy-bindings> > >>> <invoker-proxy-binding> > >>> <name>stateless-pooled-invoker</name> > >>> > >>> <invoker-mbean>jboss:service=invoker,type=pooled</invoker-mbean> > >>> > >>> <proxy-factory>org.jboss.proxy.ejb.ProxyFactory</proxy-factory> > >>> <proxy-factory-config> > >>> <client-interceptors> > >>> <home> > >>> > >>> <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor> > >>> > >>> <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor> > >>> > >>> <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor> > >>> > >>> <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor> > >>> </home> > >>> <bean> > >>> > >>> <interceptor>org.jboss.proxy.ejb.StatelessSessionInterceptor</interceptor> > >>> > >>> <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor> > >>> > >>> <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor> > >>> > >>> <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor> > >>> </bean> > >>> </client-interceptors> > >>> </proxy-factory-config> > >>> </invoker-proxy-binding> > >>> **************************** > >>> But this isn't enough to bind StatelessSession (PooledStatelessSession > >>> is bound right). Exception is thrown. I looked in the 4_0_4 Branch on > >>> jboss.xml and I added these missing lines of code to jboss.xml: > >>> **************************************** > >>> <jboss> > >>> <enterprise-beans> > >>> <session> > >>> <ejb-name>StatelessSession</ejb-name> > >>> <jndi-name>StatelessSession</jndi-name> > >>> <invoker-bindings> > >>> <invoker> > >>> > >>> <invoker-proxy-binding-name>stateless-pooled-invoker</invoker-proxy-binding-name> > >>> <jndi-name>PooledStatelessSession</jndi-name> > >>> </invoker> > >>> > >>> <!-- copied from jboss.xml in JBAS 4_0_4 --> > >>> <invoker> > >>> > >>> <invoker-proxy-binding-name>stateless-rmi-invoker</invoker-proxy-binding-name> > >>> <jndi-name>StatelessSession</jndi-name> > >>> </invoker> > >>> <!-- end --> > >>> > >>> </invoker-bindings> > >>> </session> > >>> **************************************** > >>> > >>> But the test fails again, because I can't use "stateless-rmi-invoker", > >>> because it is no longer defined in > >>> server/src/etc/conf/default/standardjboss.xml in JBAS 5.0.0beta, why? > >>> I've copied the following section from JBAS4_0_4 to JBAS5 and now the > >>> test works fine. But is this the right way? > >>> **************************************** > >>> <invoker-proxy-binding> > >>> <name>stateless-rmi-invoker</name> > >>> <invoker-mbean>jboss:service=invoker,type=jrmp</invoker-mbean> > >>> <proxy-factory>org.jboss.proxy.ejb.ProxyFactory</proxy-factory> > >>> <proxy-factory-config> > >>> <client-interceptors> > >>> <home> > >>> > >>> <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor> > >>> > >>> <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor> > >>> > >>> <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor> > >>> <interceptor > >>> call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor> > >>> <interceptor > >>> call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor> > >>> </home> > >>> <bean> > >>> > >>> <interceptor>org.jboss.proxy.ejb.StatelessSessionInterceptor</interceptor> > >>> > >>> <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor> > >>> > >>> <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor> > >>> <interceptor > >>> call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor> > >>> <interceptor > >>> call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor> > >>> </bean> > >>> </client-interceptors> > >>> </proxy-factory-config> > >>> </invoker-proxy-binding> > >>> > >>> Thanks, > >>> Jaroslaw > >>> > >>> _______________________________________________ > >>> jboss-development mailing list > >>> jboss-development(a)lists.jboss.org > >>> https://lists.jboss.org/mailman/listinfo/jboss-development -- Clebert Suconic Core Developer ------------------------------------------------------------------------ _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

Is there a problem if we keep jrmp, unified and pooled on standardjboss.xml by default? When we have setup working on 5, setup will be able to define the appropriate invokers upon user's selection. On Wed, 2006-08-30 at 09:54 -0400, Tom Elrod wrote: > Sounds like I am just out of touch with what's going on with head > anymore, but the detached invokers (jrmp, pooled, or unified), can be > defined within any service xml. Traditionally, all the different > detached invokers were declared in the jboss-service.xml in the conf > directory (for jbossas 4 this was jrmp and pooled, for jbossas 5 was > unified, jrmp, and pooled). > > The standardjboss.xml in the conf directory would then specify which > declared detached invoker should be used for each ejb container (see > invoker-mean element within invoker-proxy-binding element). In jbossas > 5, this used to default to unified. If needed to change to use another > invoker, could either re-define a whole new invoker-proxy-binding and > use its name for each container declaration (or a short cut would be to > just replace the value for invoker-mbean). > > So assuming this is still how head works, could just create a new > standardjboss.xml that declared use of different detached invoker (jrmp > for example), then copy that over the old standardjboss.xml in the conf > directory for tests. > > Jaroslaw Kijanowski wrote: >> >> >> ------------------------------------------------------------------------ >> *From:* Jaroslaw Kijanowski >> *Sent:* Tue 2006-08-29 22:34 >> *To:* Clebert Suconic >> *Subject:* RE: [Fwd: Re: [JBoss-dev] jrmp invoker issue] >> >> I've found the needed invoker definition in >> testsuite\src\resources\test-configs\jrmp-invoker\conf >> So maybe it's not necessary to modify standardjboss.xml, but use somehow >> this in testsuite\src\resources\test-configs\jrmp-invoker\conf.. >> Just copying it into pooled.jar (this is deployed during the test which >> fails) doesn't work. >> >> ------------------------------------------------------------------------ >> *From:* Clebert Suconic >> *Sent:* Tue 2006-08-29 22:26 >> *To:* Tom Elrod >> *Cc:* Tom Elrod; QA Internal >> *Subject:* Re: [Fwd: Re: [JBoss-dev] jrmp invoker issue] >> >> The problem is, stadardjboss.xml on jboss-head doesn't have any of the >> legacy invokers defined, and Jaroslaw has some failures because of that. >> >> >> We need to understand if we are supposed to support JRMP and >> PooledInvokers on jboss-5 or not. >> >> If we are supposed, we would need to add these configurations back on >> standardjboss.xml, then we would have an additional invokers instead of >> replacing it. >> >> On Tue, 2006-08-29 at 22:52 -0400, Tom Elrod wrote: >> > Yes, but need to understand it better first. IIRC, only JBossAS 5 has >> > any config for UnifiedInvokers in the config files. They can be added >> > to JBossAS 4, but is a manual process. I guessed I missed something >> > here. Has this changed? >> > >> > I am not sure what the intersection with what Jaroslaw is saying is with >> > UnifiedInvoker. >> > >> > Clebert Suconic wrote: >> > > Tom, >> > > >> > > Can you please provide some comment on this (@ dev-list)? >> > > >> > > >> > > >> > > -------- Forwarded Message -------- >> > >> From: Clebert Suconic <clebert.suconic(a)jboss.com&gt; >> > >> Reply-To: clebert.suconic(a)jboss.com, JBoss.org development list >> > >> <jboss-development(a)lists.jboss.org&gt; >> > >> To: JBoss.org development list <jboss-development(a)lists.jboss.org&gt; >> > >> Subject: Re: [JBoss-dev] jrmp invoker issue >> > >> Date: Tue, 29 Aug 2006 15:28:34 -0500 >> > >> >> > >> It looks like we removed everything was not using UnifiedINvokers from >> > >> standard-jboss.xml while we still have legacy invokers defined on >> > >> jboss-service.xml. >> > >> >> > >> I know we want to have the setup taking control of this, but as we >> still >> > >> have a testsuite working on this, shouldn't we put these definitions >> > >> back on standardjboss.xml, or should we convert every test we have to >> > >> use UnifiedInvokers and treat everything else a legacy code an >> keep then >> > >> being tested in a separate testsuite? >> > >> >> > >> >> > >> Clebert >> > >> On Tue, 2006-08-29 at 12:41 -0500, Jaroslaw Kijanowski wrote: >> > >>> Hello, >> > >>> there's a test, org.jboss.test.pooled.test.BeanStressTestCase, >> which >> > >>> fails because StatelessSession isn't bound. The original >> > >>> testsuite/src/resources/pooled/META-INF/jboss.xml file looks like >> > >>> this: >> > >>> **************************** >> > >>> <jboss> >> > >>> <enterprise-beans> >> > >>> <session> >> > >>> <ejb-name>StatelessSession</ejb-name> >> > >>> <jndi-name>StatelessSession</jndi-name> >> > >>> <invoker-bindings> >> > >>> <invoker> >> > >>> >> > >>> >> <invoker-proxy-binding-name>stateless-pooled-invoker</invoker-proxy-binding-name> >> > >>> <jndi-name>PooledStatelessSession</jndi-name> >> > >>> </invoker> >> > >>> </invoker-bindings> >> > >>> </session> >> > >>> . >> > >>> . >> > >>> . >> > >>> <invoker-proxy-bindings> >> > >>> <invoker-proxy-binding> >> > >>> <name>stateless-pooled-invoker</name> >> > >>> >> > >>> <invoker-mbean>jboss:service=invoker,type=pooled</invoker-mbean> >> > >>> >> > >>> <proxy-factory>org.jboss.proxy.ejb.ProxyFactory</proxy-factory> >> > >>> <proxy-factory-config> >> > >>> <client-interceptors> >> > >>> <home> >> > >>> >> > >>> <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor> >> > >>> >> > >>> <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor> >> > >>> >> > >>> <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor> >> > >>> >> > >>> <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor> >> > >>> </home> >> > >>> <bean> >> > >>> >> > >>> >> <interceptor>org.jboss.proxy.ejb.StatelessSessionInterceptor</interceptor> >> > >>> >> > >>> <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor> >> > >>> >> > >>> <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor> >> > >>> >> > >>> <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor> >> > >>> </bean> >> > >>> </client-interceptors> >> > >>> </proxy-factory-config> >> > >>> </invoker-proxy-binding> >> > >>> **************************** >> > >>> But this isn't enough to bind StatelessSession >> (PooledStatelessSession >> > >>> is bound right). Exception is thrown. I looked in the 4_0_4 Branch on >> > >>> jboss.xml and I added these missing lines of code to jboss.xml: >> > >>> **************************************** >> > >>> <jboss> >> > >>> <enterprise-beans> >> > >>> <session> >> > >>> <ejb-name>StatelessSession</ejb-name> >> > >>> <jndi-name>StatelessSession</jndi-name> >> > >>> <invoker-bindings> >> > >>> <invoker> >> > >>> >> > >>> >> <invoker-proxy-binding-name>stateless-pooled-invoker</invoker-proxy-binding-name> >> > >>> <jndi-name>PooledStatelessSession</jndi-name> >> > >>> </invoker> >> > >>> >> > >>> <!-- copied from jboss.xml in JBAS 4_0_4 --> >> > >>> <invoker> >> > >>> >> > >>> >> <invoker-proxy-binding-name>stateless-rmi-invoker</invoker-proxy-binding-name> >> > >>> <jndi-name>StatelessSession</jndi-name> >> > >>> </invoker> >> > >>> <!-- end --> >> > >>> >> > >>> </invoker-bindings> >> > >>> </session> >> > >>> **************************************** >> > >>> >> > >>> But the test fails again, because I can't use >> "stateless-rmi-invoker", >> > >>> because it is no longer defined in >> > >>> server/src/etc/conf/default/standardjboss.xml in JBAS 5.0.0beta, why? >> > >>> I've copied the following section from JBAS4_0_4 to JBAS5 and now the >> > >>> test works fine. But is this the right way? >> > >>> **************************************** >> > >>> <invoker-proxy-binding> >> > >>> <name>stateless-rmi-invoker</name> >> > >>> <invoker-mbean>jboss:service=invoker,type=jrmp</invoker-mbean> >> > >>> <proxy-factory>org.jboss.proxy.ejb.ProxyFactory</proxy-factory> >> > >>> <proxy-factory-config> >> > >>> <client-interceptors> >> > >>> <home> >> > >>> >> > >>> <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor> >> > >>> >> > >>> <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor> >> > >>> >> > >>> <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor> >> > >>> <interceptor >> > >>> >> call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor> >> > >>> <interceptor >> > >>> >> call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor> >> > >>> </home> >> > >>> <bean> >> > >>> >> > >>> >> <interceptor>org.jboss.proxy.ejb.StatelessSessionInterceptor</interceptor> >> > >>> >> > >>> <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor> >> > >>> >> > >>> <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor> >> > >>> <interceptor >> > >>> >> call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor> >> > >>> <interceptor >> > >>> >> call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor> >> > >>> </bean> >> > >>> </client-interceptors> >> > >>> </proxy-factory-config> >> > >>> </invoker-proxy-binding> >> > >>> >> > >>> Thanks, >> > >>> Jaroslaw >> > >>> >> > >>> _______________________________________________ >> > >>> jboss-development mailing list >> > >>> jboss-development(a)lists.jboss.org >> > >>> https://lists.jboss.org/mailman/listinfo/jboss-development >> -- >> Clebert Suconic >> Core Developer >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> 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

An ejb container can have multiple invokers, only the container configuration has one default. All standard invokers should have an invoker-proxy-binding defined in the standardjboss.xml descriptor so that it can easily be used in deployment jboss.xml descriptors to add an invoker to a deployment container or change the default for a container configuration. Tom Elrod wrote: > Not sure I understand your suggestion. An ejb 2.x container can only > have *one* invoker specified (as only one can be used at any point in > time). The standardjboss.xml is the file where which invoker to use > is specified. Maybe you mean keep all three invokers declared (in the > jboss-service.xml) so that all three start up and are available for > use. Then to change which one gets used can by simply changing which > one is referenced in the standardjboss.xml? >

That's what I wanted to hear. So it's a bug, that the definition for the jrmp invoker is missing in server/src/etc/conf/default/standardjboss.xml. I will add the following lines to the file, because they should be present, right? We still want to be able to use jrmp invoker. **************************************** <invoker-proxy-binding> <name>stateless-rmi-invoker</name> <invoker-mbean>jboss:service=invoker,type=jrmp</invoker-mbean> <proxy-factory>org.jboss.proxy.ejb.ProxyFactory</proxy-factory> <proxy-factory-config> <client-interceptors> <home> <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor> <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor> <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor> <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor> <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor> </home> <bean> <interceptor>org.jboss.proxy.ejb.StatelessSessionInterceptor</interceptor> <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor> <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor> <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor> <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor> </bean> </client-interceptors> </proxy-factory-config> </invoker-proxy-binding> ------------------------------------------------------------------------ *From:* jboss-development-bounces(a)lists.jboss.org on behalf of Scott M Stark *Sent:* Wed 2006-08-30 12:32 *To:* JBoss.org development list *Subject:* Re: FW: [Fwd: Re: [JBoss-dev] jrmp invoker issue] An ejb container can have multiple invokers, only the container configuration has one default. All standard invokers should have an invoker-proxy-binding defined in the standardjboss.xml descriptor so that it can easily be used in deployment jboss.xml descriptors to add an invoker to a deployment container or change the default for a container configuration. Tom Elrod wrote: > Not sure I understand your suggestion. An ejb 2.x container can only > have *one* invoker specified (as only one can be used at any point in > time). The standardjboss.xml is the file where which invoker to use > is specified. Maybe you mean keep all three invokers declared (in the > jboss-service.xml) so that all three start up and are available for > use. Then to change which one gets used can by simply changing which > one is referenced in the standardjboss.xml? > _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development