Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 19901 invoked from network); 24 Mar 2008 10:33:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 24 Mar 2008 10:33:34 -0000 Received: (qmail 81689 invoked by uid 500); 24 Mar 2008 10:33:30 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 81664 invoked by uid 500); 24 Mar 2008 10:33:30 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 81653 invoked by uid 99); 24 Mar 2008 10:33:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Mar 2008 03:33:30 -0700 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mario.kofler@gmail.com designates 209.85.198.186 as permitted sender) Received: from [209.85.198.186] (HELO rv-out-0910.google.com) (209.85.198.186) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Mar 2008 10:32:50 +0000 Received: by rv-out-0910.google.com with SMTP id b22so1351312rvf.55 for ; Mon, 24 Mar 2008 03:33:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=x5f6oS/vfaRafw+DAwacIQUmC2qGoNWAOb6Lfl+/nBA=; b=ZE2c2SMwoLgr2mCuntO1Tiy+T0ld6gP4TiWHaizDFuBtI1v6JaGOQq+v55Ce27cy8b/G69jP4Xz/Aa0fuqvBsOIshAsOwfeR30C+aVd/WJ/r4vBSbXEitkqdhBLhUBn4FG271DyG79nZGIHRB3P4KHqQgxN2oeHl8g1/QyVZmNs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=rp3IHcCgyOnCrC74lTryO2jkwZ/UDqdKWaI7KiNqjCnhxj9LFq6TaWRVq4GDlMZfNFENvGW1e1vLr3HJcdPyFfMnRjzkLMYYn2+8WZY/5PRZAqIH2JrzWqtxSPcuENIWVNY2ra4x1xTspLo4r64QOPyw/35gcpKIaW9l6cky1w8= Received: by 10.141.190.9 with SMTP id s9mr1984380rvp.110.1206354781671; Mon, 24 Mar 2008 03:33:01 -0700 (PDT) Received: by 10.141.83.14 with HTTP; Mon, 24 Mar 2008 03:33:01 -0700 (PDT) Message-ID: <338462320803240333k7afe72d5yf2c09c1593559545@mail.gmail.com> Date: Mon, 24 Mar 2008 11:33:01 +0100 From: "Mario Kofler" To: user@geronimo.apache.org Subject: Re: MDB performance tuning, configuration In-Reply-To: <466797bd0803231115p7c3d15bfhb37712c58fc984c7@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_9485_13336396.1206354781643" References: <16234678.post@talk.nabble.com> <466797bd0803231115p7c3d15bfhb37712c58fc984c7@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_9485_13336396.1206354781643 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline hallo, it seems i completely messed up with my MDB application now. i tried the "activation spec" that you mentioned and it worked fine. then i thought ia lso try to set the InstanceLimit to 0. so i went to the config.xml file and changed the "MDB\ Container\ InstanceLimit=0" wrong thing to do. after that i did not receive the wanted updates anymore in the database. i increased the value again to "maxPool" size.. and since that at startup of the server or at deploy time i always realize that some messages are delivered but then it stops again. i dont even send messages anymore, the messages that are delivered are from a test 2 hours ago! i also tried to restart the database, restart the server, computer, everything. and tried to start with an empty db. the only thing i realize is that at startup or deploytime of my application it sends some 10 messages to the queue and after this it stops. by the way.. i already set the values back to their initial state.. but no effect.. i keep having this error and not possible to deliver any new messages.. just everytime i start i see more 10 values being changed in the database. can anyone help me, please. thanks, mario 2008/3/23, Manu George : > > You may have tried this out but increasing the maxMessagesPerSession > activation config property will increase the prefetch size and > generally speed it up a bit more. I assume u have already increased > the maxSessions activation config property to increase the no of > parallel Mdb instances. Here is a link for the properties that AMQ > allows http://activemq.apache.org/activation-spec-properties.html. The > configurable OpenEJB properties are given here > http://openejb.apache.org/example-generated-documentation.html. > > Try setting the InstanceLimit property of the MdbContainer to 0 so > that the no of instances created matches the no of AMQ sessions > available. For setting this you need to set this as a system property. > The property should be containerId.InstanceLimit where containerId is > of the format .- > > eg: org.apache.geronimo.configs/activemq-ra/2.2-SNAPSHOT/car.ActiveMQ > RA-javax.jms.MessageListener > > ie = artifactId of the jms RA > - The resource Group name u gave while creating the > RA > - javax.jms.MessageListener in this case > > So the property in this case can be set as > org.apache.geronimo.configs/activemq-ra/2.2-SNAPSHOT/car.ActiveMQ\ > RA-javax.jms.MessageListener.InstanceLimit=0 > > Regards > > Manu > > On Sun, Mar 23, 2008 at 4:49 PM, the666pack > wrote: > > > > hello, > > > > i am trying to test the performance of geronimo under load for message > > driven beans. the observed behaviour is that i get a maximum of about > 85 > > transactions per second. after this, tested with about 60 concurrent > users, > > the performance drops again to about 45 tps. i hoped to increase the > > performance somehow.. things i already tried: > > > > -increase the mdb pool size > > -increase the thread pool size > > -increase the connector-thread-pool-size > > > > unfortunately nothing helped, the performance situation remains the > same. > > > > another observed behaviour is that in the time of silence between tests > the > > server needs some time to fulfill the requests sent before. so i see it > is > > still working although i am not sending mdb-requests anymore. > > > > i suppose these are the requests that are still in the queue and have > to be > > finished. i think this is the reason for the performance drop with more > > concurrent users. i would like to see it perform without this > > "aftertime-working" and handle the requests "in time". > > > > maybe someone can give me a hint which other values could be important > to > > change for the performance of mdbs getting real good. i thank you very > much > > for your help, > > > > greetings, > > > > mario > > -- > > View this message in context: > http://www.nabble.com/MDB-performance-tuning%2C-configuration-tp16234678s134p16234678.html > > Sent from the Apache Geronimo - Users mailing list archive at > Nabble.com. > > > > > ------=_Part_9485_13336396.1206354781643 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline hallo,

it seems i completely messed up with my MDB application now. i tried the "activation spec" that you mentioned and it worked fine. then i thought ia lso try to set the InstanceLimit to 0. so i went to the config.xml file and changed the "MDB\ Container\ InstanceLimit=0" wrong thing to do. after that i did not receive the wanted updates anymore in the database. i increased the value again to "maxPool" size.. and since that at startup of the server or at deploy time i always realize that some messages are delivered but then it stops again. i dont even send messages anymore, the messages that are delivered are from a test 2 hours ago!

i also tried to restart the database, restart the server, computer, everything. and tried to start with an empty db. the only thing i realize is that at startup or deploytime of my application it sends some 10 messages to the queue and after this it stops.

by the way.. i already set the values back to their initial state.. but no effect.. i keep having this error and not possible to deliver any new messages.. just everytime i start i see more 10 values being changed in the database.

can anyone help me, please.

thanks,

mario

2008/3/23, Manu George <manu.t.george@gmail.com>:
You may have tried this out but increasing the maxMessagesPerSession
activation config property will increase the prefetch size and
generally speed it up a bit more. I assume u have already increased
the maxSessions activation config property to increase the no of
parallel Mdb instances. Here is a link for the properties that AMQ
allows http://activemq.apache.org/activation-spec-properties.html. The
configurable OpenEJB properties are given here
http://openejb.apache.org/example-generated-documentation.html.

Try setting the InstanceLimit property of the MdbContainer to 0 so
that the no of instances created matches the no of AMQ sessions
available. For setting this you need to set this as a system property.
The property should be containerId.InstanceLimit where containerId is
of the format  <artifactId>.<Resource Group Name>-<listener interface>

eg: org.apache.geronimo.configs/activemq-ra/2.2-SNAPSHOT/car.ActiveMQ
RA-javax.jms.MessageListener

ie <artifactId> =  artifactId of the jms RA
<Resource Group Name> - The resource Group name u gave while creating the RA
<listener interface> - javax.jms.MessageListener in this case

So the property in this case can be set as
org.apache.geronimo.configs/activemq-ra/2.2-SNAPSHOT/car.ActiveMQ\
RA-javax.jms.MessageListener.InstanceLimit=0

Regards

Manu

On Sun, Mar 23, 2008 at 4:49 PM, the666pack <mario.kofler@gmail.com> wrote:
>
>  hello,
>
>  i am trying to test the performance of geronimo under load for message
>  driven beans. the observed behaviour is that i get a maximum of about 85
>  transactions per second. after this, tested with about 60 concurrent users,
>  the performance drops again to about 45 tps. i hoped to increase the
>  performance somehow.. things i already tried:
>
>  -increase the mdb pool size
>  -increase the thread pool size
>  -increase the connector-thread-pool-size
>
>  unfortunately nothing helped, the performance situation remains the same.
>
>  another observed behaviour is that in the time of silence between tests the
>  server needs some time to fulfill the requests sent before. so i see it is
>  still working although i am not sending mdb-requests anymore.
>
>  i suppose these are the requests that are still in the queue and have to be
>  finished. i think this is the reason for the performance drop with more
>  concurrent users. i would like to see it perform without this
>  "aftertime-working" and handle the requests "in time".
>
>  maybe someone can give me a hint which other values could be important to
>  change for the performance of mdbs getting real good. i thank you very much
>  for your help,
>
>  greetings,
>
>  mario
>  --
>  View this message in context: http://www.nabble.com/MDB-performance-tuning%2C-configuration-tp16234678s134p16234678.html
>  Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
>
>

------=_Part_9485_13336396.1206354781643--