MySQL server - Packets larger than max_allowed_packet are not allowed.

MySQL server - Packets larger than max_allowed_packet are not allowed.

  
Anyone experience this issue when installing outsystems platform on mysql server via configuration tool?
 
  • Windows Server 2008 R2 Enterprise Edition
  • Outsystems platform 9.0.xx.0
  • MySQL Server 5.6.25.0 Community Edition (configured with settings in checklist)
Note: outsystems database created successfully, outsystems session created successfully, but it fails when you click "apply and exit"

 
 
-----------------
  1. Service Center Installer v9.0.xx.0
  2.  
  3. Start installing Service Center v9.0.xx.0...
  4. This operation may take a few minutes to complete...
  5.  
  6. Publishing Extension(s)...
  7. Publishing Extension 'OMLProcessor'...
  8. Publishing Extension 'IntegrationStudio'...
  9. Reading ServiceCenter.oml oml file information...
  10. Adding ServiceCenter eSpace to database...
  11. Message 1
  12.   [Error] MySql.Data.MySqlClient.MySqlException (0x80004005): Packets larger than max_allowed_packet are not allowed.
  13.    at MySql.Data.MySqlClient.MySqlStream.SendPacket(MySqlPacket packet)
  14.    at MySql.Data.MySqlClient.NativeDriver.ExecutePacket(MySqlPacket packetToExecute)
  15.    at MySql.Data.MySqlClient.NativeDriver.SendQuery(MySqlPacket queryPacket)
  16.    at MySql.Data.MySqlClient.Driver.SendQuery(MySqlPacket p)
  17.    at MySql.Data.MySqlClient.Statement.ExecuteNext()
  18.    at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
  19.    at MySql.Data.MySqlClient.MySqlCommand.ExecuteScalar()
  20.    at OutSystems.HubEdition.Extensibility.Data.ExecutionService.BaseExecutionService.ExecuteScalar(IDbCommand cmd)
  21.    at OutSystems.Internal.Db.Command.ExecuteScalar(String description, Boolean isApplication, Boolean skipLog, Boolean applyTransformationsToParameters)
  22.    at OutSystems.HubEdition.RuntimePlatform.DBRuntimePlatformMySQL.ExecuteNonQueryGetIdentity(Command cmd, String idColumnName)
  23.    at OutSystems.HubEdition.ServerCommon.Database.DBCommon.CreateEspaceVersion(Transaction trans, Int32 versionNum, Byte[] oml, Int32 userId, Int32 espaceId, String serviceStudioVersion, String lastUpgradeVersion, String name, String description, String hash, DateTime lastModified, Boolean hasHTTPS, Boolean hasIntegratedAuthentication, Boolean hasSMS, Boolean isUserProvider, String userProviderKey, String userProviderName, String directUpgradeFromHash, String generalHash, JQueryVersion jqueryVersion)
  24.    at #ywf.#xxf.#dxf(Transaction trans, String eSpaceName, Int32 eSpaceId, String filename, String SSVersion, String LastUpgradeVersion, Boolean hasHTTPS, Boolean hasIntegratedAuthentication, Boolean hasSMS, String versionHash, String generalHash)
  25.    at #ywf.#xxf.#jxf(String filename, Int32& eSpaceVersion, Int32& eSpaceId, String& eSpaceName, String& tenantName, ObjectKey& eSpaceSSKey)
  26.    at MySql.Data.MySqlClient.MySqlStream.SendPacket(MySqlPacket packet)
  27.    at MySql.Data.MySqlClient.NativeDriver.ExecutePacket(MySqlPacket packetToExecute)
  28.    at MySql.Data.MySqlClient.NativeDriver.SendQuery(MySqlPacket queryPacket)
  29.    at MySql.Data.MySqlClient.Driver.SendQuery(MySqlPacket p)
  30.    at MySql.Data.MySqlClient.Statement.ExecuteNext()
  31.    at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
  32.    at MySql.Data.MySqlClient.MySqlCommand.ExecuteScalar()
  33.    at OutSystems.HubEdition.Extensibility.Data.ExecutionService.BaseExecutionService.ExecuteScalar(IDbCommand cmd)
  34.    at OutSystems.Internal.Db.Command.ExecuteScalar(String description, Boolean isApplication, Boolean skipLog, Boolean applyTransformationsToParameters)
  35.    at OutSystems.HubEdition.RuntimePlatform.DBRuntimePlatformMySQL.ExecuteNonQueryGetIdentity(Command cmd, String idColumnName)
  36.    at OutSystems.HubEdition.ServerCommon.Database.DBCommon.CreateEspaceVersion(Transaction trans, Int32 versionNum, Byte[] oml, Int32 userId, Int32 espaceId, String serviceStudioVersion, String lastUpgradeVersion, String name, String description, String hash, DateTime lastModified, Boolean hasHTTPS, Boolean hasIntegratedAuthentication, Boolean hasSMS, Boolean isUserProvider, String userProviderKey, String userProviderName, String directUpgradeFromHash, String generalHash, JQueryVersion jqueryVersion)
  37.    at #ywf.#xxf.#dxf(Transaction trans, String eSpaceName, Int32 eSpaceId, String filename, String SSVersion, String LastUpgradeVersion, Boolean hasHTTPS, Boolean hasIntegratedAuthentication, Boolean hasSMS, String versionHash, String generalHash)
  38.    at #ywf.#xxf.#jxf(String filename, Int32& eSpaceVersion, Int32& eSpaceId, String& eSpaceName, String& tenantName, ObjectKey& eSpaceSSKey)

(these values does not seem right?)

Hi Robert,

In the configuration of your MySQL server, you should change the configuration in Networking. Look for max_allowed_packet and set it to 300M.
That should allow the platform to work properly.
I remembered seeing some post about MySQL configuration...
Found it: http://www.outsystems.com/forums/discussion/12536/mysql-integration-issues-in-configuration-tool/

Check there if there is any other configuration settings you may be missing.
Tiago Neves wrote:
Hi Robert,

In the configuration of your MySQL server, you should change the configuration in Networking. Look for max_allowed_packet and set it to 300M.
That should allow the platform to work properly.
 Already tired that, http://www.outsystems.com/NetworkForums/Public.Download_Attachment.aspx?AttachmentId=4176

then restarted the server
  • net stop MySql56
  • net start MySql56
 
Those settings seem good to go...

I see you are using the latest version (5.6.25.0) which was released a few days ago. That release has many changes in the InnoDB, maybe it breaks something with OutSystems Platform.

You'd better check with support or someone else might be able to help out...
Tiago Neves wrote:
Those settings seem good to go...

I see you are using the latest version (5.6.25.0) which was released a few days ago. That release has many changes in the InnoDB, maybe it breaks something with OutSystems Platform.

You'd better check with support or someone else might be able to help out...
 
Tiago

Got 5.6.25.0 to work!
What was wrong then? Any idea?
Tiago Neves wrote:
What was wrong then? Any idea?
 
 Configured the wrong file! configured my-default.ini, instead of my.ini 

Once the correct file was configured everything works! no issues!

(Other than the bug found in configuration tool - it has already been reported)
Ok. Thank God it's Friday ;)
Are you in Australia? A bit late to be working no?
Tiago, yes.. I'm from Sydney, Australia and its 2am here :)