Return-Path: 
 <user-return-11656-apmail-geronimo-user-archive=geronimo.apache.org@geronimo.apache.org>
Delivered-To: apmail-geronimo-user-archive@www.apache.org
Received: (qmail 6831 invoked from network); 3 Oct 2008 14:18:38 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 3 Oct 2008 14:18:38 -0000
Received: (qmail 36903 invoked by uid 500); 3 Oct 2008 14:18:36 -0000
Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org
Received: (qmail 36356 invoked by uid 500); 3 Oct 2008 14:18:35 -0000
Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:user-help@geronimo.apache.org>
list-unsubscribe: <mailto:user-unsubscribe@geronimo.apache.org>
List-Post: <mailto:user@geronimo.apache.org>
Reply-To: user@geronimo.apache.org
List-Id: <user.geronimo.apache.org>
Delivered-To: mailing list user@geronimo.apache.org
Received: (qmail 36345 invoked by uid 99); 3 Oct 2008 14:18:35 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Oct 2008 07:18:35 -0700
X-ASF-Spam-Status: No, hits=0.2 required=10.0
	tests=SPF_PASS,WHOIS_MYPRIVREG
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of manu.t.george@gmail.com
 designates 209.85.142.191 as permitted sender)
Received: from [209.85.142.191] (HELO ti-out-0910.google.com) (209.85.142.191)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Oct 2008 14:17:31 +0000
Received: by ti-out-0910.google.com with SMTP id b6so794812tic.1
        for <user@geronimo.apache.org>; Fri, 03 Oct 2008 07:17:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to
         :subject:in-reply-to:mime-version:content-type
         :content-transfer-encoding:content-disposition:references;
        bh=oJB9hXXFd8+2OY6XQKFSJW9gKgYaje2alEuOiOTcowg=;
        b=f4s6p0L6Uy0+yJlDAQZe7Ga5bNn/w5MxwxFlbdlXE6RZMtaol1d1GcrWtMkQECuhlP
         8WOaJi8lsYlFZvaNE9nslryZyG1FSveYuVQASMCmxmH0aqFfmraDBzkdhhvaGtcpXrhJ
         O9tq6nder2oamBDeB65xYQG6ULlJRjyoQs0MM=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=U58SpiN+7ocSMsce0mbvJmdzTOKcH0sDead1r0HzFRKioNyyEiJaVbAYdljkPfTnk3
         AQ2tSJYi3HvvEU9wZB0jI0UOhB7pjzs2N9CwoESCW1C8Lx61qp8A0qX+M9xI9vAdyspj
         YF+j2JQWCBahHwl5yxG0IPBrs0XidrLpSXrTA=
Received: by 10.110.46.3 with SMTP id t3mr831523tit.30.1223043468211;
        Fri, 03 Oct 2008 07:17:48 -0700 (PDT)
Received: by 10.110.3.11 with HTTP; Fri, 3 Oct 2008 07:17:48 -0700 (PDT)
Message-ID: <466797bd0810030717h2c121963x94a7d42e58e65e12@mail.gmail.com>
Date: Fri, 3 Oct 2008 19:47:48 +0530
From: "Manu George" <manu.t.george@gmail.com>
To: user@geronimo.apache.org
Subject: Re: MDB pool size
In-Reply-To: <466797bd0810030647i4889ab05j27e5cbbbe014d33e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <19759437.post@talk.nabble.com>
	 <F2ECDBD6-9371-4D82-9398-CC82ECA98F90@yahoo.com>
	 <19776736.post@talk.nabble.com>
	 <466797bd0810030605v59018253w8a730256f209e378@mail.gmail.com>
	 <466797bd0810030647i4889ab05j27e5cbbbe014d33e@mail.gmail.com>
X-Virus-Checked: Checked by ClamAV on apache.org

One thing to keep in mind while setting the instance limit. I just
tried it out in trunk in config.xml

 <module name="org.apache.geronimo.configs/j2ee-server/2.2-SNAPSHOT/car">
<gbean gbeanInfo="org.apache.geronimo.system.properties.SystemProperties"
name="org.apache.geronimo.configs/j2ee-server/2.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/j2ee-server/2.2-SNAPSHOT/car,j2eeType=GBean,name=CustomPropertiesGBean">
<attribute name="systemProperties">Apache/TestingJMS/1/rar.TestingJMS-javax.jms.MessageListener.InstanceLimit=100</attribute>
</gbean>
    </module>

Here notice the name of the Mdb container. It is actually in the
format $moduleName.$shortName-javax.jms.MessageListener where
$moduleName is the name of the resource adapter module the mdb is
using i.e Apache/TestingJMS/1/rar and the shortName in this case is
the value of the resourceadapter-name property in the RA plan i.e.
TestingJMS. So the property can be set as
containerName.propertyName=propertyValue or
Apache/TestingJMS/1/rar.TestingJMS-javax.jms.MessageListener.InstanceLimit=100

Regards
Manu



On Fri, Oct 3, 2008 at 7:17 PM, Manu George <manu.t.george@gmail.com> wrote:
> Hi Vladimir,
>              If the issue still persists, can you open a JIRA and
> upload a sample that illustrates the issue. It will be really helpful
> for us to debug.
>
> Regards
> Manu
>
>
> On Fri, Oct 3, 2008 at 6:35 PM, Manu George <manu.t.george@gmail.com> wrote:
>> Hi Vladimir,
>>               Try raising the instanceLimit also to 50. By default it
>> is 10. The following JIRA gives u the steps
>> https://issues.apache.org/jira/browse/GERONIMO-3783
>>
>> Regards
>> Manu
>>
>> On Thu, Oct 2, 2008 at 3:54 PM, my_forum <my_forum@ukr.net> wrote:
>>>
>>>
>>> djencks wrote:
>>>>
>>>> You also have to configure the MDB pool size.  I don't remember
>>>> whether this is in the MDB configuration in openejb-jar.xml or in the
>>>> openejb MDB container configuration itself.  I think this question has
>>>> been discussed before on the user list.... if not perhaps someone with
>>>> more specific knowledge will provide more info.
>>>>
>>>> david jencks
>>>>
>>>> On Oct 1, 2008, at 5:31 AM, my_forum wrote:
>>>>
>>>>>
>>>>> Guys,
>>>>> Could anyone tell me how I can to increase MDB pool size (the
>>>>> default value
>>>>> is 10 as far as I understand). I tryied to set Pool Min Size = 20
>>>>> and Pool
>>>>> Max Size = 50 while setting up the connection factory but looks like
>>>>> this
>>>>> does not have any effect i.e. the the pool is still equal to 10 (ten
>>>>> messages are processed simultaneously)
>>>>> --
>>>>> View this message in context:
>>>>> http://www.nabble.com/MDB-pool-size-tp19759437s134p19759437.html
>>>>> Sent from the Apache Geronimo - Users mailing list archive at
>>>>> Nabble.com.
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> David,
>>> I send 100 test messages to my queue as usual.
>>> I have tried the following:
>>> 1. Changed Pool Min Size=50 and Pool Max Size=50 in my
>>> QueueConnectionFactoryJMS resource
>>> 2. Added activation properties to my MDB
>>>
>>>    @ActivationConfigProperty(propertyName="maxSessions",
>>> propertyValue="50"),
>>>    @ActivationConfigProperty(propertyName="maxMessagesPerSessions",
>>> propertyValue="50")
>>>
>>> But this also does not have any effect (10 messages are processing
>>> simultaneously instead of 50 as I expect).
>>>
>>> However I can decrease the bandwidth when I set
>>>    @ActivationConfigProperty(propertyName="maxSessions",
>>> propertyValue="5"),
>>>    @ActivationConfigProperty(propertyName="maxMessagesPerSessions",
>>> propertyValue="5")
>>> 5 messages are processing simultaneously instead of 10 now and that's OK
>>>
>>> I thought to use minSessions, minMessagesPerSessions but no such activation
>>> parameters exist.
>>> So I can decerase the bandwidth but can not increase it. Probably someone
>>> undocumented limitation exists...
>>>
>>> Could you please refer me to the 'person with more specific knowledge'?
>>> Thanks,
>>> Vladimir.
>>>
>>>
>>>
>>> --
>>> View this message in context: http://www.nabble.com/MDB-pool-size-tp19759437s134p19776736.html
>>> Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
>>>
>>>
>>
>