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?
On Mon, Sep 20, 2010 at 9:14 PM, Ashish <[email protected]> wrote: > Couple of things > 1. Plan to upgrade to MINA 2.0 once its out in a few days.. 1.1.7 is way > old > 2. For immediate action, try a few thread dumps and see why CPU is so > high, prob u have too many CPU bound task > 3. Try tweaking Tomcat setting, after giving a look at your Thread dumps. > > About Architecture, its tough to give an opinion without knowing all > System constraints. This is very beneficial if you have > many HTTP front-ends accepting requests and posting to a single Server > acting as your HTTP-SMPP gateway. The good part > of this architecture is you can easily move to multiple machines, add > more http front-ends without code change :) > On the other hand, if you never intend to work it that ways, its an > overkill. Better do this in Servlet. > AFAIK, you would using one of SMPP lib's (Logica SMPP/jsmpp/opensms) > for sending message to SMSC in your MINA IO Handler. > > I definitely don't like running client and Server on the same machine > in production for sure. Single machine, Single point of failure. > Again this is very specific to what you need. If it works fine for > you, probably that's what u need. > > Good Luck! > > - ashish > > > On Mon, Sep 20, 2010 at 7:34 PM, Kumar Abhishek <[email protected]> wrote: > > okies, will give it a shot tonite when traffic is minimal :) > > Any comments on the architecture I am using for the client server > > communication, is it a good design to have tomcat act as http > > interface(backed by client connectors) and socket server accepting http > > requests from client to fire smpp sms sending requests > > > > On Mon, Sep 20, 2010 at 7:36 PM, Emmanuel Lécharny <[email protected] > >wrote: > > > >> On 9/20/10 3:39 PM, Kumar Abhishek wrote: > >> > >>> On Mon, Sep 20, 2010 at 7:12 PM, Emmanuel Lecharny<[email protected] > >>> >wrote: > >>> > >>> On 9/20/10 3:02 PM, Kumar Abhishek wrote: > >>>> > >>>> 2 CPUs of the following configuration(Intel Dual Core XEON Processor > 3.3 > >>>>> Ghz > >>>>> ) > >>>>> > >>>>> Using thread dump on tomcat java process is a bit risky for us as it > >>>>> will > >>>>> bring down all our web services. > >>>>> > >>>>> Kill -3 bringing down services ??? How possible ? > >>>> > >>>> yes because java of tomcat is running in background > >>> > >> > >> Should not harm. It just get a thread dump, it does nothing else, > AFAIK... > >> > >> Which Java version are you using ? >
