List:General Discussion« Previous MessageNext Message »
From:Michael Dykman Date:February 24 2012 4:42pm
Subject:Re: two 5.1 servers, different behaviour
View as plain text  
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 <web@stripped> wrote:
> I am using DBvisualizer to inspect two MySQL 5.1 databases on two
> different systems.  The two different systems are nearly identical
> in the O/S and the version of MySQL (5.1.58 vs 5.1.60).  Both 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 = 16M
> #skip-networking
>
> mysql5.1.58% cat /usr/local/etc/mysql/my.cnf
> [mysqld]
> max_allowed_packet = 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:
>
>   "com.mysql.jdbc.PacketTooBigException: Packet for query is too
>   large (7696217 > 1048576). You can change this value on the server
>   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.  They have no
> clue and suggested I contact the MySQL community which I am now doing.
>
>  =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> Product:  DbVisualizer Personal 8.0
> Build:  #1689 (2011/06/16 12:10)
> Java VM:  OpenJDK Client VM
> Java Version:  1.6.0
> Java Vendor:  Sun Microsystems Inc.
> OS Name:  FreeBSD
> OS Arch:  i386
> OS Version:  8.2-STABLE
>
> 13:32:29 [DEBUG AWT-EventQueue-1 DbVisualizerGUI.?] Init Seconds: 4.630 splash
> display: 1.238 window display: 4.629
> 13:32:39 [DEBUG AWT-EventQueue-1 L.?] Loading class using dynamic ClassLoader:
> com.mysql.jdbc.Driver
> 13:32:39 [DEBUG AWT-EventQueue-1 L.?] Loading class using dynamic ClassLoader:
> 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:
> com.mysql.jdbc.Driver
> 13:32:39 [DEBUG Thread-6 L.?] Loading class using dynamic ClassLoader:
> com.mysql.jdbc.Driver
> 13:32:39 [DEBUG pool-1-thread-1 D.?] RootConnection:
> Driver.acceptsURL("jdbc: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=****, password=********})
> 13:32:39 [DEBUG pool-1-thread-2 D.?] RootConnection: EXCEPTION ->
> com.mysql.jdbc.PacketTooBigException: Packet for query is too large (7696217 >
> 1048576). You can change this value on the server by setting the max_allowed_packet'
> variable.
>
>  =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> 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.  Thank you in advance.
>
> Regards,
>
> web...
>
> --
> William Bulley                    
> Email: web@stripped
>
> 72 characters width template ----------------------------------------->|
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:    http://lists.mysql.com/mysql
>



-- 
 - michael dykman
 - mdykman@stripped

 May the Source be with you.
Thread
two 5.1 servers, different behaviourWilliam Bulley24 Feb
  • Re: two 5.1 servers, different behaviourMichael Dykman24 Feb
Re: two 5.1 servers, different behaviourWilliam Bulley24 Feb
  • Re: two 5.1 servers, different behaviourMichael Dykman24 Feb
Re: two 5.1 servers, different behaviourWilliam Bulley24 Feb
  • Re: two 5.1 servers, different behaviourMichael Dykman24 Feb
Re: two 5.1 servers, different behaviourWilliam Bulley24 Feb
  • Re: two 5.1 servers, different behaviourAndrew Moore24 Feb
  • Re: two 5.1 servers, different behaviourMichael Dykman24 Feb
Re: two 5.1 servers, different behaviourWilliam Bulley24 Feb
Re: two 5.1 servers, different behaviourWilliam Bulley24 Feb