You are right, I cannot give you a reason. Looking at it now I cannot find anything that depends on my JMSProvider. But it was just a last attempt to help you with my limited knowledge. My strategie is "first copy almost everything" till it works, then "try to modify and cut things away". Perhaps I have not cut away enough, perhaps you have not copied enough...
But wait, when I once again look at your config there is one thing I don't understand: Why do both of your Providers use the same jndiname to register their ConnectionFactories to? Maybe one overwrites the other? The ProviderLoader obtains a Connection after looking up these Factories, so how could this work? Just my 2c Michael Bartmann Barlow, Dustin wrote: > I didn't, but instead used the default one that was already setup in the > standardjboss.xml as I didn't see any difference between it and yours. Is > that incorrect to do? > > Dustin > > >>-----Original Message----- >>From: Michael Bartmann [mailto:[EMAIL PROTECTED]] >>Sent: Tuesday, September 17, 2002 3:19 PM >>To: [EMAIL PROTECTED] >>Subject: Re: [JBoss-user] 3.2.x config for JBoss based remote JMS >>queues/t opics and MDB? >> >> >>Did you also copy the MBean with the ServerSessionPool from >>my ...-service.xml? >> >>Michael Bartmann >> >>Barlow, Dustin wrote: >> >>>Ok, I did what you suggested, and also looked at Michael Bartmann's >>>configuration he was kind enough to forward to me, but it's >> >>still now >> >>>working. Just to be clear, I am using version 3.2.0RC1. >>> >>>It appears that when I deploy the MDB that it's still using the >>>DefaultJMSProvider, not my new one. >>> >>>My jboss.xml (bundled with the MDB) : >>> >>><?xml version="1.0"?> >>><jboss> >>> <enterprise-beans> >>> <message-driven> >>> <ejb-name>TextQueueMDB</ejb-name> >>> <configuration-name>RemoteMDB</configuration-name> >>> >> >><destination-jndi-name>queue/testQueue</destination-jndi-name> >> >>> >>> >> >><depends>jboss.mq:service=JMSProviderLoader,name=RemoteJBossMQ >>Provider</depe >> >>>nds> >>> </message-driven> >>> </enterprise-beans> >>> >>> <container-configurations> >>> <container-configuration> >>> <container-name>RemoteMDB</container-name> >>> <call-logging>false</call-logging> >>> <container-interceptors> >>> >> >><interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor> >> >>> >>> >> >><interceptor>org.jboss.ejb.plugins.RunAsSecurityInterceptor</i >>nterceptor> >> >>> <interceptor >>> >> >>transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT >></interceptor> >> >>> <interceptor transaction="Container" >>> >> >>metricsEnabled="true">org.jboss.ejb.plugins.MetricsInterceptor >></interceptor> >> >>> <interceptor >>> >> >>transaction="Container">org.jboss.ejb.plugins.MessageDrivenIns >>tanceIntercept >> >>>or</interceptor> >>> <interceptor >>> >> >>transaction="Bean">org.jboss.ejb.plugins.MessageDrivenInstance >>Interceptor</i >> >>>nterceptor> >>> <interceptor >>> >> >>transaction="Bean">org.jboss.ejb.plugins.MessageDrivenTxInterc >>eptorBMT</inte >> >>>rceptor> >>> <interceptor transaction="Bean" >>> >> >>metricsEnabled="true">org.jboss.ejb.plugins.MetricsInterceptor >></interceptor> >> >>> >>> >> >><interceptor>org.jboss.resource.connectionmanager.CachedConnec >>tionIntercepto >> >>>r</interceptor> >>> </container-interceptors> >>> >>> >> >><instance-pool>org.jboss.ejb.plugins.MessageDrivenInstancePool >></instance-poo >> >>>l> >>> <instance-cache></instance-cache> >>> <persistence-manager></persistence-manager> >>> >> >><transaction-manager>org.jboss.tm.TxManager</transaction-manager> >> >>> <container-pool-conf> >>> <MaximumSize>100</MaximumSize> >>> >>> >> >><feeder-policy>org.jboss.ejb.plugins.TimedInstancePoolFeeder</ >>feeder-policy> >> >>> <feeder-policy-conf> >>> <increment>10</increment> >>> <period>500</period> >>> </feeder-policy-conf> >>> </container-pool-conf> >>> </container-configuration> >>> </container-configurations> >>> >>> <invoker-proxy-binding> >>> <name>message-driven-bean</name> >>> <invoker-mbean>default</invoker-mbean> >>> >>> >> >><proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</ >>proxy-factory> >> >>> <proxy-factory-config> >>> >>> >> >><JMSProviderAdapterJNDI>java:/RemoteJMSProvider</JMSProviderAd >>apterJNDI> >> >>> >>> >> >><ServerSessionPoolFactoryJNDI>java:/StdJMSPool</ServerSessionP >>oolFactoryJNDI >> >>> <MaximumSize>15</MaximumSize> >>> <MaxMessages>1</MaxMessages> >>> <Optimized>True</Optimized> >>> <MDBConfig> >>> <ReconnectIntervalSec>10</ReconnectIntervalSec> >>> <!-- <DLQConfig> >>> <DestinationQueue>queue/DLQ</DestinationQueue> >>> <MaxTimesRedelivered>10</MaxTimesRedelivered> >>> <TimeToLive>0</TimeToLive> >>> </DLQConfig> --> >>> </MDBConfig> >>> </proxy-factory-config> >>> </invoker-proxy-binding> >>></jboss> >>> >>> >>>My jms-service.xml has the following included: >>> >>> <!-- The JMS provider loader --> >>> <mbean code="org.jboss.jms.jndi.JMSProviderLoader" >>> name="jboss.mq:service=JMSProviderLoader,name=JBossMQProvider"> >>> <attribute name="ProviderName">DefaultJMSProvider</attribute> >>> <attribute name="ProviderAdapterClass"> >>> org.jboss.jms.jndi.JBossMQProvider >>> </attribute> >>> <attribute >> >>name="QueueFactoryRef">java:/XAConnectionFactory</attribute> >> >>> <attribute >> >>name="TopicFactoryRef">java:/XAConnectionFactory</attribute> >> >>> </mbean> >>> >>> <!-- The JMS provider loader --> >>> <mbean code="org.jboss.jms.jndi.JMSProviderLoader" >>> >>> >> >>name="jboss.mq:service=JMSProviderLoader,name=RemoteJBossMQProvider"> >> >>> <attribute name="ProviderName">RemoteJMSProvider</attribute> >>> <attribute name="ProviderAdapterClass"> >>> org.jboss.jms.jndi.JBossMQProvider >>> </attribute> >>> <attribute >> >>name="QueueFactoryRef">java:/XAConnectionFactory</attribute> >> >>> <attribute >> >>name="TopicFactoryRef">java:/XAConnectionFactory</attribute> >> >>> <attribute name="ProviderUrl">my.remote.host:1099</attribute> >>> </mbean> >>> >>> >>>The JMSProvider that I want to use is the >> >>RemoteJBossMQProvider as it has >> >>>the ProviderUrl pointing to the remote JMS host. The >> >>JBossMQProvider one is >> >>>the default JBoss provider. I'm not seeing from the >> >>examples how the >> >>><invoker-proxy-bindings> ties to the >> >><container-configuration> section. >> >>>Seems like I'm still missing something. >>> >>>I did decide to use the default ServerSessionPoolLoader >> >>that comes with >> >>>JBoss instead of creating my own. I presume that is ok. >>> >>>Any other tips? >>> >>>Dustin >>> >>> >>> >>>>-----Original Message----- >>>>From: Peter Antman [mailto:[EMAIL PROTECTED]] >>>>Sent: Tuesday, September 17, 2002 10:59 AM >>>>To: [EMAIL PROTECTED] >>>>Subject: Re: [JBoss-user] 3.2.x config for JBoss based remote JMS >>>>queues/t opics and MDB? >>>> >>>> >>>>You hace to have a complete container cinbfiguration. Not just my >>>>snippet. Steel one from stdjboss or whats its named. >>>> >>>>//Peter >>> >>> >>> >>>------------------------------------------------------- >>>This SF.NET email is sponsored by: AMD - Your access to the experts >>>on Hammer Technology! Open Source & Linux Developers, register now >>>for the AMD Developer Symposium. Code: EX8664 >>>http://www.developwithamd.com/developerlab >>>_______________________________________________ >>>JBoss-user mailing list >>>[EMAIL PROTECTED] >>>https://lists.sourceforge.net/lists/listinfo/jboss-user >>> >> >> >> >>------------------------------------------------------- >>This SF.NET email is sponsored by: AMD - Your access to the experts >>on Hammer Technology! Open Source & Linux Developers, register now >>for the AMD Developer Symposium. Code: EX8664 >>http://www.developwithamd.com/developerlab >>_______________________________________________ >>JBoss-user mailing list >>[EMAIL PROTECTED] >>https://lists.sourceforge.net/lists/listinfo/jboss-user >> > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: AMD - Your access to the experts > on Hammer Technology! Open Source & Linux Developers, register now > for the AMD Developer Symposium. Code: EX8664 > http://www.developwithamd.com/developerlab > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > ------------------------------------------------------- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source & Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
