Tomcat Reviews

It's a rock solid Java host.

It is at the core of our production application server environment.

None that I can think of.

I've been using it for 10 years,

No, it's rock solid.

The server needs to be bounced every three months. We reboot on schedule whether we need to or not.

No issues encountered.

Customer Service:

It's open source and the community is very helpful.

Technical Support:

It's open source and the community is very helpful.

We used IBM WebSphere, but the cost drove us to Tomcat.

It's drop dead easy.

We did it all in-house.

No investment, and a huge return.

We bounce the servers every three months, but other than that the costs are trivial.

We looked at other products from IBM, Sun, BEA and a couple others.

Do it. Drop it in and if you have huge traffic requirements, drop it on a couple of machines and run a network balancer.

• Simplicity
• Speed of deployment

• It allows rapid application deployment for Java web container applications.
• It provides a stable platform for the application to work with.

• The documentation can be better.
• It also lacks the flexibility to configure files.
• Clustering is complicated.

I managed it for approximately three years.

No issues encountered.

No issues encountered.

It's difficult to scale/cluster.

It was straightforward.

• Lightweight
• Configurable
• High-performance
• Cross-platform
• Open source 
• It has sufficient documentation for application development

The cluster management and load balancing is a bit complex. Also, they need to improve the documentation to handle JNDI resources.

I've used it for 10 years.

Deployment is simple, however, a limitation is hot deployment.

No issues encountered.

No costs.

If you were to have no JEE applications, then it is advisable, otherwise the application server falls short.

We use this solution as a web application server.

It provides website hosting services.

The most valuable features of this solution are the general web server features.

It's simple and easy to use.

In terms of features, this solution is limited. It does do its job, but the enterprise-level features are missing.

In the next release, I would like to see better maintenance and administration utilities. For example, they could be simplified.

I have been using Tomcat for three years.

We are using the latest version. It is always updating.

It's a pretty stable solution.

This solution is actively being used.

Technical support is limited. We don't get very many issues, but when we do, the service is not very straightforward.

It was a default install and it was done before I arrived.

We used a vendor for the deployment.

My advice Look at all the options of server hosting before choosing Tomcat.

I would rate Tomcat a seven out of ten.

Public Cloud

It has a small footprint.

With this, we were able to deliver our products faster to our customers through packaging.

The configuration needs work.

I've used it for six months.

No issues encountered.

This depends on the load of the server. We had no issues, but we never ran more than application/site at a time.

No issues encountered.

Customer Service:

I've not used customer service.

Technical Support:

I've not used technical support.

We switched because of the nature of the application and technology.

I always design my systems simple and keep them simple as possible.

We implemented it with in-house team. We like to keep the knowledge in-house.

It was crucial and it definitely paid off.

Keep the systems simple. Try to work with open-source solutions and pay for technical support and subscription to support the projects.

Yes I always and regularly evaluate. In case of Java we evaluated all Applications servers who support JEE full profile.

I was using Apache Tomcat, JBoss AS (RedHat), WebMethods (Software AG) and IIS (Microsoft). All of them have their specialities, but depending on the goals and purpose it’s quiet easy to make a choice. Products based on Microsoft .NET do not give companies lot of options; either with Server Operating System shipped IIS, or the developer version called IIS Express. Applications written in Java, n opposite, can be accommodated on several fully-profiled or non-fully-profiled application or web servers.

Only have one application per server if possible. Do not over complicate it, and keep the variance in the configuration simple as possible.

We are using this solution because of the Oracle REST data services we are using.

The most valuable feature is the free EE server.

In the solution, we are using the terminal to enter command line codes for operations and management, this is difficult for me. It would be better if we had some administrator UI tools for this.

I have been using the solution within the last 12 months.

The solution is reliable.

We have approximately five people using the solution in my organization.

The initial setup is easy. However, we did have some difficulties at first that we managed to resolve. There is plenty of documentation online to help with the solution.

We did the implementation of the solution.

The solution is free.

I would recommend this solution to others.

I rate Tomcat an eight out of ten.

On-premises

Apache Tomcat has become almost the defacto server for serving Java-based applications on the internet. We use Tomcat for our Java web applications and just recently also for our Android software development classes.We chose Tomcat as it was the most widely-used Java web application programming server at that time. Also, most of our resources were tailored to work with Tomcat, and our colleagues who underwent Java web application development was also taught using Tomcat.Features-wise, it's a complete solution. Plus, a lot of other developers are also using it, and the project has been steadily supported by Apache.

The main gripe that I have with Tomcat is it's speed and size. Understandably, Java-based systems have the pre-conceived notion of being slow. However, being exposed to other web servers like the Apache web server really makes you wish Tomcat is as fast as it is. It does take time to load even on current hardware and newly-deployed applications also tend to load slowly during first access.Another grip is size. Size in terms of its memory usage and its installation. Again, compared to Apache, Tomcat really takes-up a lot of memory resources. As a rule of thumb, you need to have a lot of memory on the server which will run Tomcat. Installation size is also big, and it can take a while to download the installation package.

Overall, Tomcat is still a recommended product for use with Java web application development and Android application development. Though it has speed and size issues, it's still the most widely-used development web server for Java and Android web and application development. Just make sure you have a server that has more than enough memory if you use Tomcat, as it tends to use a lot of it.

- JSP/Servlet container

- Realm database for role and user management

10 years

Out-of-Memory issues, which can be solved by increasing the heap space.

Tomcat is a simple JSP/JSF container, but if you want to host J2EE applications you must switch to other solutions, such as JBOSS or Oracle Web Logic.

In-house

Tomcat is free and opensource.