0 Replies Latest reply on Mar 27, 2003 1:20 PM by John

    Session Pool Configuration

    John Newbie

      Hi,

      In Jboss 3.0.0-Tomcat 4.0.3, I deployed an MDB with the intention of only having 1 bean in the pool at any time. It worked fine. Here is the jboss.xml for this bean:

      <?xml version="1.0" encoding="UTF-8"?>

      <enterprise-beans>
      <message-driven>
      <ejb-name>POInfoListener</ejb-name>
      jboss.j2ee:service=EJB,jndiName=ejb/Configuration
      <configuration-name>Standard Message Driven Bean</configuration-name>
      <destination-jndi-name>queue/POInfoNativeQ</destination-jndi-name>
      </message-driven>

      <container-configurations>
      <container-configuration>
      <container-name>Standard Message Driven Bean</container-name>
      <container-invoker-conf>
      DefaultJMSProvider
      StdJMSPool
      1
      1
      True
      </container-invoker-conf>
      <container-pool-conf>
      1
      1
      True
      </container-pool-conf>
      </container-configuration>
      </container-configurations>

      </enterprise-beans>


      I switched to JBoss 3.0.4 - Tomcat 4.1.12 and now the session pool configuration is being ignored - the container creates a new bean instance for each JMS message. I only want 1 bean to ever exists in the pool.

      Has anyone been able to configure this properly?

      Thanks in advance.

      John