Your message dated Fri, 09 Aug 2013 13:30:45 +0200
with message-id <>
and subject line Re: libmysql-java: Prepared Queries broken
has caused the Debian Bug report #564961,
regarding libmysql-java: Prepared Queries broken
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Package: libmysql-java
Version: 5.1.10+dfsg-2
Severity: critical
Justification: breaks unrelated software

libmysql-java 5.1.0 does not work with prepared queries.

NoClassDefFoundError: Could not initialize class 
    at com.mysql.jdbc.ConnectionImpl.prepareStatement(
    at com.mysql.jdbc.ConnectionImpl.prepareStatement(
    at sql.SqlServerRecord.prepareStatement(

Replacing the mysql-java.jar in /usr/share/java
with mysql-connector-5.0.8 or 5.1.6 makes the problem go away.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libmysql-java depends on:
ii  default-jre-headless [java2 1.6-34       Standard Java or Java compatible R
ii  openjdk-6-jre-headless [jav 6b16-1.6.1-2 OpenJDK Java runtime, using Hotspo
ii  sun-java6-jre [java2-runtim 6-16-1       Sun Java(TM) Runtime Environment (

libmysql-java recommends no packages.

Versions of packages libmysql-java suggests:
ii  libcommons-logging-java       1.1.1-6    commmon wrapper interface for seve
ii  liblog4j1.2-java              1.2.15-7   Logging library for java

-- no debconf information

--- End Message ---
--- Begin Message ---
I'm closing this bug since it isn't reproducible and most likely a
mistake in the usage of the library (the jar wasn't in the classpath).

--- End Message ---
This is the maintainer address of Debian's Java team
Please use for discussions and questions.

Reply via email to