Hi,
I may have a curious problem. But as I use the geotools DataStore to
connect geoserver to other services (i.e. WPS), I always get a problem,
if geoserver and the other service (WPS) are running on the same tomcat
instance. In case of geoserver 1.3.3 the DataStores are populated during
geoserver/tomcat start-up. But as tomcat is trying to start geoserver
and the dataStores are sending requests to initialize the registered
DataStores, the other services on that tomcat instance are not
responding. So geoserver is just staying idle while waiting that the
DataStore is ready. I am aware of the fact, that this is somehow also a
tomcat problem, because tomcat is not responding to anything while
start-up, I guess.
I could imagine, that this problem is not completely new to you, as the
same problem might occur in WFSDataStores or so (when trying to connect
to a WFS on the same tomcat instance). Do you have any idea how to solve
this? Will this problem be solved in geoserver 1.4?
Cheers
Theodor
ITC, Enschede
Department of Geo Information Processing PO. Box 6 7500 AA Enschede the
Netherlands
Theodor Foerster ha scritto:
Hi,
I may have a curious problem. But as I use the geotools DataStore to
connect geoserver to other services (i.e. WPS), I always get a problem,
if geoserver and the other service (WPS) are running on the same tomcat
instance. In case of geoserver 1.3.3 the DataStores are populated during
geoserver/tomcat start-up. But as tomcat is trying to start geoserver
and the dataStores are sending requests to initialize the registered
DataStores, the other services on that tomcat instance are not
responding. So geoserver is just staying idle while waiting that the
DataStore is ready. I am aware of the fact, that this is somehow also a
tomcat problem, because tomcat is not responding to anything while
start-up, I guess.
I could imagine, that this problem is not completely new to you, as the
same problem might occur in WFSDataStores or so (when trying to connect
to a WFS on the same tomcat instance). Do you have any idea how to solve
this?
Unfoturnately it's the first time I hear about this problem, basically
because no-one is running two different WFS in the same tomcat (doesn't
make much sense to me). Anyways, I see the issue, you have a separate
data provider that does not fit into geoserver and I guess you've
written a datastore to communicate with it.
The only way I can think of solving this would be to have geoserver
lazily load the datastore information, to allow full startup before
caring about feature types.
Will this problem be solved in geoserver 1.4?
No, I guess it's already too late for 1.4.0, 1.4.0rc3 is almost out
and if no big bugs show up we'll release it unchanged as 1.4.0.
We may try to tackle this for 1.4.1 thought, so please file a Jira
issue about this problem.
Cheers
Andrea
Unfoturnately it's the first time I hear about this problem, basically
because no-one is running two different WFS in the same tomcat (doesn't
make much sense to me).
I regularly come across the desire to do this. In fact I'd say most deploying agencies have to deal with this. A classic case is deploying a stable version for a range of data products, and a less stable newer version or branch to support some significant feature fix or enhancement for certain data. Another common case is multiple custodians of data products within an organisation, having to deal with a very very slow deployment turn-around time - getting another Tomcat visible through a firewall means months of delay and generation of business cases etc, whereas if they could just maintain thier own geoserver instances, life would be good!
The reason you dont hear about it much is that it doesnt work. I have seen it on the threads a few times, people just go away muttering very early on in the process rather than make a lot of noise.
Rob A