Performance optimization is an area of concern in Tomcat that should be made better. I think the performance optimization has to be improved for monitoring, management of logs, load balancing, and containerization support. I think there is a need for some enhancement in the product's security as I work in my company's security area. If someone asks me about Tomcat from a performance perspective, I would say that tuning thread pools, caching, and compression needs improvement. In general, Tomcat should provide regular updates with respect to security.

I think Tomcat is a good and lightweight tool, but it needs improvement in areas like security and performance. Maybe a web application firewall or WAF products can be considered to protect the applications on websites, which is again some improvements needed from a security perspective. If you ask me about the feature and monitoring and management of logs, which are generally areas related to APM, needs improvement. Even the alerts provided by the tool need improvement.

Some simplified configurations and enhanced clustering can be considered for improvement in the product.

View full review »

Tomcat needs to improve its user interface. 

View full review »

If Tomcat could support the driver's VIN, they can run natively without the GBM. Now, we can run what we call the native cloud application that doesn't require GBM. If Tomcat can support that, it's going to improve performance and backup.

View full review »

Improvements could be made in the integration process of securing the Tomcat server within development environments like STS and SCS. The current procedure appears complex and could benefit from a more straightforward solution.

View full review »

Sometimes, the UI part does not run properly, or the server goes down.

View full review »

Suppose Tomcat is segregating its own version to utilize it in a testing area. It will be useful if a direct report concerning a particular server configuration or application usage is readily available in the dashboard.

View full review »

One way to improve the solution is by making the logging capabilities of Tomcat better by providing a logger within the server itself and making it easy to access and view the server logs. This can be especially useful when debugging issues with applications deployed on the Tomcat server. By having the ability to view both the application logs and the server logs, you can more easily identify the source of any issues and troubleshoot them more efficiently. Providing a connector or other similar feature that allows you to access the server logs from within your application can also be helpful in this regard. Having access to both the application logs and the server logs can be a valuable resource when trying to identify and resolve problems.

To make it easier to identify and troubleshoot issues, it can be helpful to have a single location where you can view both the application logs and the server logs together. This could include only the debug and error logs, rather than all logs, to make it easier to focus on potential issues. By having all relevant logs in one place, you can more easily scan for problems and identify their source, whether it is within the application or the server. This can save time and improve the efficiency of your troubleshooting efforts.

View full review »

Vulnerability is one of the areas that can be considered an issue in the solution. Apart from that, there are no other issues with the solution. Also, I cannot comment on what additional features and changes need to be made in Tomcat.

With the solution's community version, we always have some patches and bug releases. However, we cannot deploy it since the vendor doesn't certify the book fixes in the solution. In short, we cannot just use it in production and test it ourselves when the vendor does not certify it. If a vendor is using a Tomcat-based application, then the vendor should be prompt enough to fix the available bugs in that particular version, which is not the case in reality. Any vendor who releases a product on Tom Cat should keep revising the version of their product based on the latest available bug-free version. These are some of the areas which can be challenging for those using Tomcat.

View full review »

The solution cannot host .NET applications. 

View full review »

I've not used any other products in that space apart from the Apache versions. Having nothing to compare it to, it's hard to see what a weakness is. 

Some items may be vulnerable due to IT attacks or IT security breaches. If Apache can come up with a better solution to provide better security, that would be ideal. It is something that could be improved in both Apache and NICE Actimize.

View full review »

The solution should develop a better UI base in the Linux environment.

Tomcat has a Linux environment and is available as a CLI-based system.

View full review »

The setup is complex and could be improved.

View full review »

Tomcat is a polished product that has been around for a long time. It should be simple and high-performing, with the ability to grow and maintain stability. The fewer features it has, the more stable it will be.

Also, there could be more configuration options. It's always lovely to have finely tuned-configurations.

View full review »

The disability and memory management is a problem with the solution and has room for improvement.

I would like to have quicker Java application deployments.

View full review »

Sometimes we face issues with the private and public networks and ensuring that once Tomcat is installed, that it is secure. This is an area of the solution that could be improved, possibly by adding an additional package for security. 

View full review »

The product's pricing needs improvement.

View full review »

I would like to see the APM tools enhanced for all customers. Some APM customers are not yet fully integrated. I would also like to see a dashboard with some integrations in order to see the logs and trace performance easier.

View full review »

Tomcat needs to improve its stability. 

View full review »

Java has not been very good for some time in the middle, and then, again, they have improved. I have to ensure that the binary codes are compiled and set up correctly. I have to ensure the classes are done and the framework is correct. When I look at the classes, I need to be able to identify the entire framework correctly.

Therefore, I need to push it to the documentation framework, which will automatically take the software code and ensure the documentation is happening correctly. Java functions should be built better into the solution.

View full review »

Tomcat is not user-friendly. I would also like to be able to have multiple applications run at the same time.

In the next release, I would like to see better security features.

View full review »

Security integration in Tomcat is complicated. We need to use another tool to solve the security issues.

View full review »

I don't have too much experience with monitoring, however, it's possible it could be improved. It would be great if they offered more integration of monitoring tools.

The management maybe can be improved a bit. 

View full review »

The interface is not user-friendly.

You need to have knowledge of the operating system, and Linux to configure the solution. It is not user-friendly.

I would like to see a user-friendly interface.

View full review »

The stability must be improved.

View full review »

The solution's interface and backup features could be better.

View full review »

Tomcat's cache could be improved. Tomcat's performance is less than other solutions like IBM WebSphere or JBoss.

View full review »

This product needs an improvement to its centralized management console that can apply configurations and deployments for large scale clusters and groups of servers without the need of accessing each server to apply the changes. Also, it would be nice to have multiple profiles pre-configured for specific utilization, like other products in the market.

View full review »

Tomcat is used mainly for database connections. As of now, we configure that environment for any database configuration. But if any utility can integrate where we can pass the database connection as a string of details, then it should encrypt them and keep them inside. From that security perspective, Tomcat requires improvement. They should integrate this security feature.

View full review »

I would personally like it if the admin console would show more information specifically about memory being used.

View full review »

None that I can think of.

View full review »

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

View full review »

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

View full review »

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.

View full review »

The configuration needs work.

View full review »

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.

View full review »

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. View full review »

The high availability is not as robust as the competition is, such as WebLogic and Jboss.

At the moment, it is dependent on how Java is working. So if Java goes this way, then Apache Tomcat follows. Apache is very tightly coupled to Java. 

The question would more be where does Java need to be? Then Apache Tomcat will follow because it's Open-Source.

View full review »

Deployment automation needs some custom tooling. View full review »

The enterprise support: Tomcat is an open source project, but for IT concerns, the enterprise support is needed when we encounter problems on it.

View full review »

There are certain well known compatibility issues with some implementations of JDK Tomcat doesn't give you a performance like Apache when you have static HTML contents. And it is more suitable for hosting servlets and works best as a servlet container. Scalability is a major problem with Tomcat. When your application grows out of proportion and you have applications that draws heavy traffic, then Tomcat is not the right option and you might have to look for other options. View full review »