Re: [mapguide-users] MySQL connection timing out
I'm having this same issue running MapGuide Server (Version 2.0.2.3011). It looks as though this issue has been resolved (for future a future release ?). I'm new to this community so I don't know how this works, but there is a service ticket for what looks like the same issue... http://trac.osgeo.org/mapguide/ticket/825 What does this mean for me? Do I have to wait for the next release or is there a fix out there somewhere? -Mark George McLean wrote: I left my development server last night thinking things were in pretty good shape but this morning when querying a map no features stored in MySQL and rendered using FDO were displayed. I see in Mapguide's error log that starting at 4:12AM the connection was lost to MySQL. Restarting theMySQL service did not fix the problem but restarting MG did. I have never seen this with MG 1.2 that I am aware of. I see there are settings in MySQL that can extend the connection timeout but I am not sure if this is the best solution. Has anyone else seen this issue and found a solution? I am not sure I completely understand what is happening here. Does MG make a leave a connection open to MySQL? Why would I get a query attempt every hour as shown in the log below? My first attempt to render a map occurred at 08:51:21 as show below but the connection was apparently broken by then? Thanks again, George McLean -- View this message in context: http://n2.nabble.com/MySQL-connection-timing-out-tp1816785p2353948.html Sent from the MapGuide Users mailing list archive at Nabble.com. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
[mapguide-users] MySQL connection timing out
I left my development server last night thinking things were in pretty good shape but this morning when querying a map no features stored in MySQL and rendered using FDO were displayed. I see in Mapguide's error log that starting at 4:12AM the connection was lost to MySQL. Restarting theMySQL service did not fix the problem but restarting MG did. I have never seen this with MG 1.2 that I am aware of. I see there are settings in MySQL that can extend the connection timeout but I am not sure if this is the best solution. Has anyone else seen this issue and found a solution? I am not sure I completely understand what is happening here. Does MG make a leave a connection open to MySQL? Why would I get a query attempt every hour as shown in the log below? My first attempt to render a map occurred at 08:51:21 as show below but the connection was apparently broken by then? Thanks again, George McLean 2008-07-18T04:12:45 Administrator Error: An exception occurred in FDO component. RDBMS: Lost connection to MySQL server during query StackTrace: - MgTimedEventHandler.handle_timeout line 123 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_27.16\mgdev\server\src\core\TimedEventHandler.cpp - MgDataConnectionTimeoutEventHandler.HandleEvent line 89 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_27.16\mgdev\server\src\core\DataConnectionTimeoutEventHandler.cpp - MgFdoConnectionManager.RemoveExpiredFdoConnections line 484 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_27.16\mgdev\server\src\common\manager\FdoConnectionManager.cpp An exception occurred in FDO component. RDBMS: Lost connection to MySQL server during query 2008-07-18T05:12:49 Administrator Error: An exception occurred in FDO component. RDBMS: MySQL server has gone away StackTrace: - MgTimedEventHandler.handle_timeout line 123 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_27.16\mgdev\server\src\core\TimedEventHandler.cpp - MgDataConnectionTimeoutEventHandler.HandleEvent line 89 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_27.16\mgdev\server\src\core\DataConnectionTimeoutEventHandler.cpp - MgFdoConnectionManager.RemoveExpiredFdoConnections line 484 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_27.16\mgdev\server\src\common\manager\FdoConnectionManager.cpp An exception occurred in FDO component. RDBMS: MySQL server has gone away 2008-07-18T06:12:45 Administrator Error: An exception occurred in FDO component. RDBMS: MySQL server has gone away StackTrace: - MgTimedEventHandler.handle_timeout line 123 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_27.16\mgdev\server\src\core\TimedEventHandler.cpp - MgDataConnectionTimeoutEventHandler.HandleEvent line 89 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_27.16\mgdev\server\src\core\DataConnectionTimeoutEventHandler.cpp - MgFdoConnectionManager.RemoveExpiredFdoConnections line 484 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_27.16\mgdev\server\src\common\manager\FdoConnectionManager.cpp An exception occurred in FDO component. RDBMS: MySQL server has gone away 2008-07-18T07:12:45 Administrator Error: An exception occurred in FDO component. RDBMS: MySQL server has gone away StackTrace: - MgTimedEventHandler.handle_timeout line 123 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_27.16\mgdev\server\src\core\TimedEventHandler.cpp - MgDataConnectionTimeoutEventHandler.HandleEvent line 89 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_27.16\mgdev\server\src\core\DataConnectionTimeoutEventHandler.cpp - MgFdoConnectionManager.RemoveExpiredFdoConnections line 484 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_27.16\mgdev\server\src\common\manager\FdoConnectionManager.cpp An exception occurred in FDO component. RDBMS: MySQL server has gone away 2008-07-18T08:12:45 Administrator Error: An exception occurred in FDO component. RDBMS: MySQL server has gone away StackTrace: - MgTimedEventHandler.handle_timeout line 123 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_27.16\mgdev\server\src\core\TimedEventHandler.cpp - MgDataConnectionTimeoutEventHandler.HandleEvent line 89 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_27.16\mgdev\server\src\core\DataConnectionTimeoutEventHandler.cpp - MgFdoConnectionManager.RemoveExpiredFdoConnections line 484 file d:\buildforgeprojects\mapguide_open_source_v2.0\build_27.16\mgdev\server\src\common\manager\FdoConnectionManager.cpp An exception occurred in FDO component. RDBMS: MySQL server has gone away 2008-07-18T08:51:21 127.0.0.1Administrator Error: Failed to stylize layer: Sectionalizer An exception occurred in FDO component. RDBMS: MySQL server has gone away StackTrace: - MgMappingUtil.StylizeLayers line 775 file