Mailing-List: contact users-help@mina.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@mina.apache.org
Received-SPF: pass (nike.apache.org: domain of paliwalashish@gmail.com
 designates 74.125.82.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=hJ0OJtvenuvxaNJ/7EU/BvgoH46sWgnbn3Z4qjz+JQXMGEhVzgiogxOZ7OTsrSmQoh
         rFl1KO7EoB9jeyAzM7IhwMYhemfKNwZ6CjuuS3rPpBAUTKpaW94Wm9YDq+JliwRW12XW
         1J1hqdcYXBhu1ndbrYAU4KAwetN1uGJ8RL3EA=
MIME-Version: 1.0
In-Reply-To: <AANLkTi=s-Q5nm067Wj_2zB2UKGMpi7Dsi+qSE39y2vkh@mail.gmail.com>
References: <AANLkTi=F4yYkE-WWYBoQFROMq=Ep8Xb271Qnr+95YGjM@mail.gmail.com>
	<AANLkTi=d+44ZYjq=5BOQZ_uT21SrjecuoaeHoiieP_6P@mail.gmail.com>
	<AANLkTikw6wBmSa1sdhmueeGeG53FP0TxsGS=oiQQR5gk@mail.gmail.com>
	<4C9764C6.9050208@gmail.com>
	<AANLkTi=xWMOChGbg3tL8b5VBAp6yxeSFqqF8iAy-3A_j@mail.gmail.com>
	<4C976A55.5070608@apache.org>
	<AANLkTi=Uuqw+grOPz6qKbMyY0bgOyEMk0aJ98V2KKiQP@mail.gmail.com>
	<AANLkTi=xWE0HHCoJHmi8Gk67YGsagD2r2mp4SFuQW1xy@mail.gmail.com>
	<AANLkTi=s-Q5nm067Wj_2zB2UKGMpi7Dsi+qSE39y2vkh@mail.gmail.com>
Date: Mon, 20 Sep 2010 22:30:01 +0530
Message-ID: <AANLkTinqvi4AkqPpxKa=tEmLK=PvUOzt66wmFgNH32XS@mail.gmail.com>
Subject: Re: MINA performance on Centos/Tomcat
From: Ashish <paliwalashish@gmail.com>
To: users@mina.apache.org
Cc: elecharny@apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Sep 20, 2010 at 10:18 PM, Kumar Abhishek <kumabhi@gmail.com> wrote:
> Thanks for the kind reply. A quick update on why I didn't go for doing this
> in Servlets is the smpp server needs to be continuously binded to smsc, this
> calls for background thread execution in tomcat which I didn't think to be a
> good idea. Also, poor console based monitoring of smsc binded process if
> tomcat is the front-end ;)
> Also, you are very right about separation of concerns thing, that was the
> very idea behind this architecture, to move the http g/w around and possibly
> replicate as well on demand :)
> Any inputs on what tomcat settings can be played around with?

You could use context listeners for starting/stopping Threads, not
necessary in servlets.
Add JMX support and you should be good for monitoring.

Touch tomcat setting only if its an hurting ur app. Best is look
what's eating up CPU?
1. Something is eating the CPU, find out what it is
2. For Tomcat, tune Threads in server.xml, removed unused context and
other stuff. If possible use tcnative to give an extra dose of power.
    At this moment leave it untouched. Might come in handy later on.
3. Keep ur eye open to GC

Well these are all wild guesses. First thing is to get info out of
your system and analyze what's going on.

This is ALL I can help without Thread dumps.

thanks
ashish