Dispatcher Crash and MySQL DB Driver errors

Hi there,

We were tracking down a dispatcher crash today – which we thing we found in a bad configuration for a particular render slave. In the meantime we noticed the following errors in the dispatcher.log:

06/17/2013 17:57:43 – [Mysql DB Driver] DB Query error: Cannot increase Mysql max packet. Falling back to default value. Server error: SESSION variable ‘max_allowed_packet’ is read-only. Use SET GLOBAL to assign the value
06/17/2013 17:57:43 – [Mysql DB Driver] DB Query error: Cannot increase Mysql net buffer length. Falling back to default value. Server error: SESSION variable ‘net_buffer_length’ is read-only. Use SET GLOBAL to assign the value
06/17/2013 17:57:43 – [Core] Connection with database engine (mysql) on localhost successfull
06/17/2013 17:57:43 – [Core] Attempting history database connection(mysql) on localhost (muster_history)
06/17/2013 17:57:43 – [Mysql DB Driver] DB Query error: Cannot increase Mysql max packet. Falling back to default value. Server error: SESSION variable ‘max_allowed_packet’ is read-only. Use SET GLOBAL to assign the value
06/17/2013 17:57:43 – [Mysql DB Driver] DB Query error: Cannot increase Mysql net buffer length. Falling back to default value. Server error: SESSION variable ‘net_buffer_length’ is read-only. Use SET GLOBAL to assign the value

Has anyone else seen this? Is there recommended values for net_buffer_length and max_allowed_packet? Searching other MySQL forums there were recommendations on preferred size and we have increased these accordingly but it seems to make no difference.

ESXi 5.1U1
Windows Server 2012 x64
4 cores
4GB RAM
Muster 7.0.7

TIA,

H4nd0