Geronimo
  1. Geronimo
  2. GERONIMO-3115

MDB pool size should be able to be configurable in openejb-jar.xsd

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 2.0-M6
    • Fix Version/s: 2.0.3, 2.1
    • Component/s: OpenEJB
    • Security Level: public (Regular issues)
    • Labels:
      None

      Description

      There should be an attribute for message driven beans in the openejb-jar.xsd schema that will configure the pool size. For example, if a pool size of "1" were configured for a specific bean, then there would only be a maximum of 1 message driven bean instance of that type that would be instantiated.

        Activity

        Hide
        Kevan Miller added a comment -

        as described in the jira, pool size is configurable.

        Show
        Kevan Miller added a comment - as described in the jira, pool size is configurable.
        Hide
        Manu T George added a comment -

        Descriptions are given here. http://activemq.apache.org/activation-spec-properties.html
        I think it will map to the max number of sessions that can be opened by the entire set of MDBs of a particular instance type since there is no pooling at the EJB container side.

        Show
        Manu T George added a comment - Descriptions are given here. http://activemq.apache.org/activation-spec-properties.html I think it will map to the max number of sessions that can be opened by the entire set of MDBs of a particular instance type since there is no pooling at the EJB container side.
        Hide
        Aman Nanner added a comment -

        I tried this out and it works! This is exactly what I was looking for. Is there any documentation on what each property actually configures? Is the "maxSessions" value equal to the max number of sessions that can be opened by a particular MDB bean instance, or is it the max number of sessions that can be opened by the entire set of MDBs of a particular instance type?

        Show
        Aman Nanner added a comment - I tried this out and it works! This is exactly what I was looking for. Is there any documentation on what each property actually configures? Is the "maxSessions" value equal to the max number of sessions that can be opened by a particular MDB bean instance, or is it the max number of sessions that can be opened by the entire set of MDBs of a particular instance type?
        Hide
        Manu T George added a comment -

        Infact using the above method we need not even have two resource adapters and the performance is also better than using the dual RAs

        Show
        Manu T George added a comment - Infact using the above method we need not even have two resource adapters and the performance is also better than using the dual RAs
        Hide
        Manu T George added a comment -

        You can still make it work by setting the following for your MDB

        <activation-config>
        <activation-config-property>
        <activation-config-property-name>maxSessions</activation-config-property-name>
        <activation-config-property-value>1</activation-config-property-value>
        </activation-config-property>
        <activation-config-property>
        <activation-config-property-name>maxMessagesPerSessions </activation-config-property-name>
        <activation-config-property-value>1</activation-config-property-value>
        </activation-config-property>
        </activation-config>

        Show
        Manu T George added a comment - You can still make it work by setting the following for your MDB <activation-config> <activation-config-property> <activation-config-property-name>maxSessions</activation-config-property-name> <activation-config-property-value>1</activation-config-property-value> </activation-config-property> <activation-config-property> <activation-config-property-name>maxMessagesPerSessions </activation-config-property-name> <activation-config-property-value>1</activation-config-property-value> </activation-config-property> </activation-config>
        Hide
        Aman Nanner added a comment -

        Has this been shown to work in a real example?

        Show
        Aman Nanner added a comment - Has this been shown to work in a real example?
        Hide
        Aman Nanner added a comment -
        Show
        Aman Nanner added a comment - I had tried this at one time and it didn't work: http://www.nabble.com/Sharing-resources-in-an-MDB-tf3412013s134.html#a9506828
        Hide
        Manu T George added a comment -

        This mail from the openejb-dev list may throw some light on the matter
        http://mail-archives.apache.org/mod_mbox/openejb-dev/200706.mbox/%3CB1AE72A1-3DF5-40BD-9DD5-5AEF27700151@iq80.com%3E

        In the case of openejb integrated in geronimo, you can only set the pool size on the resource adapter. An MDB container is created for each adapter provided you have an MDB using that RA. So you can create a new RA with the pool size as 1 and then assign the MDB (for which pool size is 1) to that RA.

        This is how you can get a pool size of 1 currently.

        Show
        Manu T George added a comment - This mail from the openejb-dev list may throw some light on the matter http://mail-archives.apache.org/mod_mbox/openejb-dev/200706.mbox/%3CB1AE72A1-3DF5-40BD-9DD5-5AEF27700151@iq80.com%3E In the case of openejb integrated in geronimo, you can only set the pool size on the resource adapter. An MDB container is created for each adapter provided you have an MDB using that RA. So you can create a new RA with the pool size as 1 and then assign the MDB (for which pool size is 1) to that RA. This is how you can get a pool size of 1 currently.

          People

          • Assignee:
            Unassigned
            Reporter:
            Aman Nanner
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development