• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Clients on Tomcat 3.3

 
Ranch Hand
Posts: 36
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all,
I'm planning to develop a client-server application and host it on Tomcat 3.3
There will be a maximum of about 100 clients connected to the server at the same time. Does Tomcat support this number of clients at the same time? If not what server can I use to implement my project?
Thanks in advance.
Ahmed.
 
Ranch Hand
Posts: 2676
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
This question is more appropriate for the Apache/Tomcat forum. I will move it there for you.
Matthew Phillips
 
Saloon Keeper
Posts: 27752
196
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
"connected" is a dangerous term. Since HTTP is a transactional protocol, you won't be consuming large amounts of network resources unless you have big data transfers and/or lots of concurrent activity, where the network bandwidth and CPU are likely to be the limiting factor.
Of course, one type of "connection" is the server-side session information, which may be anything from nothing to huge (well, try to avoid huge), depending on your design. It's always best to keep this light, in which case 100 of them isn't likely to be a problem.
There are no hard-coded limits in Tomcat for most of this, except for things like maximum simultaneous connections (NOT session connections - we're talking actual in-progress HTTP requests), sizes of resource pools, and such, which are used mostly for tuning.
Whether 100 users is a burden depends on your server and the way the app is written. It's not a bad idea to set up some benchmarks and stress tests.
 
If you believe you can tell me what to think, I believe I can tell you where to go. Go read this tiny ad!
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic