Discussion:
[mapguide-users] Additional monitoring of MapGuide
Gunter Becker
2016-10-21 13:35:48 UTC
Permalink
Hi,

I'm facing a big problem with our application on MGOS 3.0. Once or twice
every day the mgserver.exe stops immediately working without any error
message in MapGuide logfiles (no failure message). IIS log also doesn't give
any hint on that problem. The only error is logged in Windows application
log:



I've already set the logging in serverconfig.ini to the highest logging
level possible but without any result:




OS: Windows 2012, 64Bit, 32GB RAM
MG Server 3.0, approx. 200 FeatureSources of any kind (Shape, SDF, SQLite,
SQL Server, Oracle, WMS) and 400 LayerDefinitions

Is there anything I can do to additionally monitor what's going on with
MapGuide Server?

Any help would be great, cause our customer want to roll back the system to
MGOS 2.4.

Gunter





--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Additional-monitoring-of-MapGuide-tp5291944.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
Rémy Gourrat
2016-10-21 15:45:57 UTC
Permalink
Hi,

Long time ago (2.2, 2.5), i have the same thing when i have a lot of unvalidate geometry in Oracle with KingFdo.

Remy
Gunter Becker
2016-10-25 07:07:54 UTC
Permalink
Hi,

there is just one Oracle FeatureSource and it contains just point features.
So, I think there's little chance for invalid geometries. However, I will
check them.

Thanks Remy

Gunter



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Additional-monitoring-of-MapGuide-tp5291944p5292470.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
Hans Milling
2016-10-24 09:08:06 UTC
Permalink
We also experience this with our WebGIS. We never found the cause of this,
but some of our customers experience this every day and others never
experience it.
My research suggests that if you query the MapGuide server with an expired
session, some errors occur inside MapGuide and at some point it stops
working due to memory leaks or something. Best way to avoid the crashes is
to avoid working with expired MapGuide server sessions. So set the IIS
session timeout to something lower than the MapGuide timeout or have some
keep alive request that triggers both IIS and MapGuide server requests.



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Additional-monitoring-of-MapGuide-tp5291944p5292249.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
Gunter Becker
2016-10-25 07:50:28 UTC
Permalink
Hi Hans,

I also had the suspicion, that expired sessions could cause some problems or
maybe lead to a crash of the server. IIS session timeout is already set to a
lower value then the session timeout of MapGuide and I've already kept them
both alive in our WebGIS. But, I've always realized session timeouts logged
in error.log since the beginning of MGOS. I suppose, that it belongs to
users who leave their computer for a while and when the computers operating
system switches into sleep mode the sessions couldn't kept alive anymore.
When the user starts working again afterwards, then a session timeout could
occur. I have up to 20 or 30 warnings in Windows application.log each day
that could be caused by this issue. Even more when the server crashes.
MapGuide error.log is usually flooded with session timeout errors each day,
so that it is hard to identify the "real" errors.

In a former MapGuide version (can't remember wich one) the user got a
message when a session timeout occurs. That way the user knew that he had to
restart the viewer. But this feature was removed for some reason, I can't
imagine.

Thanks, Gunter



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Additional-monitoring-of-MapGuide-tp5291944p5292480.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
Gunter Becker
2016-10-25 11:09:55 UTC
Permalink
By the way I found another issue which causes the MapGuide Application Pool
in IIS to stop: #2751 <https://trac.osgeo.org/mapguide/ticket/2751#ticket>

Unfortunately it is not the reason for the mgserver.exe crash.

Gunter



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Additional-monitoring-of-MapGuide-tp5291944p5292548.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
jcabrera
2017-03-10 14:21:16 UTC
Permalink
Gunter,

Did you ever find the cause of the server stopping?



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Additional-monitoring-of-MapGuide-tp5291944p5311758.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
Gunter Becker
2017-03-10 17:32:55 UTC
Permalink
No, I am sorry.

Sometimes everything works as expected and sometimes we got a lot of errors
without knowing the reason of these errors. I've got the suspicion, that
when you have a lot of corrupted LayerDefinitions or FeatureSources because
of no more existing or uncorrect linked datasources, then MapGuids is very
vulnerable.

Gunter



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Additional-monitoring-of-MapGuide-tp5291944p5311786.html
Sent from the MapGuide Users mailing list archive at Nabble.com.

Loading...