Hi,
I recommend you to make a new installation and try if you can repeat the error with the demo layers. That way we can see if the trouble is specific for your data or grids or if it is service wide in your environment.
-Jukka Rahkonen-
···
Wilhelm, Dirk wrote:
Hi,
well, i removed the demo layers, so i can’t give you the command with them.
But i used your json string, i just exchanged the layer name, srs and bounds. I double checked that the bounds are inside my layer.
It doesn’t matter if i use json, xml or the gwc seed form.
Without the bounds, it works fine. With the bounds, no luck.
Regards,
Dirk
Von: Rahkonen Jukka (Tike) [mailto:jukka.rahkonen@anonymised.com]
Gesendet: Dienstag, 13. Mai 2014 14:31
An: Wilhelm, Dirk
Betreff: Re: [Geoserver-users] Error with gwc when using curl seedrequest with bounds
Hi,
Could you mail an exact command that fails with some of the Geoserver demo layers?
-Jukka Rahkonen-
Wilhelm, Dirk
Hello,
same effect. With bounds i get an error, without bounds it works.
Regards,
Dirk
Von: Rahkonen Jukka (Tike) [mailto:jukka.rahkonen@anonymised.com]
Gesendet: Dienstag, 13. Mai 2014 13:51
An: Wilhelm, Dirk; ‘geoserver-users@lists.sourceforge.net’
Betreff: Re: [Geoserver-users] Error with gwc when using curl seedrequest with bounds
Hi,
This kind of json seed requests work for us
curl -x cache.company.fi:8888 -v -k -u admin:geoserver -XPOST -H “Content-type: application/json” -d “{‘seedRequest’:{‘name’:‘GWC_seedlayer’,‘bounds’:{‘coords’:{ ‘double’:[‘3000000.0’,‘6600000.0’,‘3100000.0’,‘6700000.0’]}},‘srs’:{‘number’:2393},‘zoomStart’:8,‘zoomStop’:11,‘format’:‘image/png’,‘type’:‘seed’,‘threadCount’:4}}}” http://server.company.fi:80/geoserver/gwc/rest/seed/GWC_seedlayer.json
-Jukka Rahkonen-
Wilhelm, Dirk wrote:
Hello,
i have a problem sending rest request with a seeding request with bounds to the gwc.
A request without bounds works fine, when i add bounds i get an Internal Server error.
Its the same when i try to use the gwc seed form.
I’m using:
Geoserver 2.5
Jdk 1.7.0_45
Tomcat 7
I found a similar thread in the list:
Is upgrading geoserver or dosngrading the java version really the only solution?
Regards,
Dirk