Re: [Geoserver-users] GeoServer Slow to Start with Lots of Namespaces ( > 3h )

2016-12-18 Thread Jaroslav Urik
ring the first run > with JDBC-Config enabled as it reads every resource file, validates it, and > then inserts into the database, but then on subsequent startups the system > is ready almost instantaneously. > > Kevin M. Weiss > Software Engineer > CRITICAL NETWORKS / HARRIS CORPORATIO

Re: [Geoserver-users] GeoServer Slow to Start with Lots of Namespaces ( > 3h )

2016-12-01 Thread Jaroslav Urik
; > > > *Fra:* Jaroslav Urik [mailto:jarda.u...@gmail.com] > *Sendt:* 1. december 2016 14:36 > *Til:* geoserver-users@lists.sourceforge.net > *Emne:* [Geoserver-users] GeoServer Slow to Start with Lots of Namespaces > ( > 3h ) > > > > Hi, > > I have the same

[Geoserver-users] GeoServer Slow to Start with Lots of Namespaces ( > 3h )

2016-12-01 Thread Jaroslav Urik
it starts.. My question is: Is there any way to disable these checks? Or do them only one a month or so? Or is there any other solution? It is quite annoying when server needs to be restarted and people are waiting for it.. Thanks in advance Jaroslav Urik [1] http://osgeo-org.1560.x6.nabble.com

[Geoserver-users] GeoServer startup time (>2h)

2015-10-26 Thread Jaroslav Urik
server accessed via NFS. They are in JPEG2000 format, Geoserver is using Kakadu 6.4 library, has access to 1024MB of RAM (-XX:MaxPermSize=1024m), and the CPU load during startup is ~20%. So, is there any way to speed this up? Maybe to skip some checking of these layers? Thank you Jaroslav Urik

Re: [Geoserver-users] GeoServer startup time (>2h)

2015-10-26 Thread Jaroslav Urik
gt; immediately the sender by telephone, fax or e-mail and delete the > information in this message that has been received in error. The sender > does not give any warranty or accept liability as the content, accuracy or > completeness of sent messages and accepts no responsibility for changes &

[Geoserver-users] GeoServer - kakadu 6.4 problem ( jp2000 )

2015-10-01 Thread Jaroslav Urik
] - Creating a new JP2KFormat. <<< which seems ok to me.. Can anyone please point out where I could have made mistake? I would be grateful for any ideas.. Thank you Jaroslav Urik <http://mapy2.natur.cuni.cz:8080/geoserver/web/?wicket:bookmarkablePage=