Can't create a coverage store for an arcsde raster
--------------------------------------------------
Key: GEOS-2570
URL: http://jira.codehaus.org/browse/GEOS-2570
Project: GeoServer
Issue Type: Bug
Components: ArcSDE
Affects Versions: 1.7.1
Environment: Tomcat/6.0.18, JVM 1.6.0_11-b03, Linux CentOS 2.6.24-22-xen, amd64
ArcSDE 9.2.0.11 (SP16) for Oracle 10g build 1271
Reporter: Alain Camus
Assignee: Andrea Aime
Attachments: geoserver.log
When I try to create a coveragestore for an ArcSDE raster using the URI :
sde://username:password@anonymised.com:5161/#ITGI_ADM.RD_TOP50R
I get the error message
"The following exception was thrown: * class org.vfny.geoserver.global.ConfigurationException: Could not obtain a reader for the CoverageDataSet. Please check the CoverageDataSet configuration!"
In /opt/tomcat-6.0/webapps/geoserver/data/logs/geoserver.log, I see "THIS CONNECTION IS LOCKED TO A DIFFERENT THREAD".
If I change "ora-SDE" into a name of server which doesn't exist, I get a specific error about this. Same thing for the port, the table and the username. If I set a random password, I get the same error ("THIS CONNECTION IS LOCKED TO A DIFFERENT THREAD") in the log files. I thought it meant my password was wrong, so I asked the DBA a new username/password combination, and paid attention to the caps, but it's still the same error. Therefor, and because of the error message, I think I can exclude a username or password error.
I'm monitoring the ArcSDE connections, and I see that 2 connections come alive when I get the error. If I delete the coveragestore that I just tried to create, stop geoserver, stop tomcat and halt the machine, they remain alive. The DBA has to kill them.
Creating a datastore on ora-SDE, port 5161, no instance, user and pass same as for the coveragestore works fine. I can even create a featureType on another (vector) table using this datastore.
After creating this featureType, 2 ArcSDE connections are alive, which die when I stop geoserver.
Included the output generated in the log file at the moment of the error.
Alain
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira