Database Software

I have a java mapviewer application. Within the map, I have 2 layers reading off the same point dataset Addresses, both of which are added to the map as dynamic layers, although each is rendered differently and becomes visible at different scales. There are ~50,000 points in the layer, so it's not a large dataset, although spatially, it spans the US. The problem is that the 2nd theme where we use the Addresses dataset, Addresses by Type, whose theme is created using a more complex query and has more complex symbols, really slows down the map -- making the map generation go from ~5 seconds to ~2 minutes - in our production environment. The time it takes to generate this one layer has increased over time, at first the maps were generated in an acceptable amount of time, slowly becoming slower to generate until this point. We can pinpoint this layer as the problem, because when we remove the layer from the map in the application, the maps go back to being rendered in ~5 seconds. The Addresses dataset is continually being updated - existing data is modified, both tabular and spatial, and new locations are added. In our test/dev environment, everything works great, which makes this problem even harder to solve.

The addresses spatial dataset is stored in a separate database on a separate server than the rest of the data, MapViewer, and the java application. However, when we re-boot the server with the application, Mapviewer, and all data but the addresses, the map goes back to generating in an acceptable amount of time, including the Addresses by Type layer. The server with the Address data on it has not been rebooted/restarted. This tells me that the issue isn't with the data, but something with MapViewer. Is there a cache or temp directory that needs to periodically be cleared/deleted with MapViewer? Or any other ideas on how to solve this issue?

We are using MapViewer 10.1.3 and running on a windows server.

Thanks for your help.