[CONJ-33] JDBC unregister problem Created: 2013-05-03 Updated: 2013-05-03 Resolved: 2013-05-03 |
|
| Status: | Closed |
| Project: | MariaDB Connector/J |
| Component/s: | None |
| Affects Version/s: | 1.1.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Riccardo Prandini | Assignee: | Rasmus Johansson (Inactive) |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Tomcat 7 jdbc driver loaded in one JSP test page then used and closed, (recordset, statement and connection) |
||
| Description |
|
SEVERE: The web application [] registered the JDBC driver [org.mariadb.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered. |
| Comments |
| Comment by Vladislav Vaintroub [ 2013-05-03 ] |
|
The first hit on google delivers correct answer : ignore or put the driver into tomcat's lib directory. There are many different answers on stackoverflow : http://stackoverflow.com/questions/3320400/to-prevent-a-memory-leak-the-jdbc-driver-has-been-forcibly-unregistered (All found with googling for "A web application registered the JBDC drive mysql bug") Feel free to share more details, if you still think there is some bug in our code. Thanks. |
| Comment by Riccardo Prandini [ 2013-05-03 ] |
|
No problem; I have also read about it, but I had read about this issue in DBCP a time ago. |