Re: Geronimo 2.1.1 MDB Performance Question

Wed, 16 Jul 2008 10:06:12 -0700

I think there's a setting for the mdb pool size in the activation spec. Also it looks like the DefaultWorkManager only has 30 threads which is pretty low but I don't see offhand how this would result in only 10 worker threads. 

thanks
david jencks

On Jul 16, 2008, at 3:38 AM, Mario Kofler wrote:


my connection factory is successfully deployed on the server and the
queue is using it as far as i can say. nevertheless, not more than 10
connections are made to the database.

does the connection factory pool size always have to be the amount of
data source connections? i already tried with 20 but still no
difference, just 10 database connections open at one time.

is there a possibility to adjust the message-queue size somehow?

thanks a lot for the answers,

greetings,

mario.


2008/7/16 Mario Kofler <[EMAIL PROTECTED]>:

actually i deployed a geronimo-application.xml deployment plan,
defining the connection factory:

  <ext-module>
    <connector>jms-resources</connector>
    <external-path
xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2";>
      <dep:groupId>org.apache.geronimo.modules</dep:groupId>
      <dep:artifactId>geronimo-activemq-ra</dep:artifactId>
      <dep:version>2.1.1</dep:version>
      <dep:type>rar</dep:type>
    </external-path>
<connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2 "> 
      <dep:environment
xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2";>
        <dep:dependencies>
          <dep:dependency>
            <dep:groupId>org.apache.geronimo.configs</dep:groupId>
             <dep:artifactId>activemq-broker</dep:artifactId>
            <dep:version>2.1.1</dep:version>
            <dep:type>car</dep:type>
          </dep:dependency>
        </dep:dependencies>
      </dep:environment>
      <resourceadapter>
        <resourceadapter-instance>
          <resourceadapter-name>jms-resources</resourceadapter-name>
<workmanager xmlns="http://geronimo.apache.org/xml/ns/naming-1.2 "> 
            <gbean-link>DefaultWorkManager</gbean-link>
          </workmanager>
        </resourceadapter-instance>
        <outbound-resourceadapter>
          <connection-definition>
<connectionfactory- interface>javax.jms.ConnectionFactory</connectionfactory-interface> 
            <connectiondefinition-instance>
              <name>VideoConnectionFactory</name>
<implemented-interface>javax.jms.QueueConnectionFactory</ implemented-interface>
<implemented-interface>javax.jms.TopicConnectionFactory</ implemented-interface> 
              <connectionmanager>
                <xa-transaction>
                  <transaction-caching/>
                </xa-transaction>
                <single-pool>
                  <max-size>200</max-size>
                  <min-size>0</min-size>

<blocking-timeout-milliseconds>5000</blocking-timeout-milliseconds>
                  <idle-timeout-minutes>5</idle-timeout-minutes>
                  <match-one/>
                </single-pool>
              </connectionmanager>
            </connectiondefinition-instance>
          </connection-definition>
        </outbound-resourceadapter>
      </resourceadapter>
      <adminobject>
<adminobject-interface>javax.jms.Queue</adminobject- interface> <adminobject- class>org.apache.activemq.command.ActiveMQQueue</adminobject-class> 
        <adminobject-instance>
<message-destination-name>queue/videoupdate</message- destination-name> 
          <config-property-setting
name="PhysicalName">queue/videoupdate</config-property-setting>
        </adminobject-instance>
      </adminobject>
    </connector>
but maybe it ignores these settings and it takes the default settings. 
i will give it a try,

thanks for helping,

mario.

2008/7/16 YunFeng Ma <[EMAIL PROTECTED]>:
Are you using the default ActiveMQ RA (DefaultActiveMQConnectionFactory) to 
send the JMS message? DefaultActiveMQConnectionFactory configures a
single-pool with default max-size 10. I'm not sure whether this can explain what you saw in your scenario, but I think you can try to create a new 
ActiveMQ RA (you can do this via admin console) with a larger size
single-pool and rerun your scenario.

Hope this helps.

-- Yun Feng

the666pack wrote:

hello,

i have a question regarding MDBS in Geronimo 2.1.1
i bombard the server with a high amount of mdb requests, the mdbs write tuples to a database. so although my database connection pool maximum is 
20
i realize that with mdbs the pool is just utilized with 10 connections to 
the database, no matter how many requests are coming in.
does somebody have an idea what might be the reason for this behaviour? 

thanks a lot,

mario

Reply via email to