The Apache Tomcat team announces the immediate availability of Apache Tomcat 7.0.32.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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.30. The notable changes include:
Please refer to the change log for the complete list of changes:
http://tomcat.apache.org/tomcat-7.0-doc/changelog.html
Note: 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.
Note: If you use the APR/native AJP or HTTP connector you *must* upgrade to version 1.1.24 or later of the AJP/native library
Downloads:
http://tomcat.apache.org/download-70.cgi
Migration guides from Apache Tomcat 5.5.x and 6.0.x:
http://tomcat.apache.org/migration.html
Thank you,
-- The Apache Tomcat Team
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Register for the tomcat-announce email list to receive Apache announcements directly.
Popular Links
Comments
Server failed to resume the transaction: Desc:430000000d.
We have just upgraded our development enviroment to Following:
The environment on this server is:
MS SQL Server 2008 R2
NetBeans 7.2
JDK 1.7.7
Tomcat 7.0.30
Latest SQL JDBC 4 drivers.
Latest Java Mail API.
For all the projects, source code project property is now updated to java 1.7 and source code is recompiled under JDK 1.7
Other configuration changes under this environment are:
Commons-dbcp connection is now changed with Tomcat database connection pool
The database connection pool JNDI resources are now moved form application level to server level. So, there would be only 2 central database connection pools which would be shared by all the applications host on an instance of Tomcat. In the earlier configuration all the application hosted on the instance of Tomcat use to maintain individual database connection pools.
Now The problem is:
sometimes when we execute procedures which contain statement like begin transaction and commit transaction then it throws "server resume to failed the transaction, Now for testing when i removed begin transaction and end transaction and use only begin and end, it works fine.
Also when i used dbcp instead of jdbc connection pools it works fine.
Nayan
Post new comment