Hi Steve, I'm now not sure what the problem is, but it seems to be triggered by character length in the NAME attribute. We think its triggering some kind of memory problem. Sorry about the vagueness but its really difficult to narrow it down. The problem just seems to affect the xml returned by the GetCapabilities call, Testing with shp2img we can still get a valid image even when the capabilities doc breaks.
With 1 service, the memory problem occurred when the char length of NAME was over 81. The strange thing was that if I tried to name another layer in the same service with a name 81 characters long the service broke again, but worked if I reduced this to 80 characters. Then same again for another layer, I had to reduce the name length to 79. However this was not the case for a different service where the character lengths needed to break the service (return an invalid xml doc) were completely different. So because its not reproduceable I haven't included a mapfile with test data. I do include a txt file with some of the apache error log though (we get nothing from the mapserver error log). Also calls using 1.3.0 and 1.1.1 both return invalid docs. We're going to try 5.6.6 to see if that makes a difference. If we make a breakthrough or manage to make this reproduceable I'll let you know. Sorry I couldn't give more , or more precise info. You may be able to reproduce it with one of your own services, just make one of the layer names very long! Best Regards Tom http://osgeo-org.1803224.n2.nabble.com/file/n5965802/stacktraces.mapserver.zip stacktraces.mapserver.zip -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/Character-Limit-for-NAME-and-GROUP-tp5922135p5965802.html Sent from the Mapserver - User mailing list archive at Nabble.com. _______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
