• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

servlet load issue

Ranch Hand
Posts: 111
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hello there , can you please help me with this:
my application is multitier application .
applets run at end user and all the execution report data is
appended in one string buffer , whenever applet is destroyed - all
this data is sent to "MYServlet" on the server , "MYServlet" parse
this data and according to given logic inserts figures in the
database. now can you please tell me that how should my servlet
be designed and what webserver and java application server should
i use to achive maximum scalability that it handles the report
parsing coming from massive number of end users at the same time running jdbc queires as well , i have implementd entire code of
my applets and the servlet "MYServlet" but i am worried about
whether this single servlet can handle big big number of end user
at any given time , is tomcat is fine for this (what is limitation of tomcat)
waiting for your reply.
thanks in advance.
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I can see the following subsections in your Question. My terse view on each follows.
Servlet design: Use of servlet chaining will help take the load off a single servlet holding huge functionality. Coupled it with the use the Controller concept of MVC design where the controller servlet handles the flow control. So the servlets could be sectioned into parser, businesslogic execution and dbaccess servlets (multitiered servlets!). Make sure that the servlet uses multithread model.DB connection pools are useful and implemented with most servers.
Web Server: Going around are Iplanet(expensive), Apache and IIS (not recommended).
App Server: weblogic, Jrun, IPlanet's app server.
Scalibility: These are scalable and suited to handle large no of hits.
Tomcat: Cannot comment about scalability.
ray bond
Ranch Hand
Posts: 111
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
thanks for reply pavitra ,
my servlet's main functionality is "parsing incoming data from applets and then inserting into database (not data but only update statements)." , i have already separated servlets to multipule so that single servlet do not take all the load , but can you please tell me that,
- should this servlet implement "SingleThreadModel" or not ?
- the methods which parse data and insert into database , should those methods be "synchronized" methods or not ?
- right now whenever servlet initialized , i open the database connection and the use that statment through out all the methods , is it good implementation for interaction with the database or not. ?
- there are multipule servlets for different data but they all perform same tasks , so when there are number of servlet , is tomcat is good enough to handle these many instances of servlets ,
- what is the limitation of tomcat , what is good option for tomcat for above requirments. ?
What could go wrong in a swell place like "The Evil Eye"? Or with this tiny ad?
Thread Boost feature
    Bookmark Topic Watch Topic
  • New Topic