From: Michael Dykman Date: February 24 2012 4:42pm Subject: Re: two 5.1 servers, different behaviour List-Archive: http://lists.mysql.com/mysql/226853 Message-Id: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable That error is coming from neither the MySQL server nor from DBVisualizer. That is coming from your JDBC driver. Check the version of that and research the effect of configuration options. http://dev.mysql.com/doc/refman/5.0/en/connector-j-reference-configuration-= properties.html - michael dykman On Fri, Feb 24, 2012 at 10:44 AM, William Bulley wrote: > I am using DBvisualizer to inspect two MySQL 5.1 databases on two > different systems. =A0The two different systems are nearly identical > in the O/S and the version of MySQL (5.1.58 vs 5.1.60). =A0Both the > systems have MySQL configured in the same way (see below) and are > successfully using MySQL underneath a Perl CGI application. > > mysql5.1.60% cat /usr/local/etc/mysql/my.cnf > [mysqld] > max_allowed_packet =3D 16M > #skip-networking > > mysql5.1.58% cat /usr/local/etc/mysql/my.cnf > [mysqld] > max_allowed_packet =3D 16M > #skip-networking > > I can successfully connect to the 5.1.60 server using DBvisualizer, > but I get the following well-known error when I try to connect to the > 5.1.58 server on the other system: > > =A0 "com.mysql.jdbc.PacketTooBigException: Packet for query is too > =A0 large (7696217 > 1048576). You can change this value on the server > =A0 by setting the max_allowed_packet' variable." > > I have contacted the support folks at DBvisualizer sending them the > following stack trace when the above exception occurs. =A0They have no > clue and suggested I contact the MySQL community which I am now doing. > > =A0=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*= =3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D > > Product: =A0DbVisualizer Personal 8.0 > Build: =A0#1689 (2011/06/16 12:10) > Java VM: =A0OpenJDK Client VM > Java Version: =A01.6.0 > Java Vendor: =A0Sun Microsystems Inc. > OS Name: =A0FreeBSD > OS Arch: =A0i386 > OS Version: =A08.2-STABLE > > 13:32:29 [DEBUG AWT-EventQueue-1 DbVisualizerGUI.?] Init Seconds: 4.630 s= plash display: 1.238 window display: 4.629 > 13:32:39 [DEBUG AWT-EventQueue-1 L.?] Loading class using dynamic ClassLo= ader: com.mysql.jdbc.Driver > 13:32:39 [DEBUG AWT-EventQueue-1 L.?] Loading class using dynamic ClassLo= ader: com.mysql.jdbc.Driver > 13:32:39 [DEBUG Thread-6 G.?] Connecting: myapp test/development server > 13:32:39 [DEBUG Thread-6 L.?] Loading class using dynamic ClassLoader: co= m.mysql.jdbc.Driver > 13:32:39 [DEBUG Thread-6 L.?] Loading class using dynamic ClassLoader: co= m.mysql.jdbc.Driver > 13:32:39 [DEBUG pool-1-thread-1 D.?] RootConnection: Driver.acceptsURL("j= dbc:mysql://xxx.yyy.zzz.www:3306/myapp") > 13:32:39 [DEBUG pool-1-thread-2 D.?] RootConnection: Driver.connect("jdbc= :mysql://xxx.yyy.zzz.www:3306/myapp", {user=3D****, password=3D********}) > 13:32:39 [DEBUG pool-1-thread-2 D.?] RootConnection: EXCEPTION -> com.mys= ql.jdbc.PacketTooBigException: Packet for query is too large (7696217 > 104= 8576). You can change this value on the server by setting the max_allowed_p= acket' variable. > > =A0=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*= =3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D > > I could easily upgrade to 5.1.60 on the failing system, but I'd rather > not have to do that unless that is the called for solution. > > I would be greatful for any hints or suggestions as to how I might go > about correcting this problem. =A0Thank you in advance. > > Regards, > > web... > > -- > William Bulley =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Email: web@stripped= du > > 72 characters width template ----------------------------------------->| > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: =A0 =A0http://lists.mysql.com/mysql > --=20 =A0- michael dykman =A0- mdykman@stripped =A0May the Source be with you.