According to Michael Dykman on Fri, 02/24/12 at 14:10:
>
> *maybe* your router is doing some packet mangling? Wild shot in the dark..
That is worth investigating... :-)
Thanks.
> Perhaps try hitting that 'local' server' from a remote client to see
> if the effect is the same? Is this the one
According to Andrew Moore on Fri, 02/24/12 at 14:03:
>
> To rule out a version issue have you tried another host with the
> problematic version and same/similar config?
No, for two reasons:
a) I just tumbled onto the idea of doing a version upgrade today,
and
b) the amount of work to do as you
On Fri, Feb 24, 2012 at 1:46 PM, William Bulley wrote:
>> Are both servers on the same subnet?
>
> Negative.
*maybe* your router is doing some packet mangling? Wild shot in the dark..
>> Is your DBVisualizer client local to either of these or on the same
>> subnet as one and not another?
>
> Th
To rule out a version issue have you tried another host with the
problematic version and same/similar config?
On Feb 24, 2012 6:47 PM, "William Bulley" wrote:
> According to Michael Dykman on Fri, 02/24/12 at 13:23:
> >
> > At this point, I would not know what else to do except fire up
> > wires
According to Michael Dykman on Fri, 02/24/12 at 13:23:
>
> At this point, I would not know what else to do except fire up
> wireshark and start debugging the packets.
Well, doesn't that beat all, sigh... Now I'm back to square zero... :-(
> Are both servers on the same subnet?
Negative.
> Is
At this point, I would not know what else to do except fire up
wireshark and start debugging the packets.
Are both servers on the same subnet?
Is your DBVisualizer client local to either of these or on the same
subnet as one and not another?
You mentioned a minor version difference between the se
According to Michael Dykman on Fri, 02/24/12 at 12:58:
>
> I see your point. Configuration files aside, what do you get when you
> query the servers themselves with:
>
> show variables like 'max_allowed_packet'
>
> There *might* be something in your start-up scripts overriding that
> config
I see your point. Configuration files aside, what do you get when you
query the servers themselves with:
show variables like 'max_allowed_packet'
There *might* be something in your start-up scripts overriding that
config setting.
- md
On Fri, Feb 24, 2012 at 11:57 AM, William Bulley wrot
According to Michael Dykman on Fri, 02/24/12 at 11:42:
>
> 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/c
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 dykm
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 underneat
11 matches
Mail list logo
