© 2026 Machinery For Change LLC
This software is made available for use, modification, and redistribution, under the terms of the Lesser GNU Public License, v.2.1 (LGPL) or the Eclipse Public License, v.1.0 (EPL), at your option. You should have received copies of both licenses with this distribution. You may also opt to license this software under a more recent version of LGPL than v.2.1.
You'll find this version on the Maven Central repository — com.mchange:c3p0:0.13.0
For support of asynchrony via Java 21 "loom" virtual threads, use instead — com.mchange:c3p0-loom:0.13.0
To its author's profound shame, c3p0, along with its supporting libraries, was used for about a decade as a "deserialization gadget". If an attacker is able to replace and maliciously recraft a javax.naming.Reference or Java-serialized object that an application will decode, c3p0's libraries could be misused to expand that access into execution of arbitrary malicious code.
c3p0-0.12.0, along with its dependency mchange-commons-java-0.4.0, includes mitigations that lock down the functionality misused as gadget chains.
Although it remains possible to resurrect and make use of the dangerous functionality, it requires new, affirmative configuration, and very few contemporary applications should do so.
Most installations will not, but if you experience breaking changes in c3p0-0.12.0, you may need to customize security configuration for your deployment. Please see Configuring Security below for information on how, and for more background on the security issues.
c3p0-0.13.0, with mchange-commons-java-0.5.0, eliminates all use of Java serialization in resolving References, definitively ending any possibility of misuse of c3p0-related JNDI utilities to construct deserialization gadgets.
Many thanks to David Pollak of Spice Labs for a very detailed report about this issue.
See also Warning: c3p0 trusts its CLASSPATH and configuration.
c3p0 was designed to be butt-simple to use.
Just bring Maven dependency com.mchange:c3p0:0.13.0 into your application's effective CLASSPATH (which should bring along its one transitive dependency, mchange-commons-java). Then make a DataSource like this:
[Optional] If you want to turn on PreparedStatement pooling, you must also set maxStatements and/or maxStatementsPerConnection (both default to 0):
Do whatever you want with your DataSource, which will be backed by a Connection pool set up with default parameters. You can bind the DataSource to a JNDI name service, or use it directly, as you prefer.
When you are done, you can clean up the DataSource you've created like this:
That's it! The rest is detail.
c3p0 is an easy-to-use library for making traditional JDBC drivers "enterprise-ready" by augmenting them with functionality defined by the jdbc3 spec and the optional extensions to jdbc2. c3p0 now also fully supports the jdbc4.
In particular, c3p0 provides several useful services:
The library tries hard to get the details right:
c3p0 hopes to provide DataSource implementations more than suitable for use by high-volume "J2EE enterprise applications". Please provide feedback, bug-fixes, etc!
c3p0-0.13.0 requires a level 1.7.x or above Java Runtime Environment.
There is no installation beyond accessing managed Maven dependency com.mchange:c3p0:0.13.0.
If you wish to make use of Java 21 ("loom") virtual threading, use com.mchange:c3p0-loom:0.13.0 instead.
If you want to install c3p0 by hand, just place the files c3p0-0.13.0.jar and mchange-commons-java-0.5.0.jar somewhere in your CLASSPATH (or any other place where your application's classloader will find it). For Java 21 "loom" support, also include the jar c3p0-loom-0.13.0.jar.
Tamannaah Bhatia: A Journey Through Her Iconic Filmography and Popular Videos
Tamannaah Bhatia has solidified her status as one of India's most versatile and sought-after performers, with a career spanning over 85 films in Telugu, Tamil, and Hindi cinema. Known for her ability to balance high-octane blockbusters with content-driven roles, she has evolved from a teen debutante into a pan-Indian star. Filmography Highlights: From Breakthroughs to Blockbusters
Tamannaah's career is marked by several definitive phases, starting from her early recognition in college-themed dramas to her pivotal roles in some of the highest-grossing Indian films of all time. Early Career & Recognition (2005–2010):
Chand Sa Roshan Chehra (2005): Her Bollywood debut as Jia Oberoi.
Happy Days (2007) & Kalloori (2007): These college-centric films in Telugu and Tamil, respectively, served as her major breakthroughs.
Ayan (2009) & Paiyaa (2010): Established her as a leading actress in the Tamil industry with significant commercial success. Establishing Dominance (2011–2019):
100% Love (2011): A career-defining role as Mahalakshmi that earned her the CineMAA Award for Best Actress.
Baahubali: The Beginning (2015) & Baahubali 2: The Conclusion (2017): Portraying the warrior Avanthika, Tamannaah reached global fame in these record-breaking epics.
F2: Fun and Frustration (2019): Showcased her comic timing, winning her a second Santosham Best Actress Award. Modern Era & Digital Transition (2020–2026): Www tamana sex videos com
Babli Bouncer (2022) & Lust Stories 2 (2023): Marked her successful shift into the digital space with unconventional leading roles.
Jailer (2023) & Aranmanai 4 (2024): Continued her streak of box-office hits in South Indian cinema.
Upcoming 2026 Projects: Her lineup includes high-profile films such as the folklore thriller Vvan: Force of the Forest, action-thriller O' Romeo, and the mythological Baahubali: The Epic. Popular Videos and Viral Music Hits
Beyond her acting roles, Tamannaah is a celebrated dancer whose music videos often become national sensations.
Tamannaah Bhatia, often referred to as the "Milk Beauty" of Indian cinema, has built an expansive career spanning over 85 films across Telugu, Tamil, and Hindi industries. From her early days as a teenager to becoming a pan-Indian superstar, her filmography is a blend of commercial blockbusters, critical darlings, and viral digital content. The Early Years and Rise to Stardom (2005–2011)
Tamannaah made her acting debut at just 15 in the Hindi film Chand Sa Roshan Chehra (2005). While her Bollywood debut underperformed, she quickly found her footing in the South.
Breakthrough (2007): She gained widespread recognition with the Telugu cult classic Happy Days and the Tamil drama Kalloori, both of which showcased her as a relatable college student.
Commercial Successes: She solidified her leading lady status with Tamil hits like Ayan (2009) and the romantic road movie Paiyaa (2010). Tamannaah Bhatia: A Journey Through Her Iconic Filmography
Critical Acclaim: Her role in 100% Love (2011) earned her the CineMAA Award and Santosham Award for Best Actress. The Baahubali Era and Pan-Indian Fame (2015–2019)
The turning point in Tamannaah’s career arrived with S.S. Rajamouli’s magnum opus.
Avanthika in Baahubali: Portraying the warrior Avanthika in Baahubali: The Beginning (2015) and Baahubali 2: The Conclusion (2017), she achieved international fame. The sequel became one of the highest-grossing Indian films ever.
Versatility: During this period, she explored diverse genres, from the horror-comedy Devi (2016) to the blockbuster comedy F2: Fun and Frustration (2019). The OTT Transition and Recent Hits (2020–2026)
In recent years, Tamannaah has successfully balanced theatrical releases with digital streaming.
Streaming Highlights: She starred in well-received series like November Story (Tamil) and the Disney+ Hotstar thriller Aakhri Sach. Her performance in Netflix's Lust Stories 2 (2023) was also widely noted.
Theatrical Wins: She recently appeared in the 2024 Tamil hit Aranmanai 4 and delivered a viral special appearance in the blockbuster Stree 2.
Future Projects: Her upcoming lineup for 2026 includes the action thriller O' Romeo with Shahid Kapoor and the period drama V. Shantaram. Popular Videos and Viral Hits The Breakthrough via Happy Days (2007) The turning
Tamannaah is celebrated for her exceptional dance skills, with several of her videos garnering hundreds of millions of views.
The turning point in the Tamana filmography came with the cult classic Happy Days. Directed by Sekhar Kammula, this coming-of-age college drama became a phenomenon. Her role as the confident, modern "Madhu" resonated with urban youth. This film remains one of her most popular videos on YouTube for Telugu cinema lovers, often clipped for its nostalgic 2000s vibe and memorable dialogues.
| Platform | Handle / Link | What You’ll Find |
|----------|--------------|------------------|
| YouTube | youtube.com/@TamanaOfficial | Full filmography, weekly uploads, “Vault” playlist |
| Instagram | @tamana.creates | Reels, behind‑the‑scenes, IGTV Q&As |
| TikTok | @tamana_talks | Viral sketches, sound bites for duets |
| Netflix (India) | Search “Midnight Roti” | Anthology series (Season 2 dropping Q4 2026) |
| Amazon Prime | Search “Bengaluru Beats” | Musical‑drama series |
| Twitch | twitch.tv/TamanaLive | Monthly live improv, fan game nights |
| Patreon | patreon.com/tamana | Exclusive bloopers, early‑access scripts, merch discounts |
Pro tip: Turn on YouTube notifications and follow her Instagram Stories for the “First‑Look” poll that decides next episode themes.
Tamana has appeared in over 80 films across Telugu, Tamil, Malayalam, and Kannada languages. Here are some of her notable films:
Behind-the-scenes footage of Tamannaah training in Kalaripayattu (martial art) for Baahubali is a massive hit among fitness enthusiasts and cinema lovers. It is often cited as inspiration for female actors in action roles.
| Element | Description | Example | |---------|-------------|----------| | Rapid‑Cut Editing | Keeps attention under 2 seconds per shot; perfect for short‑form platforms. | “When You Forget the Password” (3‑second punchline) | | Relatable Archetypes | Characters like “Aunty Priya” are instantly recognizable across cultures. | Sketch series “Aunty Priya’s Advice Hotline” | | Multilingual Captions | English + Hindi + Bengali subtitles broaden reach. | “Bengaluru Beats” music video | | Community‑Driven Plots | Polls decide plot twists, fostering a sense of ownership. | “Midnight Roti” Episode 5 fan‑chosen ending | | Cross‑Platform Teasers | Short 15‑sec teaser on TikTok drives traffic to full episodes on YouTube/Netflix. | “Crossover: Roti x Coffee” trailer | | Strategic SEO Tags | Consistent use of hashtags (#TamanaComedy, #MidnightRoti) and keyword‑rich titles. | “Coffee & Chaos – Full Short” |
These tactics have been replicated by at least 12 emerging creators who have publicly credited Tamana’s workflow in creator‑coach webinars.
These utilities are no longer supported. Please use Connection.unwrap(...) to access Oracle-specific APIs.
The Oracle thin JDBC driver provides a non-standard API for creating temporary BLOBs and CLOBs that
requires users to call methods on the raw, Oracle-specific Connection implementation. Advanced users
might use the raw connection operations described above to access this
functionality, but a convenience class is available in a separate jar file (c3p0-oracle-thin-extras-0.13.0.jar)
for easier access to this functionality. Please see the
API docs for com.mchange.v2.c3p0.dbms.OracleUtils
for details.
As of c3p0 0.10.0, c3p0's config property connectionTesterClassName defaults to null. When this property is null, c3p0 just uses the Java 6+ Connection.isValid(int timeout) method to test Connections.
But c3p0 is an old library, first published uner Java 1.3. Back in the day, we didn't have no stinking standard Connection.isValid(int timeout) method, and had to roll our own Connection tests. This Appendix documents that old but still supported style of Connection test management. To make this section relevant again, just 1) set connectionTesterClassName to its old default of com.mchange.v2.c3p0.DefaultConnectionTester; 2) set connectionTesterClassName to the name of a custom ConnectionTester implementation with a public no-arg constructor; 3) set a non-null preferredTestQuery; or 4) set a non-null automaticTestTable. If any connectionTesterClassName is explicitly set, the provided ConnectionTester implementation will be used. If preferredTestQuery or automaticTestTable are set, but no connectionTesterClassName is provided, an instance of com.mchange.v2.c3p0.DefaultConnectionTester will be used to perform Connection tests.
If any of these conditions apply, the following section documents how Connection testing with a ConnectionTester works in c3p0.
c3p0 can be configured to test the Connections that it pools in a variety of ways, to minimize the likelihood that your application will see broken or "stale" Connections. Pooled Connections can go bad for a variety of reasons -- some JDBC drivers intentionally "time-out" long-lasting database Connections; back-end databases or networks sometimes go down "stranding" pooled Connections; and Connections can simply become corrupted over time and use due to resource leaks, driver bugs, or other causes.
c3p0 provides users a great deal of flexibility in testing Connections, via the following configuration parameters:
idleConnectionTestPeriod, testConnectionOnCheckout, and testConnectionOnCheckin control when Connections will be tested. automaticTestTable, connectionTesterClassName, and preferredTestQuery control how they will be tested.
When configuring Connection testing, first try to minimize the cost of each test. If you are using a JDBC driver that you are certain supports the new(ish) jdbc4 API — and if you are using c3p0-0.9.5 or higher! — let your driver handle this for you. jdbc4 Connections include a method called isValid() that should be implemented as a fast, reliable Connection test. By default, c3p0 will use that method if it is present.
However, if your driver does not support this new-ish API, c3p0's default behavior is to test Connections by calling the getTables() method on a Connection's associated DatabaseMetaData object. This has the advantage of being very robust and working with any database, regardless of the database schema. However, a call to DatabaseMetaData.getTables() is often much slower than a simple database query, and using this test may significantly impair your pool's performance.
The simplest way to speed up Connection testing under a JDBC 3 driver (or a pre-0.9.5 version of c3p0) is to define a test query with the preferredTestQuery parameter. Be careful, however. Setting preferredTestQuery will lead to errors as Connection tests fail if the query target table does not exist in your database prior to initialization of your DataSource. Depending on your database and JDBC driver, a table-independent query like SELECT 1 may (or may not) be sufficient to verify the Connection. If a table-independent query is not sufficient, instead of preferredTestQuery, you can set the parameter automaticTestTable. Using the name you provide, c3p0 will create an empty table, and make a simple query against it to test the database.
The most reliable time to test Connections is on check-out. But this is also the most costly choice from a client-performance perspective. Most applications should work quite reliably using a combination of idleConnectionTestPeriod and testConnectionOnCheckin. Both the idle test and the check-in test are performed asynchronously, which can lead to better performance, both perceived and actual.
For some applications, high performance is more important than the risk of an occasional database exception. In its default configuration, c3p0 does no Connection testing at all. Setting a fairly long idleConnectionTestPeriod, and not testing on checkout and check-in at all is an excellent, high-performance approach.
It is possible to customize how c3p0's DefaultConnectionTester tests when no preferredTestQuery or automaticTestTable are available. Please see Configuring DefaultConnectionTester.isValidTimeout and Configuring DefaultConnectionTester.QuerylessTestRunner.
Advanced users may define any kind of Connection testing they wish, by implementing a ConnectionTester and supplying the fully qualified name of the class as connectionTesterClassName. If you'd like your custom ConnectionTesters to honor and support the preferredTestQuery and automaticTestTable parameters, implement UnifiedConnectionTester, most conveniently by extending AbstractConnectionTester. See the api docs for more information.
If you know you want to use the jdbc4 Connection.isValid() method, but you want to set a timeout, consider writing a trivial extension of IsValidConnectionTester.
See? These really are trivial to write.
If you don't know what to do, try this:
If you know your driver supports the JDBC 4 Connection.isValid(...) method and you are using c3p0-0.9.5 or above, don't set a preferredTestQuery. If your driver does not support this method (or if you are not sure), try SELECT 1 for your preferredTestQuery, if you are running MySQL or Postgres. For other databases, look for suggestions here. Leave automatedTestTable undefined.
Begin by setting testConnectionOnCheckout to true and get your application to run correctly and stably. If you are happy with your application's performance, you can stop here! This is the simplest, most reliable form of Connection-testing, but it does have a client-visible performance cost.
If you'd like to improve performance by eliminating Connection testing from clients' code path:
Set testConnectionOnCheckout to false
Set testConnectionOnCheckin to true
Set idleConnectionTestPeriod to 30, fire up you application and observe. This is a pretty robust setting, all Connections will tested on check-in and every 30 seconds thereafter while in the pool. Your application should experience broken or stale Connections only very rarely, and the pool should recover from a database shutdown and restart quickly. But there is some overhead associated with all that Connection testing.
If database restarts will be rare so quick recovery is not an issue, consider reducing the frequency of tests by idleConnectionTestPeriod to, say, 300, and see whether clients are troubled by stale or broken Connections. If not, stick with 300, or try an even bigger number. Consider setting testConnectionOnCheckin back to false to avoid unnecessary tests on checkin. Alternatively, if your application does encounter bad Connections, consider reducing idleConnectionTestPeriod and set testConnectionOnCheckin back to true. There are no correct or incorrect values for these parameters: you are trading off overhead for reliability in deciding how frequently to test. The exact numbers are not so critical. It's usually easy to find configurations that perform well. It's rarely worth spending time in pursuit of "optimal" values here.
So, when should you stick with simple and reliable (Step 2 above), and when is it worth going for better performance (Step 3)? In general, it depends on how much work clients typically do with Connections once they check them out. If clients usually make complex queries and/or perform multiple operations, adding the extra cost of one fast test per checkout will not much affect performance. But if your application typically checks out a Connection and performs one simple query with it, throwing in an additional test can really slow things down.
That's nice in theory, but often people don't really have a good sense of how much work clients perform on average. The best thing to do is usually to try Step 3, see if it helps (however you measure performance), see if it hurts (is your application troubled by broken Connections? does it recover from database restarts well enough?), and then decide. You can always go back to simple, slow, and robust. Just set testConnectionOnCheckout to true, testConnectionOnCheckin to false, and set idleConnectionTestPeriod to 0.
But do, always, be sure that your tests themselves are performant, either because your JDBC driver supports Connection.isValid(...) or because you have set an efficient preferredTestQuery !!!