The Apache Tomcat team announces the immediate availability of Apache Tomcat 7.0.35.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Apache Tomcat is an open source software implementation of the Java Servlet and JavaServer Pages technologies.
This release contains a small number of bug fixes and improvements compared to version 7.0.34. The notable changes include:
The Apache Tomcat team announces the immediate availability of Apache Tomcat 7.0.34.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Apache Tomcat is an open source software implementation of the Java Servlet and JavaServer Pages technologies.
This release contains a small number of bug fixes and improvements compared to version 7.0.33. The notable changes include:
The Tomcat Expert community is a project sponsored by VMware SpringSource aimed to help improve enterprise adoption of Apache Tomcat. Over the past two years, we’ve put out nearly a hundred unique articles from our pool of experts to help users understand more about how Tomcat works and how you can use it more effectively to power business critical applications. We’ve covered new functionality in Tomcat 7, including posts on the jdbc-pool, parallel deployment, and the WebSocket implementation. We have also covered a number of other common questions ranging from the basic "Is Apache Tomcat an App Server?" to the detailed "How do I decide between mod_jk, mod_proxy_http, and mod_proxy_ajp?".
A new question we are hoping to answer for our community is, “How can I find quality candidates to help on my Tomcat deployment?” – and we aim to do this by offering the ability for employers to post available tomcat jobs, as well as the ability for members to find jobs and to apply for them directly from our community site.
Users will need to create a login account in order to access the job posting form. Users can post an unlimited number of jobs, however until a job poster earns enough karma, each job will need to be approved by a tomcatexpert administrators to ensure the job feed is filled with quality jobs. Jobs should be related directly to the configuration, management and operation of Apache Tomcat; however, the roles can go beyond the traditional system administration and web operations roles to include java or Spring developers, instructors, technical sales engineers, and software product or architect roles that depend on Apache Tomcat. Employers have the option to have TomcatExpert email candidate submissions which include links to the candidate’s TomcatExpert profile, or to be redirected to your company’s submission process.
EMC Consulting is hosting a customer facing webinar covering heavyweight to tcServer migration. The objective is to drive vFabric product and joint service revenue.
Migrating Java applications from Websphere or Weblogic to vFabric TC Server helps IT to reduce the cost and complexity of applications. Bruce Snyder will share best practices and use real life examples to explain how to transform your applications quickly and easily. Learn More/Register Now
I have observed the tomcat 7 process memory (private bytes) was initially 1.2 GB during startup and it got increased to 3.5 GB where my server RAM size is only 4GB after running a 100 users test for 4 hours. this private bytes was not released even after stopping the test. could you please let us know any configurations that might help this or kindly analyze the situation and provide your suggestions/solutions.
Regards,
Raga
Lacking more specific about the behavior that you are seeing and about the environment that you are using to run your tests, and since this is a testing environment, my suggestion to you would be to run your tests while you have a profiler hooked up to Tomcat (YourKit is an excellent profiler). The profiler will allow you to look for memory problems in your application.
That's not to say there is definitely a problem here. It is entirely possible that you could see the heap grow from 1.2 G to 3.5G legitimately. It just depends on your JVM options and the memory demands of your application.
2011 has been a great year for the Tomcat Expert community. After almost 2 years of operating, the Tomcat Expert has hit its stride, unloading an array of new information, as well as keeping you up to date with the newest releases for Apache Tomcat 6 and Apache Tomcat 7. With the addition of two new Tomcat Expert Contributors, (Channing Benson and Daniel Mikusa), the Tomcat Expert community continues to build on its reputation for being the leading source for fresh perspectives and new information on how to best leverage Apache Tomcat in the enterprise.
Hi all,
Our system is 32 bit Windows 2003 server. We have increased java heap size to max value for 32 bit OS. But we still need much more RAM for Tomcat server. Is there a way to decrease used memory or increase memory?
Thanx
The simplest solution is to upgrade to a 64-bit OS. That will allow the OS to address more memory and it will allow you to run a 64-bit JVM, which can then take advantage of the additional memory addressable by the OS.
If you are stuck running a 32-bit OS then you're limited by two factors: the amount of memory addressable by your OS and by the amount of memory addressable by a 32-bit JVM. Some operating systems will allow you to work around the first limitation by enabling PAE [1], however there is no way to work around the second limitation.
The technical limit for a 32-bit JVM is 4G (i.e. 2^32 bytes), however the actual amount of memory that can be used by a 32-bit JVM is going to be less than that. There are several factors which will limit the amount of memory available (such as OS usage, OS per processor limits and JVM non-heap usage). In practice, I've seen people report getting anywhere from 1.5 to 2.5G for a max heap size (-Xmx).
Having said that, you can see that it is possible for you to increase the available heap space by doing things like reducing the amount of memory consumed by the OS. However if you already have a large heap allocated to your application, it is not likely that you'll be able to increase the heap size very much (since you'd have to take it from somewhere else).
If you need to significantly increase the heap size then the only viable solution is to upgrade to a 64-bit operating system.
[1] - https://en.wikipedia.org/wiki/Physical_Address_Extension
Announced this morning by the Apache Tomcat team:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Apache Tomcat team announces the immediate availability of Apache Tomcat 6.0.33 stable.
Apache Tomcat 6.0.33 is primarily a security and bug fix release. All users of older versions of the Tomcat 6.0 family should upgrade to 6.0.33.
Note that is version has 4 zip binaries: a generic one and three bundled with Tomcat native binaries for different CPU architectures.
Apache Tomcat 6.0 includes new features over Apache Tomcat 5.5, including support for the new Servlet 2.5 and JSP 2.1 specifications, a refactored clustering implementation, advanced IO features, and improvements in memory usage.
Please refer to the change log for the list of changes:
http://tomcat.apache.org/tomcat-6.0-doc/changelog.html
Downloads:
http://tomcat.apache.org/download-60.cgi
Migration guide from Apache Tomcat 5.5.x:
http://tomcat.apache.org/migration.html
Thank you,
-- The Apache Tomcat Team
Announced this morning by the Apache Tomcat team:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Apache Tomcat team announces the immediate availability of Apache Tomcat 7.0.20
Apache Tomcat 7.0.20 includes bug fixes and the following new features compared to version 7.0.19:
Please refer to the change log for the complete list of changes: http://tomcat.apache.org/tomcat-7.0-doc/changelog.html
Note that this version has 4 zip binaries: a generic one and three bundled with Tomcat native binaries for Windows operating systems running on different CPU architectures.
Downloads: http://tomcat.apache.org/download-70.cgi
Migration guide from Apache Tomcat 5.5.x and 6.0.x: http://tomcat.apache.org/migration.html
Thank you,
-- The Apache Tomcat Team
Announced this morning by the Apache Tomcat team:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Apache Tomcat team announces that support for Apache Tomcat 5.5.x will end on 30 September 2012.
This means that after 30 September 2012:
Three months later (i.e. after 31 December 2012)
Note that all 5.5.x releases will always be available from the archive.
It is anticipated that the final 5.5.x release will be made shortly before 30 September 2012.
Thank you,
-- The Apache Tomcat Team
Popular Links