8 Replies Latest reply on Apr 18, 2003 6:47 AM by Horia Muntean

    Container configuration for my MDB doesn't work as expected

    Bernd Zeitler Expert

      Hi,

      I am providing my own container configuration in jboss.xml deployed with my MDB. But it seems, that the container-invoker-conf doesn't work. I am using JBoss 3.2RC4 and the jboss.xml is valid against jboss_3_2.dtd .

      This is a snippit of the jboss.xml:
      [pre]
      <container-configuration>
      <container-name>My Message Driven Bean</container-name>
      <call-logging>false</call-logging>
      <container-interceptors>
      org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor
      org.jboss.ejb.plugins.LogInterceptor
      org.jboss.ejb.plugins.RunAsSecurityInterceptor
      <!-- CMT -->
      org.jboss.ejb.plugins.TxInterceptorCMT
      org.jboss.ejb.plugins.MetricsInterceptor
      org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor
      <!-- BMT -->
      org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor
      org.jboss.ejb.plugins.MessageDrivenTxInterceptorBMT
      org.jboss.ejb.plugins.MetricsInterceptor
      org.jboss.resource.connectionmanager.CachedConnectionInterceptor
      </container-interceptors>
      <instance-pool>org.jboss.ejb.plugins.MessageDrivenInstancePool</instance-pool>
      <instance-cache></instance-cache>
      <persistence-manager></persistence-manager>
      <transaction-manager>org.jboss.tm.TxManager</transaction-manager>
      <container-invoker-conf>

      20

      queue/myDLQ
      1
      60


      </container-invoker-conf>
      <container-pool-conf>
      100
      </container-pool-conf>
      </container-configuration>
      [/pre]

      The configuration used instead is defined in my standardjboss.xml (invoker-proxy-binding).

      What do I have to do to get my own configuration working (differend configurations for different beans deployed in my .jar)?

      Greetings,

      Frito