OSGeo.org › OSGeo Software and Data Projects › Feature Data Objects (FDO) › FDO Internals

bad behaviour in low memory situation verified on yesterday build from build server #480,

9 messages

bad behaviour in low memory situation verified on yesterday build from build server #480,

Reply Threaded

To verify the low memory behaviour of the server I was rendering the
tiles of our big map
on a 1GB windows server machine using a most recent build from the build
server.

I can observer a relative consistent behaviour now....
First the FDO reader falls over trying to load a large file. (SDF
database access)
After this happened a few times, the MappingService fails to allocate
memory itself.
In the meanwhile SUCCESS gets returned for wrong tiles.

I think the OoM exception inside FDO does not get propagated to MapGuide
correctly nor handled in a useful manner.
I remember seeing some exception free code under the sdf reader....
Similarly the OoM exception does not get handled in a useful manner in
MapGuide.

Generally, the behaviour of the server when memory runs out is now
almost worse than before because the tileserver returns SUCCESS for
wrongly rendered tiles instead of INVALID STREAM HEADER.
I am happy to help but I need help.
I supplied the retry routine for the ByteSink which was a step forward
in stability,
But the underlying problem of this multi-threaded server when it comes
to memory shortage IS NOT SOLVED.

[Approach1]
A wait retry loop around each memory allocation to catch out of memory
exception .... this should serialize memory requests sufficiently to
make things stable. We could create a clever macro for all memory
allocation which would do exactly this.
Also the allocator base class for std library containers can be used for
that. I think an important place would be the FDO readers which open the
few hundred MB files. There is no point in doing that in MapGuide only.
This could be done by propagating more meaningful errors from FDO to
mapguide so this can be dealt with correctly (recognize OoM and attempt
retry) Black boxing FDO and having only a general exception there seems
the wrong way to deal with such problems.

This is a lot of work but I assume that doing that for the few memory
hungry parts will sort most problems. (see also ByteSink)

[Approach2]
The minimal useful workaround would be to have the server return an
error message as a HTTP response or on the tile without creating the
tile in the cache! This way the client layer can attempt to retry later.

# Log Type: Error Log
# Log Parameters: CLIENT,CLIENTIP,USER,ERROR,STACKTRACE
<2009-04-20T13:30:01> 2088
Success: Server started.
<2009-04-20T14:04:41> 5212 192.168.99.99 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - HWY
Cannot establish connection.
StackTrace:
- MgMappingUtil.StylizeLayers line 763 file
c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-20T14:07:28> 5540 192.168.99.99 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers line 763 file
c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-20T14:07:29> 1768 192.168.99.99 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers line 763 file
c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-20T14:23:54> 3380 192.168.99.99 Anonymous
Error: Failed to stylize layer: Feb 08-ABORIG_WA
Out of memory.
bad allocation
StackTrace:
- MgMappingUtil.StylizeLayers line 763 file
c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp
.....
_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

Haris Kurtagic

RE: bad behavior in low memory situation verified on yesterday build from build server #480,

Reply Threaded

I don't think we can do much in FDO. It is about providers what they do
with memory.
I doubt that SDF provider is using lot of memory regardless of size of
SDF file.
I believe, the worst provider regarding memory usage could be KML
provider. It loads whole KML into memory. Although once loaded, FDO
readers created after do not use additional memory.

Where exactly you think is problems with memory allocation. Perhaps it
is in MG when serializing FDO reader, rather in reader itself ?

Haris

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of UV
Sent: Monday, April 20, 2009 6:50 AM
To: MapGuide Internals Mail List; FDO Internals Mail List
Subject: [fdo-internals] bad behaviour in low memory situation verified
on yesterday build from build server #480,

To verify the low memory behaviour of the server I was rendering the
tiles of our big map
on a 1GB windows server machine using a most recent build from the build

server.

I can observer a relative consistent behaviour now....
First the FDO reader falls over trying to load a large file. (SDF
database access)
After this happened a few times, the MappingService fails to allocate
memory itself.
In the meanwhile SUCCESS gets returned for wrong tiles.

I think the OoM exception inside FDO does not get propagated to MapGuide

correctly nor handled in a useful manner.
I remember seeing some exception free code under the sdf reader....
Similarly the OoM exception does not get handled in a useful manner in
MapGuide.

Generally, the behaviour of the server when memory runs out is now
almost worse than before because the tileserver returns SUCCESS for
wrongly rendered tiles instead of INVALID STREAM HEADER.
I am happy to help but I need help.
I supplied the retry routine for the ByteSink which was a step forward
in stability,
But the underlying problem of this multi-threaded server when it comes
to memory shortage IS NOT SOLVED.

[Approach1]
A wait retry loop around each memory allocation to catch out of memory
exception .... this should serialize memory requests sufficiently to
make things stable. We could create a clever macro for all memory
allocation which would do exactly this.
Also the allocator base class for std library containers can be used for

that. I think an important place would be the FDO readers which open the

few hundred MB files. There is no point in doing that in MapGuide only.
This could be done by propagating more meaningful errors from FDO to
mapguide so this can be dealt with correctly (recognize OoM and attempt
retry) Black boxing FDO and having only a general exception there seems
the wrong way to deal with such problems.

This is a lot of work but I assume that doing that for the few memory
hungry parts will sort most problems. (see also ByteSink)

[Approach2]
The minimal useful workaround would be to have the server return an
error message as a HTTP response or on the tile without creating the
tile in the cache! This way the client layer can attempt to retry later.

# Log Type: Error Log
# Log Parameters: CLIENT,CLIENTIP,USER,ERROR,STACKTRACE
<2009-04-20T13:30:01> 2088
Success: Server started.
<2009-04-20T14:04:41> 5212 192.168.99.99 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - HWY
Cannot establish connection.
StackTrace:
- MgMappingUtil.StylizeLayers line 763 file
c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp

<2009-04-20T14:07:28> 5540 192.168.99.99 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers line 763 file
c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp

<2009-04-20T14:07:29> 1768 192.168.99.99 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers line 763 file
c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp

<2009-04-20T14:23:54> 3380 192.168.99.99 Anonymous
Error: Failed to stylize layer: Feb 08-ABORIG_WA
Out of memory.
bad allocation
StackTrace:
- MgMappingUtil.StylizeLayers line 763 file
c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp

.....
_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals
_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

Trevor Wekel-3

RE: [mapguide-internals] bad behaviour in low memory situation verified on yesterday build from build server #480,

Reply Threaded

In reply to this post by UV wild

I suspect we are looking at a memory leak somewhere in the MapGuide code base. I am currently investigating memory leaks in MapGuide and may know more in a couple of days.

UV, were you using a strictly SDF based map? How many tiles were generated before you started running into memory issues? How many layers were on the map? Were you using any of the advanced stylization? I'm just trying to scope the problem a bit.

Thanks,
Trevor

________________________________________
From: [hidden email] [[hidden email]] On Behalf Of UV [[hidden email]]
Sent: Sunday, April 19, 2009 10:50 PM
To: MapGuide Internals Mail List; FDO Internals Mail List
Subject: [mapguide-internals] bad behaviour in low memory situation verified on yesterday build from build server #480,

To verify the low memory behaviour of the server I was rendering the
tiles of our big map
on a 1GB windows server machine using a most recent build from the build
server.

I can observer a relative consistent behaviour now....
First the FDO reader falls over trying to load a large file. (SDF
database access)
After this happened a few times, the MappingService fails to allocate
memory itself.
In the meanwhile SUCCESS gets returned for wrong tiles.

I think the OoM exception inside FDO does not get propagated to MapGuide
correctly nor handled in a useful manner.
I remember seeing some exception free code under the sdf reader....
Similarly the OoM exception does not get handled in a useful manner in
MapGuide.

Generally, the behaviour of the server when memory runs out is now
almost worse than before because the tileserver returns SUCCESS for
wrongly rendered tiles instead of INVALID STREAM HEADER.
I am happy to help but I need help.
I supplied the retry routine for the ByteSink which was a step forward
in stability,
But the underlying problem of this multi-threaded server when it comes
to memory shortage IS NOT SOLVED.

[Approach1]
A wait retry loop around each memory allocation to catch out of memory
exception .... this should serialize memory requests sufficiently to
make things stable. We could create a clever macro for all memory
allocation which would do exactly this.
Also the allocator base class for std library containers can be used for
that. I think an important place would be the FDO readers which open the
few hundred MB files. There is no point in doing that in MapGuide only.
This could be done by propagating more meaningful errors from FDO to
mapguide so this can be dealt with correctly (recognize OoM and attempt
retry) Black boxing FDO and having only a general exception there seems
the wrong way to deal with such problems.

This is a lot of work but I assume that doing that for the few memory
hungry parts will sort most problems. (see also ByteSink)

[Approach2]
The minimal useful workaround would be to have the server return an
error message as a HTTP response or on the tile without creating the
tile in the cache! This way the client layer can attempt to retry later.

# Log Type: Error Log
# Log Parameters: CLIENT,CLIENTIP,USER,ERROR,STACKTRACE
<2009-04-20T13:30:01> 2088
Success: Server started.
<2009-04-20T14:04:41> 5212 192.168.99.99 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - HWY
Cannot establish connection.
StackTrace:
- MgMappingUtil.StylizeLayers line 763 file
c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-20T14:07:28> 5540 192.168.99.99 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers line 763 file
c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-20T14:07:29> 1768 192.168.99.99 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers line 763 file
c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-20T14:23:54> 3380 192.168.99.99 Anonymous
Error: Failed to stylize layer: Feb 08-ABORIG_WA
Out of memory.
bad allocation
StackTrace:
- MgMappingUtil.StylizeLayers line 763 file
c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp
.....
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

Dan Stoica

RE: bad behavior in low memory situation verified on yesterday build from build server #480,

Reply Threaded

In reply to this post by Haris Kurtagic

There is memory leak in the Expression Engine (see Ticket #474) which has been fixed in the Trunk.
Practically all the geometries returned by a spatial query were leaking. This might explain the bad behavior.

And for the fix itself there is a better solution (more consistent with the EE implementation) suggested by Romica.

Dan.

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Haris Kurtagic
Sent: Monday, April 20, 2009 4:01 AM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] bad behavior in low memory situation verified on yesterday build from build server #480,

I don't think we can do much in FDO. It is about providers what they do
with memory.
I doubt that SDF provider is using lot of memory regardless of size of
SDF file.
I believe, the worst provider regarding memory usage could be KML
provider. It loads whole KML into memory. Although once loaded, FDO
readers created after do not use additional memory.

Where exactly you think is problems with memory allocation. Perhaps it
is in MG when serializing FDO reader, rather in reader itself ?

Haris

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of UV
Sent: Monday, April 20, 2009 6:50 AM
To: MapGuide Internals Mail List; FDO Internals Mail List
Subject: [fdo-internals] bad behaviour in low memory situation verified
on yesterday build from build server #480,

To verify the low memory behaviour of the server I was rendering the
tiles of our big map
on a 1GB windows server machine using a most recent build from the build

server.

I can observer a relative consistent behaviour now....
First the FDO reader falls over trying to load a large file. (SDF
database access)
After this happened a few times, the MappingService fails to allocate
memory itself.
In the meanwhile SUCCESS gets returned for wrong tiles.

I think the OoM exception inside FDO does not get propagated to MapGuide

correctly nor handled in a useful manner.
I remember seeing some exception free code under the sdf reader....
Similarly the OoM exception does not get handled in a useful manner in
MapGuide.

Generally, the behaviour of the server when memory runs out is now
almost worse than before because the tileserver returns SUCCESS for
wrongly rendered tiles instead of INVALID STREAM HEADER.
I am happy to help but I need help.
I supplied the retry routine for the ByteSink which was a step forward
in stability,
But the underlying problem of this multi-threaded server when it comes
to memory shortage IS NOT SOLVED.

[Approach1]
A wait retry loop around each memory allocation to catch out of memory
exception .... this should serialize memory requests sufficiently to
make things stable. We could create a clever macro for all memory
allocation which would do exactly this.
Also the allocator base class for std library containers can be used for

that. I think an important place would be the FDO readers which open the

few hundred MB files. There is no point in doing that in MapGuide only.
This could be done by propagating more meaningful errors from FDO to
mapguide so this can be dealt with correctly (recognize OoM and attempt
retry) Black boxing FDO and having only a general exception there seems
the wrong way to deal with such problems.

This is a lot of work but I assume that doing that for the few memory
hungry parts will sort most problems. (see also ByteSink)

[Approach2]
The minimal useful workaround would be to have the server return an
error message as a HTTP response or on the tile without creating the
tile in the cache! This way the client layer can attempt to retry later.

# Log Type: Error Log
# Log Parameters: CLIENT,CLIENTIP,USER,ERROR,STACKTRACE
<2009-04-20T13:30:01> 2088
Success: Server started.
<2009-04-20T14:04:41> 5212 192.168.99.99 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - HWY
Cannot establish connection.
StackTrace:
- MgMappingUtil.StylizeLayers line 763 file
c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp

<2009-04-20T14:07:28> 5540 192.168.99.99 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers line 763 file
c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp

<2009-04-20T14:07:29> 1768 192.168.99.99 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers line 763 file
c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp

<2009-04-20T14:23:54> 3380 192.168.99.99 Anonymous
Error: Failed to stylize layer: Feb 08-ABORIG_WA
Out of memory.
bad allocation
StackTrace:
- MgMappingUtil.StylizeLayers line 763 file
c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp

.....
_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals
_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals
_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

UV wild

Re: bad behavior in low memory situation verified on yesterday build from build server #480,

Reply Threaded

In reply to this post by Haris Kurtagic

Thanks for the input!
Any information regarding such component internals is greatly appreciated.

So far not understanding too much of the details I just made a wild
guess as my test case opens
a 250MB SDF file after which the error occurs.. somewhere... so
depending on the way it is implemented
this could use more or less memory.

So if you suggest that the reader does not allocate lots of memory
except for the serialization in mapguide
we might have a good candidate to start looking for things. Thanks

Cheers
UV

PS We dont use KML in our map but its good to know that this is a memory
hungry component :)

Haris Kurtagic wrote:

> I don't think we can do much in FDO. It is about providers what they do
> with memory.
> I doubt that SDF provider is using lot of memory regardless of size of
> SDF file.
> I believe, the worst provider regarding memory usage could be KML
> provider. It loads whole KML into memory. Although once loaded, FDO
> readers created after do not use additional memory.
>
> Where exactly you think is problems with memory allocation. Perhaps it
> is in MG when serializing FDO reader, rather in reader itself ?
>
> Haris
>
> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of UV
> Sent: Monday, April 20, 2009 6:50 AM
> To: MapGuide Internals Mail List; FDO Internals Mail List
> Subject: [fdo-internals] bad behaviour in low memory situation verified
> on yesterday build from build server #480,
>
> To verify the low memory behaviour of the server I was rendering the
> tiles of our big map
> on a 1GB windows server machine using a most recent build from the build
>
> server.
>
> I can observer a relative consistent behaviour now....
> First the FDO reader falls over trying to load a large file. (SDF
> database access)
> After this happened a few times, the MappingService fails to allocate
> memory itself.
> In the meanwhile SUCCESS gets returned for wrong tiles.
>
> I think the OoM exception inside FDO does not get propagated to MapGuide
>
> correctly nor handled in a useful manner.
> I remember seeing some exception free code under the sdf reader....
> Similarly the OoM exception does not get handled in a useful manner in
> MapGuide.
>
> Generally, the behaviour of the server when memory runs out is now
> almost worse than before because the tileserver returns SUCCESS for
> wrongly rendered tiles instead of INVALID STREAM HEADER.
> I am happy to help but I need help.
> I supplied the retry routine for the ByteSink which was a step forward
> in stability,
> But the underlying problem of this multi-threaded server when it comes
> to memory shortage IS NOT SOLVED.
>
> [Approach1]
> A wait retry loop around each memory allocation to catch out of memory
> exception .... this should serialize memory requests sufficiently to
> make things stable. We could create a clever macro for all memory
> allocation which would do exactly this.
> Also the allocator base class for std library containers can be used for
>
> that. I think an important place would be the FDO readers which open the
>
> few hundred MB files. There is no point in doing that in MapGuide only.
> This could be done by propagating more meaningful errors from FDO to
> mapguide so this can be dealt with correctly (recognize OoM and attempt
> retry) Black boxing FDO and having only a general exception there seems
> the wrong way to deal with such problems.
>
> This is a lot of work but I assume that doing that for the few memory
> hungry parts will sort most problems. (see also ByteSink)
>
> [Approach2]
> The minimal useful workaround would be to have the server return an
> error message as a HTTP response or on the tile without creating the
> tile in the cache! This way the client layer can attempt to retry later.
>
> # Log Type: Error Log
> # Log Parameters: CLIENT,CLIENTIP,USER,ERROR,STACKTRACE
> <2009-04-20T13:30:01> 2088
> Success: Server started.
> <2009-04-20T14:04:41> 5212 192.168.99.99 Anonymous
> Error: Failed to stylize layer: aug 06-ROADS - HWY
> Cannot establish connection.
> StackTrace:
> - MgMappingUtil.StylizeLayers line 763 file
> c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp
>
> <2009-04-20T14:07:28> 5540 192.168.99.99 Anonymous
> Error: Failed to stylize layer: aug 06-ROADS - FWY
> An exception occurred in FDO component.
> An exception occurred in FDO component.
> An error occurred during SDF database access.
> StackTrace:
> - MgMappingUtil.StylizeLayers line 763 file
> c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp
>
> <2009-04-20T14:07:29> 1768 192.168.99.99 Anonymous
> Error: Failed to stylize layer: aug 06-ROADS - MAJ
> An exception occurred in FDO component.
> An exception occurred in FDO component.
> An error occurred during SDF database access.
> StackTrace:
> - MgMappingUtil.StylizeLayers line 763 file
> c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp
>
> <2009-04-20T14:23:54> 3380 192.168.99.99 Anonymous
> Error: Failed to stylize layer: Feb 08-ABORIG_WA
> Out of memory.
> bad allocation
> StackTrace:
> - MgMappingUtil.StylizeLayers line 763 file
> c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp
>
> .....
> _______________________________________________
> fdo-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/fdo-internals
> _______________________________________________
> fdo-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/fdo-internals
>
>

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

zspitzer

Re: RE: [mapguide-internals] bad behaviour in low memory situation verified on yesterday build from build server #480,

Reply Threaded

In reply to this post by Trevor Wekel-3

Trevor,

UV is working with the same map base I have been wokring on. It's
mostly SDF with some roads
still in SHP files. The various label bugs test cases I had filed a
while back contain the most complex
layer definitions

z

On Mon, Apr 20, 2009 at 7:07 PM, Trevor Wekel <[hidden email]> wrote:

> I suspect we are looking at a memory leak somewhere in the MapGuide code base. I am currently investigating memory leaks in MapGuide and may know more in a couple of days.
>
> UV, were you using a strictly SDF based map? How many tiles were generated before you started running into memory issues? How many layers were on the map? Were you using any of the advanced stylization? I'm just trying to scope the problem a bit.
>
> Thanks,
> Trevor
>
> ________________________________________
> From: [hidden email] [[hidden email]] On Behalf Of UV [[hidden email]]
> Sent: Sunday, April 19, 2009 10:50 PM
> To: MapGuide Internals Mail List; FDO Internals Mail List
> Subject: [mapguide-internals] bad behaviour in low memory situation verified on yesterday build from build server #480,
>
> To verify the low memory behaviour of the server I was rendering the
> tiles of our big map
> on a 1GB windows server machine using a most recent build from the build
> server.
>
> I can observer a relative consistent behaviour now....
> First the FDO reader falls over trying to load a large file. (SDF
> database access)
> After this happened a few times, the MappingService fails to allocate
> memory itself.
> In the meanwhile SUCCESS gets returned for wrong tiles.
>
> I think the OoM exception inside FDO does not get propagated to MapGuide
> correctly nor handled in a useful manner.
> I remember seeing some exception free code under the sdf reader....
> Similarly the OoM exception does not get handled in a useful manner in
> MapGuide.
>
> Generally, the behaviour of the server when memory runs out is now
> almost worse than before because the tileserver returns SUCCESS for
> wrongly rendered tiles instead of INVALID STREAM HEADER.
> I am happy to help but I need help.
> I supplied the retry routine for the ByteSink which was a step forward
> in stability,
> But the underlying problem of this multi-threaded server when it comes
> to memory shortage IS NOT SOLVED.
>
> [Approach1]
> A wait retry loop around each memory allocation to catch out of memory
> exception .... this should serialize memory requests sufficiently to
> make things stable. We could create a clever macro for all memory
> allocation which would do exactly this.
> Also the allocator base class for std library containers can be used for
> that. I think an important place would be the FDO readers which open the
> few hundred MB files. There is no point in doing that in MapGuide only.
> This could be done by propagating more meaningful errors from FDO to
> mapguide so this can be dealt with correctly (recognize OoM and attempt
> retry) Black boxing FDO and having only a general exception there seems
> the wrong way to deal with such problems.
>
> This is a lot of work but I assume that doing that for the few memory
> hungry parts will sort most problems. (see also ByteSink)
>
> [Approach2]
> The minimal useful workaround would be to have the server return an
> error message as a HTTP response or on the tile without creating the
> tile in the cache! This way the client layer can attempt to retry later.
>
> # Log Type: Error Log
> # Log Parameters: CLIENT,CLIENTIP,USER,ERROR,STACKTRACE
> <2009-04-20T13:30:01> 2088
> Success: Server started.
> <2009-04-20T14:04:41> 5212 192.168.99.99 Anonymous
> Error: Failed to stylize layer: aug 06-ROADS - HWY
> Cannot establish connection.
> StackTrace:
> - MgMappingUtil.StylizeLayers line 763 file
> c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp
> <2009-04-20T14:07:28> 5540 192.168.99.99 Anonymous
> Error: Failed to stylize layer: aug 06-ROADS - FWY
> An exception occurred in FDO component.
> An exception occurred in FDO component.
> An error occurred during SDF database access.
> StackTrace:
> - MgMappingUtil.StylizeLayers line 763 file
> c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp
> <2009-04-20T14:07:29> 1768 192.168.99.99 Anonymous
> Error: Failed to stylize layer: aug 06-ROADS - MAJ
> An exception occurred in FDO component.
> An exception occurred in FDO component.
> An error occurred during SDF database access.
> StackTrace:
> - MgMappingUtil.StylizeLayers line 763 file
> c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp
> <2009-04-20T14:23:54> 3380 192.168.99.99 Anonymous
> Error: Failed to stylize layer: Feb 08-ABORIG_WA
> Out of memory.
> bad allocation
> StackTrace:
> - MgMappingUtil.StylizeLayers line 763 file
> c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp
> .....
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals_______________________________________________
> fdo-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/fdo-internals
>

--
Zac Spitzer -
http://zacster.blogspot.com
+61 405 847 168
_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

UV wild

Re: RE: [mapguide-internals] bad behaviour in low memory situation verified on yesterday build from build server #480,

Reply Threaded

Some javascript/style in this post has been disabled (why?)

for illustration I enclosed the error access log.
I am still trying to reproduce this with a map that does not have all 140 layers in it....

However this log shows how the server processes tiles.... gets stuck..... carries on ... gets stuck again...
and always returns SUCCESS.

Zac Spitzer wrote:

Trevor,

UV is working with the same map base I have been wokring on. It's
mostly SDF with some roads
still in SHP files. The various label bugs test cases I had filed a
while back contain the most complex
layer definitions

z

On Mon, Apr 20, 2009 at 7:07 PM, Trevor Wekel [hidden email] wrote:

I suspect we are looking at a memory leak somewhere in the MapGuide code base.  I am currently investigating memory leaks in MapGuide and may know more in a couple of days.

UV, were you using a strictly SDF based map?  How many tiles were generated before you started running into memory issues? How many layers were on the map?  Were you using any of the advanced stylization?  I'm just trying to scope the problem a bit.

Thanks,
Trevor

________________________________________
From: [hidden email] [[hidden email]] On Behalf Of UV [[hidden email]]
Sent: Sunday, April 19, 2009 10:50 PM
To: MapGuide Internals Mail List; FDO Internals Mail List
Subject: [mapguide-internals] bad behaviour in low memory situation verified on yesterday build from build server  #480,

To verify the low memory behaviour of the server I was rendering the
tiles of our big map
on a 1GB windows server machine using a most recent build from the build
server.

I can observer a relative consistent behaviour now....
First  the FDO reader falls over trying to load a large file. (SDF
database access)
After this happened a few times, the MappingService fails to allocate
memory itself.
In the meanwhile SUCCESS gets returned for wrong tiles.

I think the OoM exception inside FDO does not get propagated to MapGuide
correctly nor handled in a useful manner.
I remember seeing some exception free code under the sdf reader....
Similarly the OoM exception does not get handled in a useful manner in
MapGuide.

Generally, the behaviour of the server when memory runs out is now
almost worse than before because the tileserver returns SUCCESS for
wrongly rendered tiles instead of INVALID STREAM HEADER.
I am happy to help but I need help.
I supplied the retry routine for the ByteSink which was a step forward
in stability,
But the underlying problem of this multi-threaded server when it comes
to memory shortage IS NOT SOLVED.

[Approach1]
A wait retry loop around each memory allocation to catch out of memory
exception .... this should serialize memory requests sufficiently to
make things stable. We could create a clever macro for all memory
allocation which would do exactly this.
Also the allocator base class for std library containers can be used for
that. I think an important place would be the FDO readers which open the
few hundred MB files. There is no point in doing that in MapGuide only.
This could be done by propagating more meaningful errors from FDO to
mapguide so this can be dealt with correctly (recognize OoM and attempt
retry) Black boxing FDO and having only a general exception there seems
the wrong way to deal with such problems.

This is a lot of work but I assume that doing that for the few memory
hungry parts will sort most problems. (see also ByteSink)

[Approach2]
The minimal useful workaround would be to have the server return an
error message as a HTTP response or on the tile without creating the
tile in the cache! This way the client layer can attempt to retry later.

# Log Type: Error Log
# Log Parameters: CLIENT,CLIENTIP,USER,ERROR,STACKTRACE
<2009-04-20T13:30:01>     2088
 Success: Server started.
<2009-04-20T14:04:41>     5212        192.168.99.99    Anonymous
 Error: Failed to stylize layer: aug 06-ROADS - HWY
       Cannot establish connection.
 StackTrace:
 - MgMappingUtil.StylizeLayers line 763 file
c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-20T14:07:28>     5540        192.168.99.99    Anonymous
 Error: Failed to stylize layer: aug 06-ROADS - FWY
       An exception occurred in FDO component.
       An exception occurred in FDO component.
       An error occurred during SDF database access.
 StackTrace:
 - MgMappingUtil.StylizeLayers line 763 file
c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-20T14:07:29>     1768        192.168.99.99    Anonymous
 Error: Failed to stylize layer: aug 06-ROADS - MAJ
       An exception occurred in FDO component.
       An exception occurred in FDO component.
       An error occurred during SDF database access.
 StackTrace:
 - MgMappingUtil.StylizeLayers line 763 file
c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-20T14:23:54>     3380        192.168.99.99    Anonymous
 Error: Failed to stylize layer: Feb 08-ABORIG_WA
       Out of memory.
       bad allocation
 StackTrace:
 - MgMappingUtil.StylizeLayers line 763 file
c:\ci\mapguide\build\mgdev\server\src\services\mapping\MappingUtil.cpp
.....
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

# Log Type: Access Log
# Log Parameters: CLIENT,CLIENTIP,USER,OPID
<2009-04-22T10:58:49> 3164 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,0,0,15) Success
<2009-04-22T10:58:52> 1980 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,1,1,15) Success
<2009-04-22T10:58:52> 3568 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,0,1,15) Success
<2009-04-22T10:58:53> 1320 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,1,0,15) Success
<2009-04-22T11:06:33> 1160 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,1,1,14) Success
<2009-04-22T11:06:33> 3536 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,1,0,14) Success
<2009-04-22T11:06:33> 1812 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,2,0,14) Success
<2009-04-22T11:06:34> 588 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,0,2,14) Success
<2009-04-22T11:06:35> 2260 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,0,0,14) Success
<2009-04-22T11:06:36> 532 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,0,1,14) Success
<2009-04-22T11:06:37> 2412 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,2,2,14) Success
<2009-04-22T11:06:37> 4044 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,1,2,14) Success
<2009-04-22T11:06:38> 976 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,2,1,14) Success
<2009-04-22T11:08:10> 3568 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,3,2,13) Success
<2009-04-22T11:08:10> 1320 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,1,1,13) Success
<2009-04-22T11:08:10> 1980 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,2,3,13) Success
<2009-04-22T11:08:10> 1844 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,0,1,13) Success
<2009-04-22T11:08:14> 2016 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,0,2,13) Success
<2009-04-22T11:08:14> 3164 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,3,1,13) Success
<2009-04-22T11:08:15> 1160 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,2,1,13) Success
<2009-04-22T11:08:15> 2180 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,1,2,13) Success
<2009-04-22T11:08:15> 4016 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,0,3,13) Success
<2009-04-22T11:08:15> 3832 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,1,3,13) Success
<2009-04-22T11:08:15> 4012 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,2,2,13) Success
<2009-04-22T11:08:15> 3608 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,3,3,13) Success
<2009-04-22T11:08:21> 1812 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,1,4,13) Success
<2009-04-22T11:08:21> 532 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,2,5,13) Success
<2009-04-22T11:08:21> 3536 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,1,5,13) Success
<2009-04-22T11:08:21> 588 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,2,4,13) Success
<2009-04-22T11:08:21> 2412 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,0,5,13) Success
<2009-04-22T11:08:21> 2260 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,0,4,13) Success
<2009-04-22T11:08:22> 1320 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,3,1,13) Success
<2009-04-22T11:08:23> 3568 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,0,0,13) Success
<2009-04-22T11:08:27> 976 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,1,0,13) Success
<2009-04-22T11:08:28> 1844 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,3,0,13) Success
<2009-04-22T11:08:28> 4044 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,2,0,13) Success
<2009-04-22T11:08:29> 3164 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,5,0,13) Success
<2009-04-22T11:08:31> 1980 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,4,0,13) Success
<2009-04-22T11:08:34> 1160 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,5,1,13) Success
<2009-04-22T11:08:35> 2016 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,4,1,13) Success
<2009-04-22T11:08:36> 2180 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,3,2,13) Success
<2009-04-22T11:08:36> 4012 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,3,3,13) Success
<2009-04-22T11:08:45> 1812 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,5,3,13) Success
<2009-04-22T11:08:46> 3832 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,5,2,13) Success
<2009-04-22T11:08:46> 4016 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,4,2,13) Success
<2009-04-22T11:08:47> 3608 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,4,3,13) Success
<2009-04-22T11:08:49> 3536 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,3,5,13) Success
<2009-04-22T11:08:51> 2412 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,4,5,13) Success
<2009-04-22T11:08:51> 1320 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,5,5,13) Success
<2009-04-22T11:08:53> 1844 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,7,9,12) Success
<2009-04-22T11:08:55> 3164 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,9,9,12) Success
<2009-04-22T11:09:25> 4016 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:25> 976 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:25> 1160 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:25> 1980 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:25> 3164 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:25> 1320 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:25> 3536 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:25> 1844 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:25> 4044 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - HWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:25> 2412 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:39> 1320 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - HWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:39> 1844 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - HWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:39> 1160 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - HWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:39> 976 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - HWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:39> 3536 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - HWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:39> 4016 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - HWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:39> 3164 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - HWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:39> 1980 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - HWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:39> 4044 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:39> 2412 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - HWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:41> 2412 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:41> 1980 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:41> 3164 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:41> 1844 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:41> 976 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:41> 3536 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:41> 4016 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:41> 1160 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:48> 4044 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,8,9,12) Success
<2009-04-22T11:09:48> 3164 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,3,5,12) Success
<2009-04-22T11:09:48> 976 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,7,8,12) Success
<2009-04-22T11:09:48> 1844 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,3,4,12) Success
<2009-04-22T11:09:48> 1980 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,9,8,12) Success
<2009-04-22T11:09:48> 4016 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,4,4,12) Success
<2009-04-22T11:09:48> 3536 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,4,5,12) Success
<2009-04-22T11:09:48> 2412 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,4,3,12) Success
<2009-04-22T11:09:48> 1160 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,9,7,12) Success
<2009-04-22T11:09:55> 1320 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,3,3,12) Success
<2009-04-22T11:09:58> 3536 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:58> 3568 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:58> 4044 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:58> 976 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:58> 1844 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:58> 3164 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:58> 4016 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:58> 2412 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:58> 1160 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:09:58> 1980 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - MAJ
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:10:25> 4016 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,1,4,12) Success
<2009-04-22T11:10:26> 1160 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,0,4,12) Success
<2009-04-22T11:10:26> 1980 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,0,3,12) Success
<2009-04-22T11:10:26> 4044 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,2,3,12) Success
<2009-04-22T11:10:26> 1844 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,1,3,12) Success
<2009-04-22T11:10:26> 976 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,2,4,12) Success
<2009-04-22T11:10:26> 3164 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,2,5,12) Success
<2009-04-22T11:10:26> 3536 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,1,5,12) Success
<2009-04-22T11:10:26> 2412 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,0,5,12) Success
<2009-04-22T11:10:26> 3568 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,8,8,12) Success
<2009-04-22T11:10:26> 588 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,4,4,13) Success
<2009-04-22T11:10:26> 2260 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,5,4,13) Success
<2009-04-22T11:10:26> 532 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,3,4,13) Success
<2009-04-22T11:10:31> 4044 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,-1,5,12) Success
<2009-04-22T11:10:31> 4016 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,-1,3,12) Success
<2009-04-22T11:10:32> 1980 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,-1,4,12) Success
<2009-04-22T11:10:41> 3536 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,-1,7,12) Success
<2009-04-22T11:10:41> 1844 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,-1,6,12) Success
<2009-04-22T11:10:42> 2260 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,0,8,12) Success
<2009-04-22T11:10:42> 1160 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,0,9,12) Success
<2009-04-22T11:10:42> 588 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,-1,8,12) Success
<2009-04-22T11:10:42> 532 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,1,8,12) Success
<2009-04-22T11:10:42> 1320 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,-1,9,12) Success
<2009-04-22T11:10:42> 4044 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,1,9,12) Success
<2009-04-22T11:10:43> 2412 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,0,7,12) Success
<2009-04-22T11:10:45> 3568 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,1,7,12) Success
<2009-04-22T11:10:46> 4016 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,-1,6,12) Success
<2009-04-22T11:10:47> 2016 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,5,4,12) Success
<2009-04-22T11:10:47> 3832 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,6,3,12) Success
<2009-04-22T11:10:47> 2180 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,6,5,12) Success
<2009-04-22T11:10:48> 1812 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,5,5,12) Success
<2009-04-22T11:10:48> 4012 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,5,3,12) Success
<2009-04-22T11:10:48> 1844 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,-1,2,12) Success
<2009-04-22T11:10:48> 3608 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,6,4,12) Success
<2009-04-22T11:10:49> 2412 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,0,0,12) Success
<2009-04-22T11:10:50> 1320 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,1,1,12) Success
<2009-04-22T11:10:50> 532 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,-1,1,12) Success
<2009-04-22T11:10:50> 3568 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,1,0,12) Success
<2009-04-22T11:10:50> 4044 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,-1,0,12) Success
<2009-04-22T11:10:50> 588 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,0,1,12) Success
<2009-04-22T11:10:51> 2260 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,0,2,12) Success
<2009-04-22T11:10:52> 976 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,0,6,12) Success
<2009-04-22T11:10:53> 3536 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,0,6,12) Success
<2009-04-22T11:10:54> 1160 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,1,2,12) Success
<2009-04-22T11:10:54> 3164 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,1,6,12) Success
<2009-04-22T11:10:55> 1980 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,1,6,12) Success
<2009-04-22T11:10:57> 3832 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,2,0,12) Success
<2009-04-22T11:10:57> 2412 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,3,0,12) Success
<2009-04-22T11:11:00> 1812 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,2,1,12) Success
<2009-04-22T11:11:03> 1320 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,3,1,12) Success
<2009-04-22T11:11:05> 2260 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,4,0,12) Success
<2009-04-22T11:11:06> 3568 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,3,2,12) Success
<2009-04-22T11:11:07> 4012 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,2,2,12) Success
<2009-04-22T11:11:08> 1160 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,4,2,12) Success
<2009-04-22T11:11:08> 3536 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,4,1,12) Success
<2009-04-22T11:10:19> 1160 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:10:19> 2412 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:10:19> 3536 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:10:19> 1980 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:10:19> 3568 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:10:19> 2260 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:10:19> 1844 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:10:19> 3832 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - HWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:10:19> 4044 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:10:19> 2180 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - HWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:10:19> 976 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:10:19> 1812 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - HWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:10:19> 3608 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - HWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:10:20> 532 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:10:20> 588 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:10:20> 4016 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:10:20> 2016 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - HWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:10:20> 4012 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - HWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:10:20> 3164 192.168.99.6 Anonymous
Error: Failed to stylize layer: aug 06-ROADS - FWY
An exception occurred in FDO component.
An exception occurred in FDO component.
An error occurred during SDF database access.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:11:10> 3832 192.168.99.6 Anonymous
Error: Failed to stylize layer: Oct_07-WORLD_HERITAGE - GREAT BARRIER REEF MARINE PARK
Out of memory.
bad allocation
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:11:10> 2412 192.168.99.6 Anonymous
Error: Failed to stylize layer: Oct_07-WORLD_HERITAGE - GREAT BARRIER REEF MARINE PARK
Out of memory.
bad allocation
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:11:12> 976 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,8,0,12) Success
<2009-04-22T11:11:15> 2180 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,6,0,12) Success
<2009-04-22T11:11:18> 532 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,7,0,12) Success
<2009-04-22T11:11:25> 1980 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,5,0,12) Success
<2009-04-22T11:11:27> 4016 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,5,1,12) Success
<2009-04-22T11:11:27> 1844 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,6,1,12) Success
<2009-04-22T11:11:28> 2412 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,8,1,12) Success
<2009-04-22T11:11:28> 3608 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,6,2,12) Success
<2009-04-22T11:11:28> 2016 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,5,2,12) Success
<2009-04-22T11:11:29> 588 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,7,1,12) Success
<2009-04-22T11:11:30> 4044 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,7,2,12) Success
<2009-04-22T11:11:30> 3832 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,8,2,12) Success
<2009-04-22T11:11:37> 3568 192.168.99.6 Anonymous
Error: Failed to stylize layer: Oct_07-WORLD_HERITAGE - GREAT BARRIER REEF MARINE PARK
Out of memory.
bad allocation
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:11:37> 4012 192.168.99.6 Anonymous
Error: Failed to stylize layer: Oct_07-WORLD_HERITAGE - GREAT BARRIER REEF MARINE PARK
Out of memory.
bad allocation
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:11:38> 1320 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,10,0,12) Success
<2009-04-22T11:11:38> 2260 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,9,0,12) Success
<2009-04-22T11:11:38> 4012 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,10,1,12) Success
<2009-04-22T11:11:38> 3536 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,9,1,12) Success
<2009-04-22T11:11:38> 1160 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,10,2,12) Success
<2009-04-22T11:11:40> 3568 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,9,2,12) Success
<2009-04-22T11:11:41> 4016 192.168.99.6 Anonymous
Error: Failed to stylize layer: Oct_07-WORLD_HERITAGE - GREAT BARRIER REEF MARINE PARK
Out of memory.
bad allocation
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:11:41> 1980 192.168.99.6 Anonymous
Error: Failed to stylize layer: Oct_07-WORLD_HERITAGE - GREAT BARRIER REEF MARINE PARK
Out of memory.
bad allocation
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:11:41> 2412 192.168.99.6 Anonymous
Error: Failed to stylize layer: Oct_07-WORLD_HERITAGE - GREAT BARRIER REEF MARINE PARK
Out of memory.
bad allocation
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:11:41> 1844 192.168.99.6 Anonymous
Error: Failed to stylize layer: Oct_07-WORLD_HERITAGE - GREAT BARRIER REEF MARINE PARK
Out of memory.
bad allocation
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:11:57> 532 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,10,3,12) Success
<2009-04-22T11:11:59> 3164 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,9,3,12) Success
<2009-04-22T11:12:00> 4016 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,8,3,12) Success
<2009-04-22T11:12:01> 2180 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,9,4,12) Success
<2009-04-22T11:12:03> 1844 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,7,4,12) Success
<2009-04-22T11:12:03> 2412 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,7,3,12) Success
<2009-04-22T11:12:03> 1980 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,8,4,12) Success
<2009-04-22T11:12:03> 976 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,10,4,12) Success
<2009-04-22T11:12:04> 3608 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,6,3,12) Success
<2009-04-22T11:12:04> 2016 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,6,4,12) Success
<2009-04-22T11:12:04> 588 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,5,2,12) Success
<2009-04-22T11:12:04> 588 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,5,4,12) Success
<2009-04-22T11:12:04> 1812 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,5,3,12) Success
<2009-04-22T11:12:04> 1320 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,4,3,12) Success
<2009-04-22T11:12:04> 2260 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,4,4,12) Success
<2009-04-22T11:12:04> 4012 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,3,3,12) Success
<2009-04-22T11:12:04> 1160 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,2,4,12) Success
<2009-04-22T11:12:04> 3536 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,3,4,12) Success
<2009-04-22T11:12:05> 3568 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,-1,4,12) Success
<2009-04-22T11:12:05> 532 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,-1,5,12) Success
<2009-04-22T11:12:06> 3164 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,3,5,12) Success
<2009-04-22T11:12:06> 4016 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,4,5,12) Success
<2009-04-22T11:12:06> 2180 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,5,5,12) Success
<2009-04-22T11:12:06> 1844 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,6,5,12) Success
<2009-04-22T11:12:06> 3608 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,10,3,12) Success
<2009-04-22T11:12:06> 2016 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,10,4,12) Success
<2009-04-22T11:12:07> 1812 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,9,7,12) Success
<2009-04-22T11:12:08> 1320 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,10,7,12) Success
<2009-04-22T11:12:10> 3832 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,10,6,12) Success
<2009-04-22T11:12:22> 588 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,10,5,12) Success
<2009-04-22T11:12:22> 2412 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,7,5,12) Success
<2009-04-22T11:12:23> 1980 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,8,5,12) Success
<2009-04-22T11:12:24> 3536 192.168.99.6 Anonymous
Error: Failed to stylize layer: Oct_07-WORLD_HERITAGE - GREAT BARRIER REEF MARINE PARK
An exception occurred in FDO component.
An unclassified exception occurred.
StackTrace:
- MgMappingUtil.StylizeLayers() line 809 file d:\desktop\mapguide\src\mgdev\server\src\services\mapping\MappingUtil.cpp
<2009-04-22T11:12:24> 976 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,9,5,12) Success
<2009-04-22T11:12:24> 4044 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,9,6,12) Success
<2009-04-22T11:12:24> 3164 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,7,5,12) Success
<2009-04-22T11:12:34> 1844 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,6,7,12) Success
<2009-04-22T11:12:36> 532 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,7,7,12) Success
<2009-04-22T11:12:42> 2180 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,6,6,12) Success
<2009-04-22T11:12:43> 4016 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,7,6,12) Success
<2009-04-22T11:12:43> 1160 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,8,6,12) Success
<2009-04-22T11:12:43> 3536 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,8,7,12) Success
<2009-04-22T11:12:44> 3608 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,5,5,12) Success
<2009-04-22T11:12:44> 2412 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,4,5,12) Success

<2009-04-22T11:12:44> 976 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,3,5,12) Success
<2009-04-22T11:12:45> 2412 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,4,7,12) Success
<2009-04-22T11:12:46> 2260 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,2,7,12) Success
<2009-04-22T11:12:46> 4044 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,3,7,12) Success
<2009-04-22T11:12:49> 1320 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,5,7,12) Success
<2009-04-22T11:12:52> 588 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,4,6,12) Success
<2009-04-22T11:12:53> 976 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,3,6,12) Success
<2009-04-22T11:12:53> 1812 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,5,6,12) Success
<2009-04-22T11:12:53> 4012 192.168.99.6 Anonymous GetTile.1.2.0:5(Library://MAPS/MAP.MapDefinition,BASE,2,6,12) Success
<2009-04-22T11:12:58> 684
Success: Server stopped.

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

UV wild

Re: RE: [mapguide-internals] bad behaviour in low memory situation build r3838

Reply Threaded

Hi all,

I rerun the tile generation on my small machine..... and the server
eventually reports FAILURE on the getTile requests...

but still too late.....

the exceptions log look the same as before..... the exception occurs and
some layers dont get rendered...
the tile gets returned without an error message!!

the first thing i missing the labels while the map is till ok.... then
it carries on and on and looses more and more layers....

Sorry but this is not done yet.

Please tell me what else I can do to help.

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

Traian Stanev

RE: RE: [mapguide-internals] bad behaviour in low memory situation build r3838

Reply Threaded

Did you try reducing the number of simultaneous connections or the thread pool size in the serverconfig.ini?

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of UV
Sent: Thursday, April 23, 2009 9:07 PM
To: FDO Internals Mail List
Subject: Re: [fdo-internals] RE: [mapguide-internals] bad behaviour in low memory situation build r3838

Hi all,

I rerun the tile generation on my small machine..... and the server
eventually reports FAILURE on the getTile requests...

but still too late.....

the exceptions log look the same as before..... the exception occurs and
some layers dont get rendered...
the tile gets returned without an error message!!

the first thing i missing the labels while the map is till ok.... then
it carries on and on and looses more and more layers....

Sorry but this is not done yet.

Please tell me what else I can do to help.

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals
_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals