Hi, More comments about this ticket. We're using ms4w 3.0 beta 11 (DEVELOPMENT) as commented previously, which includes MapServer 5.6.1 version. In the beginning we started using ms4w 2.3.1 (STABLE), which includes MapServer 5.2.1. We've installed again the STABLE version with same DB server, same data, same WMS configuration and the error is not reproduced anymore.
We've noticed that the ogr_OCI.dll file is different. It could be posible that problem could be there?? Or it's more likely to be a bug in MapServer's code?? Thanks. -----Mensaje original----- De: mapserver-users-boun...@lists.osgeo.org [mailto:mapserver-users-boun...@lists.osgeo.org] En nombre de Sumit Sharma Enviado el: jueves, 23 de septiembre de 2010 16:17 Para: mapserver-users@lists.osgeo.org Asunto: [mapserver-users] Re: Coments about the Tickedt 3541 Initially this bug appears random to me as well, but it is certainly not. However, there is surely some loophole in OCI, and that bug is exploited by MapServer. I have posted this bug in Oracle forum as well, but no luck as of now. As Alan is already able to verify this behavior, hopefully we will get some patch soon ... :-) -Sumit -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/Coments-about-the-Tickedt-3541-tp 5558012p5563227.html Sent from the Mapserver - User mailing list archive at Nabble.com. _______________________________________________ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users _______________________________________________ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users