Opened 13 years ago
Last modified 13 years ago
#3960 reopened defect
msOGRFileOpen(): OGR error. Open failed for OGR connection in layer
Reported by: | MapServer31 | Owned by: | dmorissette |
---|---|---|---|
Priority: | highest | Milestone: | 5.6.4 release |
Component: | OGR Support | Version: | unspecified |
Severity: | blocker | Keywords: | |
Cc: |
Description
Hi, Sometime, MapServer crash with this error : msOGRFileOpen(): OGR error. Open failed for OGR connection in layer `LOCALIZED_BLOCKS'. File not found or unsupported format.
And we need to recycle the pool IIS.
We use a connection to an oracle database (11gR2) via an instant client 11g.
An idea ? Thanks
Attachments (1)
Change History (3)
comment:1 by , 13 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 by , 13 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
Thanks for your response.
All Oracle environment variables and TNS are ok. We made tests with 'ogrinfo' and 'ogr2ogr' and it worked fine. We can’t reproduce the crash all the time.
Our environment is :
- Windows 2008 R2 x64 / IIS 7.5 / FastCGI
- MapServer 5.6.4 / GDAL 1.7.2 compiled by Tamas Szekeres
- Oracle client 11.2.0.1
The layer works mostly but crashs randomly. The result of the crash is the error in the log : msOGRFileOpen(): OGR error. Open failed for OGR connection in layer `LOCALIZED_BLOCKS'. File not found or unsupported format.
IIS logs do not mention the error, neither Windows Log, neither Oracle Client logs.
Attached a simplified version of the layer.
Thanks
Does your OGR installation have Oracle enabled and are all Oracle environment variables available to the Apache process running MapServer?
Anyway, since this error happens with an OGR connection, the first step would be to ensure that 'ogrinfo' and 'ogr2ogr' work with the same DB/layer connection. If you could reproduce the crash with OGR that would be best... and then report the issue to the GDAL/OGR project.
Closing as invalid for now since there is no evidence of a MapServer bug in the information provided. Please reopen with all info/data required to reproduce the issue AFTER you have tested with OGR directly and confirmed that your Apache/MapServer configuration is correct.