<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.db.mysql.java">
    <title>gmane.comp.db.mysql.java</title>
    <link>http://blog.gmane.org/gmane.comp.db.mysql.java</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.mysql.java/5519"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.mysql.java/5518"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.mysql.java/5517"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.mysql.java/5516"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.mysql.java/5515"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.mysql.java/5514"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.mysql.java/5513"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.mysql.java/5512"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.mysql.java/5511"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.mysql.java/5510"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.mysql.java/5509"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.mysql.java/5508"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.mysql.java/5507"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.mysql.java/5506"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.mysql.java/5505"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.mysql.java/5504"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.mysql.java/5503"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.mysql.java/5502"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.mysql.java/5501"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.db.mysql.java/5500"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.mysql.java/5519">
    <title>MySQL Connector/J 5.1.20 has been released</title>
    <link>http://permalink.gmane.org/gmane.comp.db.mysql.java/5519</link>
    <description>&lt;pre&gt;Hello all,

MySQL Connector/J 5.1.20, a maintenance release of the production 5.1 
branch has been released.
Connector/J is the Type-IV pure-Java JDBC driver for MySQL.

Version 5.1.20 is suitable for use with many MySQL server versions, 
including 4.1, 5.0, 5.1, 5.4 and 5.5.

It is now available in source and binary form from the Connector/J 
download pages at
http://dev.mysql.com/downloads/connector/j/5.1.html
and mirror sites as well as Maven-2 repositories.

As always, we recommend that you check the "CHANGES" file in the 
download archive to be aware of changes in behavior that might affect 
your application.

We welcome and appreciate your feedback, bug reports, bug fixes, patches 
etc:
http://forge.mysql.com/wiki/Contributing

MySQL Connector/J 5.1.20 includes the following general bug fixes and 
improvements also listed in more detail on 
http://dev.mysql.com/doc/connector-j/en/cj-news-5-1-20.html:
   - Fix for Bug#64983, 5.1.19 not working with JBoss AS 4.2.3.GA.
   - Fix for Bug#13960556, java.lang.StringIndexOutOfBoundsException in 
com.mysql.jdbc.PreparedStatement.formatNanos(int nanos).
   - Fix for pluggable authentication tests to run on Windows.
   - Fix for Bug#13897714, NPE in 
testsuite.regression.StatementRegressionTest.testBug1933() with 5.6.5_m8 
server.
   - Fix for Bug#55962, Savepoint identifier is occasionally considered 
as floating point numbers.
   - Fix for Bug#13955027, SET OPTION syntax was removed starting from 
5.6.5 server version.
   - Fix for Bug#13958793, ClassCastException in 
ConnectionImpl.buildCollationMapping() with 4.1 server.
   - Fix for Bug#36478, Client prepared statement bugged if word 'limit' 
included in the query.


Enjoy!

Tonci

&lt;/pre&gt;</description>
    <dc:creator>Tonci Grgin</dc:creator>
    <dc:date>2012-05-02T06:05:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.mysql.java/5518">
    <title>MySQL Connector/J 5.1.19 has been released</title>
    <link>http://permalink.gmane.org/gmane.comp.db.mysql.java/5518</link>
    <description>&lt;pre&gt;Hello all,

MySQL Connector/J 5.1.19, a maintenance release of the production 5.1 
branch has been released.
Connector/J is the Type-IV pure-Java JDBC driver for MySQL.

Version 5.1.19 is suitable for use with many MySQL server versions, 
including 4.1, 5.0, 5.1, 5.4 and 5.5.

It is now available in source and binary form from the Connector/J 
download pages at
http://dev.mysql.com/downloads/connector/j/5.1.html
and mirror sites as well as Maven-2 repositories.

As always, we recommend that you check the "CHANGES" file in the 
download archive to be aware of changes in behavior that might affect 
your application.

We welcome and appreciate your feedback, bug reports, bug fixes, patches 
etc:
http://forge.mysql.com/wiki/Contributing

MySQL Connector/J 5.1.19 includes the following general bug fixes and 
improvements:

   - Fix for Bug#64621, setMaxRows was not correctly processed during CS 
PS metadata
     collection causing entire resultset to be fetched and possibly 
leading to OOM.

   - Fix for Bug#63456, MetaData precision is different when using UTF8 
or Latin1 tables.
     The problem was in finding maxBytesPerChar through versioned 
mapping from Java charset to MySQL charset.
     That map returns "utf8mb4" instead "utf8" for server versions 
starting with 5.5.2.
     CharsetMapping, ConnectionImpl and Field have been reorganized to 
use static maps INDEX_TO_MYSQL_CHARSET,
     STATIC_CHARSET_TO_NUM_BYTES_MAP instead. Also dynamic maps 
ConnectionImpl.indexToCustomMysqlCharset
     and ConnectionImpl.mysqlCharsetToCustomMblen have been added for 
custom charsets.

   - Added support for pluggable authentication via the 
com.mysql.jdbc.AuthenticationPlugin
     interface (which extends standard "extension" interface). Examples 
are in
     com/mysql/jdbc/authentication and in 
testsuite.regression.ConnectionRegressionTest.
     This introduces three new properties:

        authenticationPlugins defines comma-delimited list of classes 
that implement
        com.mysql.jdbc.AuthenticationPlugin and which will be used for 
authentication
        unless disabled by "disabledAuthenticationPlugins" property.

        disabledAuthenticationPlugins defines comma-delimited list of 
classes implementing
        com.mysql.jdbc.AuthenticationPlugin or mechanisms, i.e. 
"mysql_native_password".
        The authentication plugins or mechanisms listed will not be used 
for authentication
        which will fail if it requires one of them. It is an error to 
disable the default
        authentication plugin (either the one named by 
"defaultAuthenticationPlugin" property
        or the hard-coded one if "defaultAuthenticationPlugin" propery 
is not set).

        defaultAuthenticationPlugin defines name of a class implementing
        com.mysql.jdbc.AuthenticationPlugin which will be used as the 
default authentication
        plugin. It is an error to use a class which is not listed in 
"authenticationPlugins"
        nor it is one of the built-in plugins. It is an error to set as 
default a plugin
        which was disabled with "disabledAuthenticationPlugins" 
property. It is an error
        to set this value to null or the empty string (i.e. there must 
be at least a valid
        default authentication plugin specified for the connection, 
meeting all constraints
        listed above).

   - Fix for Bug#63526. The problem happens in 
com.mysql.jdbc.EscapeProcessor#escapeSQL. The function recognizes the 
string in the create table statement as an escape sequence (line 
136+138). The "if" construct beginning in line 182 tries to match a 
white-space collapsed version of the string to prefixes for valid 
jdbc-escapes (till line 300). Since no matching escape sequence is found 
and no "else" clause is defined, neither the token, nor replacement are 
added to the resulting escaped SQL string.

   - Fix for Bug#61203, noAccessToProcedureBodies does not work anymore.

   - Fix for Bug#63811, pointless Socket.bind() when using ephemeral 
ports and interfaces, which limits scalability on some platforms.

   - Connection.changeUser() would not check for closed connections, 
leading to NPEs when this method was called on a closed connection.

   - Fix for Bug#63284, memory leak with Failover proxied 
Statement/PreparedStatement with DBCP due to improper implementation of 
equals().

   - Prepared statements would needlessly allocate a 4K buffer for 
converting
     streams when no set*Stream() methods had been used.


Enjoy!

Tonci

&lt;/pre&gt;</description>
    <dc:creator>Tonci Grgin</dc:creator>
    <dc:date>2012-04-04T07:22:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.mysql.java/5517">
    <title>NullPointerException in GregorianCalendar.java:2026 when upgrading to debian squeeze</title>
    <link>http://permalink.gmane.org/gmane.comp.db.mysql.java/5517</link>
    <description>&lt;pre&gt;From mysqld  Ver 5.0.51a-24+lenny2-log for debian-linux-gnu on i486 
To      mysqld  Ver 5.1.49-3-log for debian-linux-gnu on i486
java.lang.NullPointerException
at
java.util.GregorianCalendar.computeFields(GregorianCalendar.java:2026)
at
java.util.GregorianCalendar.computeFields(GregorianCalendar.java:1996)
at java.util.Calendar.setTimeInMillis(Calendar.java:1109)
at java.util.Calendar.setTime(Calendar.java:1075)
at java.text.SimpleDateFormat.format(SimpleDateFormat.java:876)

It appears that in mysql-connector-java-5.1.10-bin.jar:
com.mysql.jdbc.PreparedStatement line: 4728

this.tsdf.setTimeZone(this.connection.getServerTimezoneTZ());

is null.

The combination "
useGmtMillisForDatetimes=true&amp;amp;amp;serverTimezone=Europe/Zurich&amp;amp;amp;" in my
tomcat's server.xml appears to fix it.
Any better hints?

    Thanks in advance

          Ralf


&lt;/pre&gt;</description>
    <dc:creator>gmx</dc:creator>
    <dc:date>2012-01-15T08:21:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.mysql.java/5516">
    <title>How disable innodb support.</title>
    <link>http://permalink.gmane.org/gmane.comp.db.mysql.java/5516</link>
    <description>&lt;pre&gt;Hi!  Can any body tell me how disable innodb support in mysql embedded
connector/MXJ?
I know that exist a skip-innodb option for my.cnf file and --skip-innodb as
parameter for mysqld, but when i try use it into the server options map
this does not disable innodb, i don't know why.
I don't need innodb support and it make very slow the mysqld startup.

I am using mysql-connector-mxj-gpl-5-0-12.jar and
mysql-connector-java-5.1.18-bin.jar

Thanks, any help is important to me.
&lt;/pre&gt;</description>
    <dc:creator>Victor Cifuentes</dc:creator>
    <dc:date>2012-01-15T05:48:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.mysql.java/5515">
    <title>Re: Problem with in-memory connector MXJ</title>
    <link>http://permalink.gmane.org/gmane.comp.db.mysql.java/5515</link>
    <description>&lt;pre&gt;Mmmmmh. It looks like it works!

Thanx!

Pierre



2011/12/21 Celil Germeyan &amp;lt;celilg&amp;lt; at &amp;gt;itg.com.tr&amp;gt;



&lt;/pre&gt;</description>
    <dc:creator>Pierre Goupil</dc:creator>
    <dc:date>2011-12-29T16:05:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.mysql.java/5514">
    <title>Problem with in-memory connector MXJ</title>
    <link>http://permalink.gmane.org/gmane.comp.db.mysql.java/5514</link>
    <description>&lt;pre&gt;Good afternoon,

I'm currently trying and configure MySQL in order to have an in-memory
database in my unit tests. My environment is: Linux 3.0.0, Java 6 openJDK,
MySQL connector 5.0.7 and MXJ 5.0.12.

Here's my code:

------------------
String driver = System.getProperty("SQL_DRIVER", "com.mysql.jdbc.Driver");
String defaultUrl =
"jdbc:mysql:///test?propertiesTransform=com.mysql.management.jmx.ConnectorMXJPropertiesTransform";

String url = System.getProperty("SQL_URL", defaultUrl);
String user = System.getProperty("SQL_USER", "root");
String password = System.getProperty("SQL_PW", "");

Class.forName(driver);

Connection conn = DriverManager.getConnection(url, user, password);
------------------

I get an exception at the last line:

------------------
Exception in thread "main" java.lang.IndexOutOfBoundsException: Index: 0,
Size: 0
at java.util.ArrayList.rangeCheck(ArrayList.java:571)
at java.util.ArrayList.get(ArrayList.java:349)
at
com.mysql.management.jmx.ConnectorMXJPropertiesTransform.&amp;lt;init&amp;gt;(ConnectorMXJPropertiesTransform.java:63)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)

at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
at java.lang.Class.newInstance0(Class.java:372)
at java.lang.Class.newInstance(Class.java:325)
at
com.mysql.jdbc.NonRegisteringDriver.parseURL(NonRegisteringDriver.java:639)
at
com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:280)
at java.sql.DriverManager.getConnection(DriverManager.java:620)
at java.sql.DriverManager.getConnection(DriverManager.java:200)
at mxj.Start.main(Start.java:25)
------------------

A clue, anyone? Any help will be much appreciated.

Regards,

Pierre Goupil




&lt;/pre&gt;</description>
    <dc:creator>Pierre Goupil</dc:creator>
    <dc:date>2011-12-21T14:24:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.mysql.java/5513">
    <title>Re: jdbc: values from mysql table always null</title>
    <link>http://permalink.gmane.org/gmane.comp.db.mysql.java/5513</link>
    <description>&lt;pre&gt;Hey Ryan,

On 12/12/2011 9:35 AM, Ryan Beckes wrote:

You say that the same exact commands executed in the CLI work fine and 
produce different results than when executed from the JDBC client 
application.  If that's the case, the most probably root cause is SQL 
Mode (for JDBC compliance, Connector/J sets SQL Mode to 
"strict_trans_tables").  The various SQL modes are described here:

http://dev.mysql.com/doc/refman/5.5/en/server-sql-mode.html

The fastest way to see exactly what's happening is to turn on the MySQL 
Server general query log, and issue the same statements from both the 
CLI and the JDBC application.  This will log the statements before they 
are executed - including statements to set the SQL Mode - and should 
help confirm exactly what the server is receiving from the JDBC application.

Best regards,

&lt;/pre&gt;</description>
    <dc:creator>Todd Farmer</dc:creator>
    <dc:date>2011-12-12T19:05:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.mysql.java/5512">
    <title>jdbc: values from mysql table always null</title>
    <link>http://permalink.gmane.org/gmane.comp.db.mysql.java/5512</link>
    <description>&lt;pre&gt;Hello,

I am trying to copy one table to another using jdbc (see code below). The
table is copied fine, but the last column is NULL for all values. I am also
having problems retrieving the value from that table (the value is always
returned as null). If I run the same sql commands via the mysql client, the
table is copied OK.

Thanks,
Ryan





    Connection conn = null;
    PreparedStatement ps1 = null;
    PreparedStatement ps2 = null;
    PreparedStatement ps3 = null;
    try {
      String userName = "user";
      String password = "password";
      String url = "jdbc:mysql://localhost:3306/plus";
      Class.forName ("com.mysql.jdbc.Driver").newInstance ();
      conn = DriverManager.getConnection (url, userName, password);
      System.out.println ("Database connection established");
      String dropQuery="DROP TABLE IF EXISTS CLASSMEMBERSHIPTMP";
      ps1 = conn.prepareStatement(dropQuery);
      ps1.executeUpdate();
      String createTmpQuery="CREATE TABLE IF NOT EXISTS CLASSMEMBERSHIPTMP
(ID bigint(20), SUBCLASS1 varchar(255), SUBCLASS2 varchar(255), SUBCLASS3
varchar(255), SUBCLASS4 varchar(255), SUBCLASS5 varchar(255), SUBCLASS6
varchar(255), CLASSMEMBERSHIP_ITEM_ID bigint(20))";
      ps2 = conn.prepareStatement(createTmpQuery);
      ps2.executeUpdate();
      String copyQuery="INSERT INTO CLASSMEMBERSHIPTMP select * from
CLASSMEMBERSHIP";
      ps3 = conn.prepareStatement(copyQuery);
      ps3.executeUpdate();
    } catch (Exception e) {
      LOGGER.info ("Cannot connect to database server");
    } finally {
      if (conn != null) {
        try {
          conn.close ();
          LOGGER.info ("Database connection terminated");
        } catch (Exception e) {
          //ignore close errors
        }
      }
    }

mysql&amp;gt; desc CLASSMEMBERSHIP;
+-------------------------+--------------+------+-----+---------+----------------+
| Field                   | Type         | Null | Key | Default |
Extra          |
+-------------------------+--------------+------+-----+---------+----------------+
| ID                      | bigint(20)   | NO   | PRI | NULL    |
auto_increment |
| SUBCLASS1               | varchar(255) | YES  |     | NULL
|                |
| SUBCLASS2               | varchar(255) | YES  |     | NULL
|                |
| SUBCLASS3               | varchar(255) | YES  |     | NULL
|                |
| SUBCLASS4               | varchar(255) | YES  |     | NULL
|                |
| SUBCLASS5               | varchar(255) | YES  |     | NULL
|                |
| SUBCLASS6               | varchar(255) | YES  |     | NULL
|                |
| CLASSMEMBERSHIP_ITEM_ID | bigint(20)   | YES  | MUL | NULL
|                |
+-------------------------+--------------+------+-----+---------+----------------+
8 rows in set (0.01 sec)

mysql&amp;gt; select * from CLASSMEMBERSHIPTMP;
+------+-----------+----------------+----------------------+-----------+-----------+-----------+-------------------------+
| ID   | SUBCLASS1 | SUBCLASS2      | SUBCLASS3            | SUBCLASS4 |
SUBCLASS5 | SUBCLASS6 | CLASSMEMBERSHIP_ITEM_ID |
+------+-----------+----------------+----------------------+-----------+-----------+-----------+-------------------------+
|    1 | C1CORE    | C1COREC2APPLE  | C1COREC2APPLEC3REDAP |
|           |           |                       1 |
|    2 | C1DELMO   |                |                      |
|           |           |                       1 |
|    3 | C1JRSIM   |                |                      |
|           |           |                       1 |
|    4 | C1MACAD   |                |                      |
|           |           |                       1 |
|    5 | P1B5      |                |                      |
|           |           |                       1 |
&lt;/pre&gt;</description>
    <dc:creator>Ryan Beckes</dc:creator>
    <dc:date>2011-12-12T17:35:10</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.mysql.java/5511">
    <title>escaping in a non-prepared query</title>
    <link>http://permalink.gmane.org/gmane.comp.db.mysql.java/5511</link>
    <description>&lt;pre&gt;Hello,

 In my application I have a query which is very hard to rewrite to a preparedstatement for legacy reasons. Is there some method so I can do the right escaping by hand?

 query = "SELECT * FROM foo WHERE bar = '" + MySQLUtils.escapeString("bla") + "'";

 Something like that.

 Thanks in advance,
 Ronald.&lt;/pre&gt;</description>
    <dc:creator>Ronald Klop (Mailing List</dc:creator>
    <dc:date>2011-11-04T12:22:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.mysql.java/5510">
    <title>MySQL Connector/J 5.1.18 has been released</title>
    <link>http://permalink.gmane.org/gmane.comp.db.mysql.java/5510</link>
    <description>&lt;pre&gt;Hello all,

MySQL Connector/J 5.1.18, a maintenance release of the production 5.1 branch has been released.
Connector/J is the Type-IV pure-Java JDBC driver for MySQL.

Version 5.1.18 is suitable for use with any MySQL version including MySQL-5.1 or MySQL-5.5.

It is now available in source and binary form from the Connector/J download pages at

http://dev.mysql.com/downloads/connector/j/5.1.html

and mirror sites as well as Maven-2 repositories.

As always, we recommend that you check the "CHANGES" file in the download 
archive to be aware of changes in behavior that might affect your application.

We welcome and appreciate your feedback, bug reports, bug fixes, patches etc.:

http://forge.mysql.com/wiki/Contributing

MySQL Connector/J 5.1.18 includes the following general bug fixes and improvements:

 - Fix for Bug#12565726, not putting the space between VALUES() and ON DUPLICATE KEY UPDATE
   causes C/J a) enter rewriting the query although it has ON UPDATE
   and b) to generate the wrong query with multiple ON DUPLICATE KEY

 - Fix for Bug#12784170, "process fork failure" errors while running test suite via ant on Windows.
   Added new ant flag, com.mysql.jdbc.junit.fork, which controls whether JUnit will fork new processes
   for testing ("on", default and legacy behavior) or not ("off", required for Windows). 
 - Reverting changes made to ConnectionImpl.java,
   private boolean characterSetNamesMatches function.

 - Added function MYSQL_INDEX_TO_MYSQL_CHARSET to retrieve server charset name
   using index instead of parsing variables to CharsetMapping.java.

 - Completed fix for Bug#61201/12649557, fixed tests failures.

 - Fix for Bug#61201/12649557, Can't establish connection when url has
   sessionVariables and characterEncoding. Fix covers only MySQL server 4.1+
 
 - Fix for Bug#61501 - Calling Statement.cancel() on a statement that isn't
   currently executing will cause some later-executed query on the same
   connection to be cancelled unexpectedly. The driver now guards against this
   condition, but it is an underlying server issue. The MySQL statement "KILL QUERY"
   (which is what the driver uses to implement Statement.cancel()) is rather
   non-deterministic, and thus the use of Statement.cancel() should be avoided
   if possible.

 - Fix for Bug#61866/12791594 - Calling Statement.getWarnings() after
   Statement.clearWarnings() has been called, returns the "old" warnings.

 - Fix for Bug#13036537 - LRUCache was really a least-recently-added cache.

 - Fix for Bug#13036309, Correcting parameter name in maxPerformance.properties.



Enjoy!

Tonci

&lt;/pre&gt;</description>
    <dc:creator>Tonci Grgin</dc:creator>
    <dc:date>2011-10-04T08:36:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.mysql.java/5509">
    <title>executing Java code from database trigger.</title>
    <link>http://permalink.gmane.org/gmane.comp.db.mysql.java/5509</link>
    <description>&lt;pre&gt;Hi,

I wanted to run java method from trigger. for that i need to write java db
procedure.. as mention in
http://download.oracle.com/javase/tutorial/jdbc/basics/storedprocedures.html#creating_stored_procedures_java_db
but i am getting sql syntax error at 'AS LANGUAGE' please let me know if you
have th solution for  the same..

my create procedure statement is =

          "CREATE PROCEDURE log_sal(IN idsal float, IN old_sal float, IN
new_sal float) " +
            //"PARAMETER STYLE JAVA " +
          "AS "+
            "LANGUAGE JAVA " +
            //"DYNAMIC RESULT SETS 1 " +
            "EXTERNAL NAME 'com.trigger.DBTrigger.logSal'";
&lt;/pre&gt;</description>
    <dc:creator>pravin kalbhor</dc:creator>
    <dc:date>2011-10-04T05:31:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.mysql.java/5508">
    <title>confirm unsubscribe to java&lt; at &gt;lists.mysql.com</title>
    <link>http://permalink.gmane.org/gmane.comp.db.mysql.java/5508</link>
    <description>&lt;pre&gt;To confirm that you would like

  gcdmj-java&amp;lt; at &amp;gt;m.gmane.org

removed from the java mailing list, please click on
the following link:

  http://lists.mysql.com/u/java/4e4f2360d44b612a/gcdmj-java=m.gmane.org

This confirmation serves two purposes. First, it verifies that we are
able to get mail through to you. Second, it protects you in case
someone forges a subscription request in your name.

We haven't checked whether your address is currently on the mailing list.
To see what address you used to subscribe, look at the messages you are
receiving from the mailing list. Each message has your address hidden
inside its return path; for example, john&amp;lt; at &amp;gt;example.com receives messages
with return path: java-return-&amp;lt;number&amp;gt;-john=example.com&amp;lt; at &amp;gt;lists.mysql.com.


--- Administrative commands for the java list ---

I can handle administrative requests automatically. Please
do not send them to the list address! Instead, send
your message to the correct command address:

To subscribe to the list, send a message to:
   &amp;lt;java-subscribe&amp;lt; at &amp;gt;lists.mysql.com&amp;gt;

To remove your address from the list, just send a message to
the address in the ``List-Unsubscribe'' header of any list
message. If you haven't changed addresses since subscribing,
you can also send a message to:
   &amp;lt;java-unsubscribe&amp;lt; at &amp;gt;lists.mysql.com&amp;gt;

or for the digest to:
   &amp;lt;java-digest-unsubscribe&amp;lt; at &amp;gt;lists.mysql.com&amp;gt;

For addition or removal of addresses, I'll send a confirmation
message to that address. When you receive it, simply reply to it
to complete the transaction.

If you need to get in touch with the human owner of this list,
please send a message to:

    &amp;lt;java-owner&amp;lt; at &amp;gt;lists.mysql.com&amp;gt;

Please include a FORWARDED list message with ALL HEADERS intact
to make it easier to help you.

--- Enclosed is a copy of the request I received.

Received: (qmail 742 invoked by uid 48); 20 Aug 2011 03:00:48 -0000
Date: 20 Aug 2011 03:00:48 -0000
Message-ID: &amp;lt;20110820030048.741.qmail&amp;lt; at &amp;gt;lists.mysql.com&amp;gt;
To: java-unsubscribe-gcdmj-java=m.gmane.org&amp;lt; at &amp;gt;lists.mysql.com
Subject: Unsubscribe request
From: &amp;lt;gcdmj-java&amp;lt; at &amp;gt;m.gmane.org&amp;gt;

This message was generated because of a request from 80.239.243.133.

&lt;/pre&gt;</description>
    <dc:creator>java-help&lt; at &gt;lists.mysql.com</dc:creator>
    <dc:date>2011-08-20T03:00:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.mysql.java/5507">
    <title>confirm unsubscribe to java&lt; at &gt;lists.mysql.com</title>
    <link>http://permalink.gmane.org/gmane.comp.db.mysql.java/5507</link>
    <description>&lt;pre&gt;To confirm that you would like

  gcdmj-java&amp;lt; at &amp;gt;m.gmane.org

removed from the java mailing list, please click on
the following link:

  http://lists.mysql.com/u/java/4e4f2343ed93b80b/gcdmj-java=m.gmane.org

This confirmation serves two purposes. First, it verifies that we are
able to get mail through to you. Second, it protects you in case
someone forges a subscription request in your name.

We haven't checked whether your address is currently on the mailing list.
To see what address you used to subscribe, look at the messages you are
receiving from the mailing list. Each message has your address hidden
inside its return path; for example, john&amp;lt; at &amp;gt;example.com receives messages
with return path: java-return-&amp;lt;number&amp;gt;-john=example.com&amp;lt; at &amp;gt;lists.mysql.com.


--- Administrative commands for the java list ---

I can handle administrative requests automatically. Please
do not send them to the list address! Instead, send
your message to the correct command address:

To subscribe to the list, send a message to:
   &amp;lt;java-subscribe&amp;lt; at &amp;gt;lists.mysql.com&amp;gt;

To remove your address from the list, just send a message to
the address in the ``List-Unsubscribe'' header of any list
message. If you haven't changed addresses since subscribing,
you can also send a message to:
   &amp;lt;java-unsubscribe&amp;lt; at &amp;gt;lists.mysql.com&amp;gt;

or for the digest to:
   &amp;lt;java-digest-unsubscribe&amp;lt; at &amp;gt;lists.mysql.com&amp;gt;

For addition or removal of addresses, I'll send a confirmation
message to that address. When you receive it, simply reply to it
to complete the transaction.

If you need to get in touch with the human owner of this list,
please send a message to:

    &amp;lt;java-owner&amp;lt; at &amp;gt;lists.mysql.com&amp;gt;

Please include a FORWARDED list message with ALL HEADERS intact
to make it easier to help you.

--- Enclosed is a copy of the request I received.

Received: (qmail 608 invoked by uid 48); 20 Aug 2011 03:00:19 -0000
Date: 20 Aug 2011 03:00:19 -0000
Message-ID: &amp;lt;20110820030019.607.qmail&amp;lt; at &amp;gt;lists.mysql.com&amp;gt;
To: java-unsubscribe-gcdmj-java=m.gmane.org&amp;lt; at &amp;gt;lists.mysql.com
Subject: Unsubscribe request
From: &amp;lt;gcdmj-java&amp;lt; at &amp;gt;m.gmane.org&amp;gt;

This message was generated because of a request from 80.239.243.133.

&lt;/pre&gt;</description>
    <dc:creator>java-help&lt; at &gt;lists.mysql.com</dc:creator>
    <dc:date>2011-08-20T03:00:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.mysql.java/5506">
    <title>MySQL Connector/MXJ 5.0.12 has been released</title>
    <link>http://permalink.gmane.org/gmane.comp.db.mysql.java/5506</link>
    <description>&lt;pre&gt;Hello all.

MySQL Connector/MXJ 5.0.12 is now available for download.

MySQL Connector/MXJ 5.0.12 is a Java utility package for deploying
and managing a MySQL RDBMS.

The 5.0.12 version includes MySQL 5.5.9 server community binaries and
related resources for the following platforms:
       * Linux x86, x86_64
       * Mac OS X x86, x86_64
       * Windows XP/2K/NT/Vista/2003/2008/7 x86, x86_64
       * SunOS sparc, x86, x86_64
       * FreeBSD x86, x86_64

Platforms can easily be added or removed from:
mysql-connector-mxj-gpl-5-0-12-db-files.jar


MySQL Connector/MXJ may be bundled into an existing Java application
and managed as a POJO (Plain Old Java Object) or launched by creating a
Connector/J connection.

This makes it easy for Java developers creating an application that uses
JDBC through MySQL Connector/J to deploy applications which require a
database by reducing installation barriers for their end-users.

Adding a MySQL database to a Java application can be as easy as:
1) configuring the CLASSPATH to include:
       * Connector/J 5.x JDBC driver
         (mysql-connector-java-5.1.15-bin.jar)
       * Connector/MXJ classes
         (mysql-connector-mxj-gpl-5-0-12.jar)
       * Connector/MXJ resources
         (mysql-connector-mxj-gpl-5-0-12-db-files.jar)

2) create a JDBC connection string specifying where to deploy the
physical files "server.basedir", and whatever additional connection
parameters to pass to Connector/J or Connector/MXJ to refine the
behavior:

         String url = "jdbc:mysql:mxj://localhost:3306/" + dbName //
                 + "?" + "server.basedir=" + databaseDir //
                 + "&amp;amp;" + "createDatabaseIfNotExist=true"//
                 + "&amp;amp;" + "server.initialize-user=true" //
         ;

With Connector/J 5.x, simply adding "mxj:" will signal the Connector/J
JDBC driver to automatically deploy and launch the MySQL database with
the first connection.

In order for MySQL Connector/MXJ to make the MySQL database appear to be
a java-based component, it determines what platform the system is
running on, selects the appropriate binary, and launches the executable.
It will also optionally deploy an initial database, with any specified
parameters.

Included is a Connector/J URL example: ConnectorMXJUrlTestExample.java
and a POJO usage example: ConnectorMXJObjectTestExample.java
Each are located in the top level of mysql-connector-mxj-gpl-5-0-12.jar
and the source is in the src/ directory.

Documentation:

http://dev.mysql.com/doc/refman/5.5/en/connector-mxj.html


You can download Connector/MXJ
sources and binaries from:

http://dev.mysql.com/downloads/connector/mxj/5.0.html

You can download the latest Connector/J JDBC driver from:

http://dev.mysql.com/downloads/connector/j/5.1.html



Remember, feedback is welcome and encouraged.
Please send questions/comments to java&amp;lt; at &amp;gt;lists.mysql.com


&lt;/pre&gt;</description>
    <dc:creator>Tonci Grgin</dc:creator>
    <dc:date>2011-07-07T17:22:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.mysql.java/5505">
    <title>MySQL Connector/J 5.1.17 Has Been Released</title>
    <link>http://permalink.gmane.org/gmane.comp.db.mysql.java/5505</link>
    <description>&lt;pre&gt;Hello all,

MySQL Connector/J 5.1.17, a maintenance release of the production 5.1 branch has been released.
Connector/J is the Type-IV pure-Java JDBC driver for MySQL.

Version 5.1.17 is suitable for use with any MySQL version including MySQL-5.1 or MySQL-5.5.

It is now available in source and binary form from the Connector/J download pages at

http://dev.mysql.com/downloads/connector/j/5.1.html

and mirror sites as well as Maven-2 repositories and MOS.

As always, we recommend that you check the "CHANGES" file in the download 
archive to be aware of changes in behavior that might affect your application.

We welcome and appreciate your feedback, bug reports, bug fixes, patches etc.:

http://forge.mysql.com/wiki/Contributing

MySQL Connector/J 5.1.17 includes the following general bug fixes and improvements:

  - Fix for Bug#61332 - LIKE not optimized in server when run against I__S tables and no
    wildcards used. Databases/tables with "_" and/or "%" in their names (escaped or not)
    will be handled by this code path, although slower, since it's rare to find these
    characters in table names in SQL. If there's a "_" or "%" in the string, LIKE will
    take care of that, otherwise we now use = . The only exception is information_schema
    database which is handled separately. Patch covers both getTables() and getColumns().

  - Fix for Bug#61150 - First call to stored procedure fails with "No Database Selected".
    The workaround introduced in DatabaseMetaData.getCallStmtParameterTypes to fix the
    bug in server where SHOW CREATE PROCEDURE was not respecting lower-case table names
    is misbehaving when connection is not attached to database and on non-casesensitive OS.

  - Fix for Bug#61105 - Avoid a concurrent bottleneck in Java's character set
    encoding/decoding when converting bytes to/from Strings.
    * IMPORTANT NOTE *
    No longer use String.getBytes(...), or new String(byte[]...), use the StringUtils
    method instead.



Enjoy!

Tonci

&lt;/pre&gt;</description>
    <dc:creator>Tonci Grgin</dc:creator>
    <dc:date>2011-07-07T17:07:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.mysql.java/5504">
    <title>Re:5</title>
    <link>http://permalink.gmane.org/gmane.comp.db.mysql.java/5504</link>
    <description>&lt;pre&gt;...Friends always help you with your problems. Just rely on me.  http://www.team-wdl.de/friends.page.php?ypupageid=98x6

&lt;/pre&gt;</description>
    <dc:creator>Knaide</dc:creator>
    <dc:date>2011-06-12T00:09:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.mysql.java/5503">
    <title>Re: ConnectorJ 5.1.16 Source does not build on JDK 1.6.0_13</title>
    <link>http://permalink.gmane.org/gmane.comp.db.mysql.java/5503</link>
    <description>&lt;pre&gt;Ok Todd,  So I need to bind to the libraries of both v1.5 and v1.6.  I now 
have the Ant build defined and getting the warning about the different 
compliers.

I will play and sort this out.

thanks for the assist.

regards,

Kevin

-----Original Message----- 
From: Todd Farmer
Sent: Tuesday, May 24, 2011 6:10 PM
To: Kevin Hine
Cc: java&amp;lt; at &amp;gt;lists.mysql.com
Subject: Re: ConnectorJ 5.1.16 Source does not build on JDK 1.6.0_13

Hi Kevin,

On 5/24/2011 2:47 AM, Kevin Hine wrote:
...

Yes, unfortunately.  You'll want to take a look at the ant build script
- it has two different compile steps.  The first handles the pre-JDBC4
code baseline (which, as noted by the error message above, does not
implement the new-to-JDBC4 methods), and a second uses a Java 6.0+
compiler to handle the JDBC-specific classes.  Within C/J itself, the
driver does a check to see if we're running in a JDBC4-enabled JVM or
not, and if so, uses the classes in the com.mysql.jdbc.JDBC4* classes.

In short, use the ant build script to compile C/J (and you will need to
have a both a pre-6.0 and 6.0+ Java compiler).

Best regards,

&lt;/pre&gt;</description>
    <dc:creator>Kevin Hine</dc:creator>
    <dc:date>2011-05-25T10:30:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.mysql.java/5502">
    <title>ConnectorJ 5.1.16 Source does not build on JDK 1.6.0_13</title>
    <link>http://permalink.gmane.org/gmane.comp.db.mysql.java/5502</link>
    <description>&lt;pre&gt;Folks,

I am compiling within the Eclipse IDE.

Within com.mysql.jdbc.CallableStatement the implented java.sql.CallableStatement

results in the following error

“The type CallableStatement must implement the inherited abstract method CallableStatement.getNString(int)”

Is there something that I am missing?

regards,

Kevin&lt;/pre&gt;</description>
    <dc:creator>Kevin Hine</dc:creator>
    <dc:date>2011-05-24T09:47:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.mysql.java/5501">
    <title>Calling resultSet.getString after resultSet.updateString</title>
    <link>http://permalink.gmane.org/gmane.comp.db.mysql.java/5501</link>
    <description>&lt;pre&gt;Hello,

While testing my application with MySQL I noticed a difference with 
Oracle's JDBC implementation.  In the following excerpt, I expect the 
call to getString to return the "new-value"

/* Sometimes the application calls moveToInsertRow() to insert a new row 
or next() to update an existing row in the database */
...
resultSet.updateString(2,"new-value");
resultSet.getString(2).equals("new-value");
...
/* Sometimes the database does not need to be updated and the changes 
are canceled */

It works as expected when inserting a new row (calling 
resultSet.moveToInsertRow() before the two lines above).
However, it does not work when updating a row (calling resultSet.next() 
before the the two lines above). In this case the call to getString 
still returns the value in the database.

Is there a way to make getString after updateString to work consistently 
for both uses case?

Thank You,
Dmitry

Sample Code:

import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;

import com.mysql.jdbc.util.BaseBugReport;

public class BugReportVisibilityOfUpdate extends BaseBugReport {
  Connection con;
  Statement stm;
 
  public BugReportVisibilityOfUpdate() {
    super();
  }

  public void setUp() throws Exception {
    con = DriverManager.getConnection(getUrl());
    stm = con.createStatement();
    stm.executeUpdate("CREATE TABLE bug (id INTEGER UNSIGNED NOT 
NULL,value VARCHAR(25), PRIMARY KEY(id));");
    stm.executeUpdate("INSERT INTO bug(id,value) 
VALUES(1,'current-value')");
  }

  public void tearDown() throws Exception {
    con = DriverManager.getConnection(getUrl());
    stm = con.createStatement();
    stm.executeUpdate("DROP TABLE bug");
    stm.close();
  }

  public void runTest() throws Exception {
    con = DriverManager.getConnection(getUrl());
    stm = con.createStatement(ResultSet.TYPE_FORWARD_ONLY, 
ResultSet.CONCUR_UPDATABLE);
    ResultSet rs = null;
   
   
    /* Test Case 1 - Passed. In the rs.moveToInsertRow test, calling 
getString after updateString works as expected */
    try {
      rs = stm.executeQuery("SELECT id, value from bug where id = '2'");
      rs.moveToInsertRow();
      assertTrue("Before update getString should return null", 
rs.getString(2)==null);

      rs.updateString("value", "new-value");
      assertTrue("After update should return 'new-value'", 
rs.getString(2).equals("new-value"));

      rs.close();
    } catch (SQLException e) {
      System.err.println("SQLException: " + e.getMessage());
    }

    /* Test Case 2 - Failed. In the rs.next test, calling getString 
after updateString still returns the value from the database
       instead of the value used in the updateString */
    try {
      rs = stm.executeQuery("SELECT id, value from bug where id = '1'");

      rs.next();

      assertTrue("Before update getString should return 
'current-value'", rs.getString(2).equals("current-value"));

      rs.updateString("value", "new-value");

      /* The following assert failes.  Oracle returns the "new-value" */
      assertTrue("After update should return 'new-value'", 
rs.getString(2).equals("new-value"));

      rs.close();
    } catch (SQLException e) {
      System.err.println("SQLException: " + e.getMessage());
    }
  }

  public static void main(String[] args) throws Exception {
    (new BugReportVisibilityOfUpdate()).run();
  }

}


&lt;/pre&gt;</description>
    <dc:creator>Dmitry Isakbayev</dc:creator>
    <dc:date>2011-05-10T19:26:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.mysql.java/5500">
    <title>DBCP error</title>
    <link>http://permalink.gmane.org/gmane.comp.db.mysql.java/5500</link>
    <description>&lt;pre&gt;Hi All,

 We are frequently getting DBCP error. We have seen this error in
catalina.log &amp;amp; apps log. This issue has started since last 2 -3 days. We
have checked the application code when this error has occured and assure
that there is no connection leakage in code. Mysql server is also running
fine. We have tune memory parameters in mysql, however effectless. Still we
are getting the same error.

 Any suggestion/solution would be appreciated.


 Mysql server version: 5.0.45

JDBC version: mysql-connector-java-5.1.5-bin.jar

apache Tomcat version: 6.0.16


 server.xml parameters are as follows::


 url="jdbc:mysql://hostname:3306/dbname" username="user" password="pass"
maxActive="40" maxIdle="20" maxWait="5000"



 ERROR:


 2011-05-05 16:32:57,666 [ajp-8009-177] ERROR TrainSearchResultCache.java -
Error retrieving Train Search from DB: s-

org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a connection,
pool error Timeout waiting for idle object

        at
org.apache.tomcat.dbcp.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:104)

        at
org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)

        at
com.eos.gds.data.DatabaseManager.getConnection(DatabaseManager.java:73)

        at
com.eos.gds.data.DatabaseManager.getConnection(DatabaseManager.java:60)

............................................

Caused by: java.util.NoSuchElementException: Timeout waiting for idle object

        at
org.apache.tomcat.dbcp.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:958)

        at
org.apache.tomcat.dbcp.dbcp.AbandonedObjectPool.borrowObject(AbandonedObjectPool.java:84)

        at
org.apache.tomcat.dbcp.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:96)

        ... 28 more


  com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications
link failure

 Last packet sent to the server was 24 ms ago.

        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)

        at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

        at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)

        at com.mysql.jdbc.Util.handleNewInstance(Util.java:406)

        at
com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1074)

        at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2873)

        at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2763)

        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3299)

        at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1837)

        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1961)

        at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2543)

        at
com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1737)

        at
com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2022)

        at
com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1940)

        at
com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1925)

        at
org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102)

        at
com.eos.gds.cache.FareQuoteDBCache.storeItinQuotesIntoPresistentCache(FareQuoteDBCache.java:1029)

        at
com.eos.gds.cache.FareQuoteDBCache.processInputQueue(FareQuoteDBCache.java:899)

        at
com.eos.gds.cache.FareQuoteDBCache.access$000(FareQuoteDBCache.java:37)

        at
com.eos.gds.cache.FareQuoteDBCache$1.run(FareQuoteDBCache.java:103)

        at java.lang.Thread.run(Thread.java:619)

Caused by: java.net.SocketException: Socket closed

        at java.net.SocketInputStream.socketRead0(Native Method)

        at java.net.SocketInputStream.read(SocketInputStream.java:129)

        at
com.mysql.jdbc.util.ReadAheadInputStream.fill(ReadAheadInputStream.java:113)

        at
com.mysql.jdbc.util.ReadAheadInputStream.readFromUnderlyingStreamIfNecessary(ReadAheadInputStream.java:160)

        at
com.mysql.jdbc.util.ReadAheadInputStream.read(ReadAheadInputStream.java:188)

        at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:2329)

        at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2774)




&lt;/pre&gt;</description>
    <dc:creator>Dhaval Jaiswal</dc:creator>
    <dc:date>2011-05-06T07:56:13</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.db.mysql.java/5499">
    <title>[HELP] aglet using mysql-connector-java-5.1.14</title>
    <link>http://permalink.gmane.org/gmane.comp.db.mysql.java/5499</link>
    <description>&lt;pre&gt;hi all, iam developing mobile agent using aglet 2.0.2 and
mysql-connector-java-5.1.14 to connect database mysql.
i was create simple code to insert some data to database.
then i compile it and its work, but when i running with tahiti server there
is error and no data insert to my database.
anyone know the problem??

regards,
scifo

*this is error message in console:*

database failure: Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The
driv er has not received any packets from the server.


*this is source code :*

 public void run() {
    System.out.println("Tampil no pencarian");
    String mysqldriver = "com.mysql.jdbc.Driver";
    Connection conn = null;
    Statement st = null;
    ResultSet rset = null;
    String sqlQuery = "INSERT INTO `cobadb`.`customer` (`nama` ,`alamat`
,`umur` ,`email` ,`telepon`) VALUES ( 'dudul', 'tegal', '21', '
dudul&amp;lt; at &amp;gt;yahoo.com', '12234567')";

    try
    {
        Class.forName(mysqldriver);    // koneksi driver database

        conn =
DriverManager.getConnection("jdbc:mysql://localhost/cobadb","root","scifoanggi");
// koneksi ke mySQL
        st = conn.createStatement();
        rset = st.executeUpdate(sqlQuery);    // ekseskusi quey SQL
    }

    catch(ClassNotFoundException e) {
        System.err.println("drive failure: " + e.getMessage());
    }
    catch (SQLException e)
    {
        System.err.println("database failure: "+ e.getMessage());
    }

    finally {
        try
        {    if (rset !=null) rset.close();    }
        catch (SQLException sqle) {}

        try
        {   if (st != null ) st.close();    }
        catch (SQLException sqle) {}

        try
        {   if (conn != null ) conn.close();    }
        catch (SQLException sqle) {}
    }
 }
&lt;/pre&gt;</description>
    <dc:creator>scifo anggy yudianto</dc:creator>
    <dc:date>2011-04-28T10:01:07</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.db.mysql.java">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.db.mysql.java</link>
  </textinput>
</rdf:RDF>

