Opened 17 years ago
Last modified 17 years ago
#1977 closed defect
OGR support is not threadsafe in MapServer — at Version 3
Reported by: | Owned by: | warmerdam | |
---|---|---|---|
Priority: | high | Milestone: | 5.0 release |
Component: | OGR Support | Version: | 5.0 |
Severity: | normal | Keywords: | threads |
Cc: | dmorissette |
Description (last modified by )
When using MapServer in a multi-threaded application (such as an ASP.NET application) ORG is not thread safe during operations that access the same data. MapServer seems to be a lot "more" thread safe with shapefiles, which leads me to believe that the issue is with OGR.
Change History (3)
comment:2 by , 17 years ago
> Generally speaking OGR is not considered thread safe, and there are some > very serious and well known thread safety issues with the GetFieldAsString() > method on the OGRFeature. This issue has been fixed when GDAL RFC 6 was applied. But I'm sure it was not the only problem to be handled. > There needs to be a "big lock" around OGR in MapServer similar to the one > already implemented around GDAL. It should be considered as a makeshift for now, and the usage of the static variables in OGR should be reconsidered in the future.
comment:3 by , 17 years ago
Cc: | added |
---|---|
Description: | modified (diff) |
Milestone: | → 5.0 release |
Note:
See TracTickets
for help on using tickets.