![]() So if this happens to you look in the portal content for any suspicious services published around the time things start to play up. Until the next time someone queried that service. The freaky thing was the CPU usage would remain for quite some time after you closed the map, until maybe the service crashed at which time things would go back to normal. It seems that java is running out of memory trying to retrieve this massive dataset and for some reason the logging component goes haywire.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |