geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manu George" <manu.t.geo...@gmail.com>
Subject Re: Geronimo 2.1.1 MDB Performance Question
Date Tue, 22 Jul 2008 08:45:55 GMT
Hi Mario,
               Can you post a sample or modify the sample in the JIRA
to replicate your issue and attach it in the mail. It will be very
helpful to debug in that case

Regards
Manu

On Sat, Jul 19, 2008 at 7:12 PM, Mario Kofler <mario.kofler@gmail.com> wrote:
> hello,
>
> i hate to say it but it i still don't see more than 10 threads.
>
> i made the additional pool in the geronimo-application.xml just like
> it was written in that JIRA. then my jsp takes the sender pool and the
> mdb takes the receiver pool. both pools configured just like in the
> posting.
>
> when i look at my web management console i still see just 10 threads
> in use (out of my 250). the thread pool that is used is the
> ConnectorThread pool.
>
> the DefaultThreadpool stays idle with 0 threads and no more thread
> pools are listed.
>
> is there a possibility how i could monitor my queue or the 2 thread
> pools that obviously should exist somewhere (because i got an
> exception as i did not change the referred name in the web.xml and the
> jsp).
>
> can it be that through the manual videoqueue settings in the ear the
> server "Default\ MDB\ Container.InstanceLimit" setting is ignored?
>
> if yes, how can i set them in the application directly? via the
> application-spec? i already set them both to the same value and to the
> same value as the thread pools and this value is higher than 10.
>
> if you want i can post my deployment descriptors here, if it helps somehow.
>
> thanks a lot for helping out,
>
> greetings,
>
> mario.
>
>
> 2008/7/18 Manu George <manu.t.george@gmail.com>:
>> Hi Mario,
>>        Looks like you have enough threads. Try making the
>> instanceLimit also equivalent to maxSessions and
>> maxMessagesPerSession.
>> The explanation for these properties is given here
>> http://activemq.apache.org/activation-spec-properties.html
>>
>> InstanceLimit actually is a facility to limit the no of bean instances
>> created. Making it 0 will make the instanceLimit unlimited and so
>> there will be no limiting from the ejb container side. The no of
>> parallel instances will be from maxSessions
>>
>> The JIRA whose link I posted in one of the previous mails contains a
>> sample plan for defining a separate thread pool/work manager for the
>> connector
>>
>> Regards
>> Manu
>>
>> On Fri, Jul 18, 2008 at 7:58 PM, Mario Kofler <mario.kofler@gmail.com> wrote:
>>> hello,
>>>
>>> sorry for the latest issue, this was an error in my application.
>>>
>>> can you perhaps tell me how i can increase the thread-pool for the
>>> activemq-resource-adapter? i just have my "default-thread-pool which
>>> has a maximum of 250 threads but it seems that just 10 are used at
>>> maximum when i make my MDB test.
>>>
>>>  i already have
>>>
>>> connection factory single-pool: 20
>>> jdbc pool = 20
>>> maxSessions = 20
>>> ejb container pool = 32
>>>
>>>
>>>  by the way can someone tell me the connection between
>>> ejb-container-pool and max-sessions value?? i dont see the big picture
>>> and i dont get it.
>>>
>>> i thought ejb container pool is the amount of simultaneous connections
>>> that can be established. so what is max-sessions? can i set it to 32
>>> or does it have to stay the same value as my jdbc/connection factory
>>> values?
>>>
>>> thanks very much for helping,
>>>
>>> mario
>>>
>>> 2008/7/18 Manu George <manu.t.george@gmail.com>:
>>>> I believe there was a similar issue some time back where u needed
>>>> maxSessions and maxMessagesPerSession to be equal. So can you try
>>>> giving both and making them equal. The jira is
>>>> https://issues.apache.org/jira/browse/GERONIMO-3783
>>>>
>>>> David Jencks had fixed this issue to the best of my knowledge and so
>>>> this shouldn't happen but just try whether that makes any difference.
>>>>
>>>> Another thing that you can try is increasing the number of threads in
>>>> the thread pool for the RA.
>>>>
>>>> Regards
>>>> Manu.
>>>>
>>>> On Fri, Jul 18, 2008 at 6:55 PM, Mario Kofler <mario.kofler@gmail.com>
wrote:
>>>>> hello,
>>>>>
>>>>> after all i specify it in my mdb via
>>>>>
>>>>> @MessageDriven(activationConfig = {
>>>>>        @ActivationConfigProperty(propertyName = "destinationType",
>>>>>                                  propertyValue = "javax.jms.Queue"),
>>>>>        @ActivationConfigProperty(propertyName = "maxSessions",
>>>>>                propertyValue = "20"),
>>>>>        @ActivationConfigProperty(propertyName = "destination",
>>>>>        propertyValue = "queue/videoupdate")})
>>>>>
>>>>> HOWEVER after i inserted the maxSessions property no messages get
>>>>> delivered anymore. also when i change back the prop by commenting it
>>>>> out i dont get messages anymore through my queue. so my database is
>>>>> never updated.
>>>>>
>>>>> after this error i do not know anything else than reinstalling the
>>>>> whole server. i dont even get an error. just no update in the database
>>>>> anymore and that's it.
>>>>>
>>>>> maybe some ideas?
>>>>>
>>>>> thanks a lot,
>>>>>
>>>>> mario.
>>>>>
>>>>> 2008/7/17 Lin Sun <linsun.unc@gmail.com>:
>>>>>> Did you try increasing the maxSessions and maxMessagesPerSessions
>>>>>> values in your openejb deployment plan?   The default is 10.
>>>>>>
>>>>>> Here is some information on this -
>>>>>> http://activemq.apache.org/activation-spec-properties.html
>>>>>>
>>>>>> Lin
>>>>>>
>>>>>> On Thu, Jul 17, 2008 at 1:17 PM, Mario Kofler <mario.kofler@gmail.com>
wrote:
>>>>>>> 2008/7/16 David Jencks <david_jencks@yahoo.com>:
>>>>>>>> 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.
>>>>>>>
>>>>>>> hello,
>>>>>>>
>>>>>>> i suppose it is right to set the MDB container instance size
in the
>>>>>>> config.xml for this?
>>>>>>>
>>>>>>> <gbean name="org.apache.geronimo.configs/j2ee-server/2.1.1/car?ServiceModule=org.apache.geronimo.configs/j2ee-server/2.1.1/car,j2eeType=GBean,name=CustomPropertiesGBean"
>>>>>>> gbeanInfo="org.apache.geronimo.system.properties.SystemProperties">
>>>>>>>            <attribute name="systemProperties">Default\
MDB\
>>>>>>> Container.InstanceLimit=32</attribute>
>>>>>>>        </gbean>
>>>>>>>    </module>
>>>>>>>
>>>>>>> but still i just get 10 concurrent worker threads to my database....
>>>>>>> very strange.
>>>>>>>
>>>>>>> regards,
>>>>>>>
>>>>>>> mario.
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>

Mime
View raw message