How do I control the number of database sessions used by MapViewer?
When MapViewer renders a map, it connects to the datasource (an Oracle spatial database) to fetch any data that reside in the database. The connections are managed by the MapViewer server. For a given data source, the maximum number of connections that will be present is determined by the complexity of the map requests and how many mappers are specified for a datasource. For instance, when requesting a map with n predefined themes, MapViewer will automatically create n connections in n threads to load the themes’ data in parallel. For performance reasons, these connections are not closed at the end of the request. Rather they are placed back in a connection pool maintained by MapViewer for that data source. As such, you may observe a large number of sessions open against a particular database user after a series of concurrent complex map requests. The default maximum number of sessions that will remain open on any data source is 100. If you must limit the number of sessions to a smalle
Related Questions
- When migrating the database used by MapViewer, what are the ways to move all the styles, themes, and map definitions in the schema?
- Can the Household Products Database be used in poisoning emergencies instead of calling a poison control center?
- How do I control the number of database sessions used by MapViewer?
