Monday June 02, 2003
Tomcat/Oracle Connectivity Problems I had a problem that I thought I fixed a while back. The problem was that our firewall between Tomcat and Oracle would close our database connection after 90 minutes of inactivity. We first solved this problem by using a Servlet/Ant Task/cron job combination to ping and use the DBCP connection pool we'd configured in Tomcat. This worked, for a little while. Then we realized we had to also ping the JDBCRealm, so we used a login test (via WebTest) and added this to our Ant Task/cron job. Again, this worked for a couple of months, until a QA Expert came on board and starting using WAPT to load test our app. Then we began having issues with many connections being opened (20+), then they were closed by the firewall, and when the app would try to re-use these connections, they wouldn't respond, and the app would enter into the "dithering idiot" mode. We finally figured out a solution, rather than workarounds, and here it is:
// In the file: $ORACLE_HOME/network/Admin/SQLNET.ORA // Add the following line to check every 10 minutes SQLNET.EXPIRE_TIME=10
Posted in Java at Jun 02 2003, 09:25:58 AM MDT Add a Comment
Search This Site
Recent Entries
- My TSSJS 2010 Presentations and Summary
- What's New in Spring 3.0
- Developing Rich Web Service APIs with Java
- C++, Java and .NET: Lessons Learned from the Internet Age
- Highly Interactive Software with Java and Flex
- The Cloud Computing Continuum with Bob McWhirter
- Software Quality: The Quest for the Holy Grail?
- What's Happening in the Java World?
- Fantastic Fun in Jackson Hole
- How We Hired a Team of 10 in 2 Months