Morning,
I've got a problem where my oracle datastores are appearing as 'not
enabled' whenever the geoserver machine is rebooted. I'm guessing the
reason for this is that tomcat (i.e. geoserver) is coming up before
oracle, and so the initial check tells the impatient geoserver the
datastore is not available. It also almost always deletes a
featuretype from my list when this happens, and i have to remember to
manually fix things up whenever the server is rebooted.
Is there a way to disable the startup checks to prevent this
happening, is it considered a bug or it is my problem for having
geoserver alive before its data is ready ?
any ideas would be appreciated.
cheers,
-ivan
Ivan Price ha scritto:
Morning,
I've got a problem where my oracle datastores are appearing as 'not
enabled' whenever the geoserver machine is rebooted. I'm guessing the
reason for this is that tomcat (i.e. geoserver) is coming up before
oracle, and so the initial check tells the impatient geoserver the
datastore is not available. It also almost always deletes a
featuretype from my list when this happens, and i have to remember to
manually fix things up whenever the server is rebooted.
This is a defects that should have been fixed in 1.7.0-RC3
(I assume you're using 1.7.0-RC2):
http://jira.codehaus.org/browse/GEOS-2203
Is there a way to disable the startup checks to prevent this
happening, is it considered a bug or it is my problem for having
geoserver alive before its data is ready ?
We could disable the startup checks, the issue is that most of the
service code is not ready do deal with broken datastores. I fear
for example that the whole WFS/WMS capabilities document would fail to
be generated if only a single data store in the list of those enabled
is not really there.
Can you open a improvement request on jira.codehaus.org, describing
again your problem?
If you can code, most of the enabled checks in 1.7.x are in the
org.geoserver.catalog.util.LegacyCatalogImporter class. You can
disable them and recompile, what happens next is that you will
have to fix also all the code that assumes enabled datastores
are working fine. I expect you'll have to add at least some
extra try/catch in the code, if you're lucky, or rethink the way
information is loaded (delaying that to the point where a feature
type is actually used) in the worst case.
By the frequent reboots and the fact you're having troubles
imposing an order on the services startup I assume you're on
a Windows workstation. There are a few articles out there
talking about how to impose an order on Windows services,
this might be easier thought it seems you can only do that
by hand modifying the registry (ugh):
http://support.microsoft.com/kb/193888
http://kb.adobe.com/selfservice/viewContent.do?externalId=kb400960
http://searchwindowsserver.techtarget.com/tip/0,289483,sid68_gci1313372,00.html
Hope this helps
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.