Menu
▾
▴
geowebcache-users — A list for GeoWebCache end users
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
(16) |
Mar
(19) |
Apr
(50) |
May
(20) |
Jun
(12) |
Jul
(21) |
Aug
(8) |
Sep
(21) |
Oct
(14) |
Nov
(42) |
Dec
(63) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(57) |
Feb
(61) |
Mar
(78) |
Apr
(25) |
May
(28) |
Jun
(76) |
Jul
(51) |
Aug
(64) |
Sep
(48) |
Oct
(46) |
Nov
(61) |
Dec
(19) |
| 2010 |
Jan
(35) |
Feb
(29) |
Mar
(40) |
Apr
(52) |
May
(58) |
Jun
(34) |
Jul
(49) |
Aug
(23) |
Sep
(47) |
Oct
(45) |
Nov
(42) |
Dec
(31) |
| 2011 |
Jan
(34) |
Feb
(34) |
Mar
(35) |
Apr
(29) |
May
(42) |
Jun
(55) |
Jul
(45) |
Aug
(48) |
Sep
(24) |
Oct
(34) |
Nov
(29) |
Dec
(15) |
| 2012 |
Jan
(31) |
Feb
(44) |
Mar
(46) |
Apr
(19) |
May
(23) |
Jun
(12) |
Jul
(26) |
Aug
(26) |
Sep
(8) |
Oct
(18) |
Nov
(18) |
Dec
(2) |
| 2013 |
Jan
(9) |
Feb
(12) |
Mar
(11) |
Apr
(8) |
May
(2) |
Jun
(1) |
Jul
(5) |
Aug
(13) |
Sep
(3) |
Oct
(14) |
Nov
(3) |
Dec
(3) |
| 2014 |
Jan
(10) |
Feb
(13) |
Mar
(14) |
Apr
(2) |
May
(11) |
Jun
(12) |
Jul
(9) |
Aug
(7) |
Sep
(5) |
Oct
(3) |
Nov
(4) |
Dec
(2) |
| 2015 |
Jan
(3) |
Feb
(7) |
Mar
(20) |
Apr
(7) |
May
(13) |
Jun
(15) |
Jul
(3) |
Aug
(19) |
Sep
(4) |
Oct
(3) |
Nov
(4) |
Dec
(2) |
| 2016 |
Jan
(3) |
Feb
(3) |
Mar
(4) |
Apr
(4) |
May
(7) |
Jun
(8) |
Jul
(5) |
Aug
(1) |
Sep
(2) |
Oct
(6) |
Nov
(1) |
Dec
(5) |
| 2017 |
Jan
(2) |
Feb
(6) |
Mar
(1) |
Apr
(3) |
May
(5) |
Jun
(8) |
Jul
|
Aug
(1) |
Sep
(6) |
Oct
(4) |
Nov
(2) |
Dec
|
| 2018 |
Jan
(5) |
Feb
(3) |
Mar
(2) |
Apr
(3) |
May
(1) |
Jun
(3) |
Jul
|
Aug
(7) |
Sep
(4) |
Oct
(2) |
Nov
(1) |
Dec
|
| 2019 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
(2) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(5) |
| 2020 |
Jan
(1) |
Feb
(7) |
Mar
(1) |
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(5) |
Oct
(4) |
Nov
(2) |
Dec
(15) |
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(5) |
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
(6) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(3) |
Dec
(1) |
| 2024 |
Jan
(3) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(3) |
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2026 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Andrea A. <and...@ge...> - 2026-07-13 13:29:45
|
Hi Ian, it's actually a bunch of pages... I've attempted a fix here: https://github.com/GeoWebCache/geowebcache/pull/1557 Cheers Andrea On Mon, Jul 13, 2026 at 1:59 PM Ian Turton <ijt...@gm...> wrote: > I think the recommendation is for tomcat 11 now, please make an edit to > the page. > > Ian > > On Mon, 13 Jul 2026 at 12:50, Troels Arvin via Geowebcache-users < > geo...@li...> wrote: > >> In the release notes at >> https://github.com/GeoWebCache/geowebcache/releases#release-2.0.0 it >> states that GWC 2 uses Jakarta EE 11. Doesn't this mean that GWC 2 nees >> to be at Tomcat 10 or newer? >> >> I'm asking because at >> >> https://geowebcache.osgeo.org/docs/current/installation/prerequisites/linux.html#apache-tomcat >> it states that one should use Tomcat 9, which I think cannot be the case >> any more? >> >> -- >> Troels >> >> >> >> _______________________________________________ >> Geowebcache-users mailing list >> Geo...@li... >> https://lists.sourceforge.net/lists/listinfo/geowebcache-users >> > > > -- > Ian Turton > _______________________________________________ > Geowebcache-users mailing list > Geo...@li... > https://lists.sourceforge.net/lists/listinfo/geowebcache-users > |
|
From: Ian T. <ijt...@gm...> - 2026-07-13 11:58:24
|
I think the recommendation is for tomcat 11 now, please make an edit to the page. Ian On Mon, 13 Jul 2026 at 12:50, Troels Arvin via Geowebcache-users < geo...@li...> wrote: > In the release notes at > https://github.com/GeoWebCache/geowebcache/releases#release-2.0.0 it > states that GWC 2 uses Jakarta EE 11. Doesn't this mean that GWC 2 nees > to be at Tomcat 10 or newer? > > I'm asking because at > > https://geowebcache.osgeo.org/docs/current/installation/prerequisites/linux.html#apache-tomcat > it states that one should use Tomcat 9, which I think cannot be the case > any more? > > -- > Troels > > > > _______________________________________________ > Geowebcache-users mailing list > Geo...@li... > https://lists.sourceforge.net/lists/listinfo/geowebcache-users > -- Ian Turton |
|
From: Troels A. <tr...@ar...> - 2026-07-13 11:50:36
|
In the release notes at https://github.com/GeoWebCache/geowebcache/releases#release-2.0.0 it states that GWC 2 uses Jakarta EE 11. Doesn't this mean that GWC 2 nees to be at Tomcat 10 or newer? I'm asking because at https://geowebcache.osgeo.org/docs/current/installation/prerequisites/linux.html#apache-tomcat it states that one should use Tomcat 9, which I think cannot be the case any more? -- Troels |
|
From: Troels A. <tr...@ar...> - 2026-07-07 13:20:59
|
Hello, I've started setting up my first GWC 2 installation, using a WAR file installation into the Tomcat 11 which ships with Debian 13. However, I get a 403 error when accessing http://servername:8080/geowebcache/ : HTTP Status 403 ? Forbidden Description The server understood the request but refuses to authorize it. For now, the installation is internal and not adjusted at all, so I'm logging in as user "geowebcache" with password "secured". I've never seen the same with previous GeoWebCache installations. In Tomcat's access log, the following is seen: 10.x.x.x - - [07/Jul/2026:14:58:21 +0200] "GET /geowebcache/ HTTP/1.1" 403 659 10.x.x.x - - [07/Jul/2026:14:58:21 +0200] "GET /favicon.ico HTTP/1.1" 404 772 127.0.0.1 - - [07/Jul/2026:14:59:54 +0200] "POST /jolokia/ HTTP/1.1" 200 779 (The jolokia line is included just to show that there's another web application on the Tomcat which is not rejecting access.) When putting Tomcat in debug logging mode, the following is seen in catalina.out after I've entered the correct credentials: [2026-07-07 14:58:21] [info] 14:58:21 (http-nio-8080-exec-6) DEBUG [web.FilterChainProxy] - Securing GET / [2026-07-07 14:58:21] [info] 14:58:21 (http-nio-8080-exec-6) DEBUG [dao.DaoAuthenticationProvider] - Authenticated user [2026-07-07 14:58:21] [info] 14:58:21 (http-nio-8080-exec-6) DEBUG [www.BasicAuthenticationFilter] - Set SecurityContextHolder to UsernamePasswordAuthenticationToken [Principal=org.springframework.security.core.userdetails.User [Username=geowebcache, Password=[PROTECTED], Enabled=true, AccountNonExpired=true, CredentialsNonExpired=true, AccountNonLocked=true, Granted Authorities=[ROLE_ADMINISTRATOR]], Credentials=[PROTECTED], Authenticated=true, Details=WebAuthenticationDetails [RemoteIpAddress=10.x.x.x, SessionId=BB8B730EC1AE7A4B99BC6CDBBB76E8B8], Granted Authorities=[ROLE_ADMINISTRATOR, FactorGrantedAuthority [authority=FACTOR_PASSWORD, issuedAt=2026-07-07T12:58:21.628297750Z]]] [2026-07-07 14:58:21] [info] 14:58:21 (http-nio-8080-exec-6) DEBUG [access.AccessDeniedHandlerImpl] - Responding with 403 status code What could be wrong with GeoWebCache? Has something changed between GWC 1 and 2 regarding access restrictions? -- Regards, Troels Arvin |
|
From: Peter S. <gs...@sm...> - 2026-05-27 18:53:34
|
Hi all GeoTools 34.4 has been released: https://geotoolsnews.blogspot.com/2026/05/geotools-344-released.html So too has GeoWebCache 1.28.4 https://github.com/GeoWebCache/geowebcache/releases/tag/1.28.4 And GeoServer 2.28.4 https://geoserver.org/announcements/2026/05/25/geoserver-2-28-4-released.html Please visit the above links for more details. Regards Peter Peter GeoServer PSC AWS Solutions Architect https://github.com/petersmythe |
|
From: Peter S. <gs...@sm...> - 2025-12-19 16:13:27
|
Hi GeoTools users GeoTools 33.4 is now available from SourceForge and maven. For more information, please see the GeoTools 33.4 blog post <https://geotoolsnews.blogspot.com/2025/12/geotools-334-released.html>, or GitHub release notes <https://github.com/geotools/geotools/releases/tag/33.41>. Thanks to Peter Smythe (AfriGIS) for making this maintenance release. -- Peter GeoServer PSC https://github.com/petersmythe |
|
From: Pfister, M. <Mar...@ma...> - 2025-07-25 19:10:25
|
Are there any considerations to sending Geoserver's CLIP parameter to a GWC request? If the source layer is in EPSG:4326 is it acceptable to send simple WKT in 4326, even if requesting 3857 tiles from GWC? Or is it recommended to send EWKT? The clipping geometries will be duplicated across many different user sessions, so to cache these requests I will want to add a filter parameter on CLIP, correct? Many thanks, Marc Pfister This electronic communication and any attachments may contain confidential and proprietary information of Maxar, Inc. If you are not the intended recipient, or an agent or employee responsible for delivering this communication to the intended recipient, or if you have received this communication in error, please do not print, copy, retransmit, disseminate or otherwise use the information. Please indicate to the sender that you have received this communication in error, and delete the copy you received. Maxar reserves the right to monitor any electronic communication sent or received by its employees, agents or representatives. |
|
From: Patrick L. <pat...@ai...> - 2025-05-14 16:20:11
|
Hello, When I setup a MBTiles store I get this error message : "Error executing query 'SELECT value from metadata WHERE layername = ? AND key like "parameters.*';' The file metadate.sqlite is created by GeoWebCache and is empty. How can I fix this problem ? Do I have to create and fill a metadata table ? Regards, Patrick The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. |
|
From: Jody G. <jod...@gm...> - 2025-05-13 17:31:30
|
The following releases are available for download and via OSGeo maven repository. - GeoWebCache 1.27.1 <https://github.com/GeoWebCache/geowebcache/releases/tag/1.27.1> ( download <https://sourceforge.net/projects/geowebcache/files/geowebcache/1.27.1/>) - GeoWebCache 1.26.3 <https://github.com/GeoWebCache/geowebcache/releases/tag/1.26.3> ( download <https://sourceforge.net/projects/geowebcache/files/geowebcache/1.26.3/>) A reminder that the project website is located at https://geowebcache.osgeo.org/ - - Jody Garnett |
|
From: Troels A. <tr...@ar...> - 2024-12-26 12:30:35
|
On 2024-12-21, pierre.cardinal wrote: > / The site http://geowebcache.org is redirect to https://systranet.com/ / Yes, it has been discussed before, see: https://sourceforge.net/p/geowebcache/mailman/message/58725281/ -- Regards, Troels Arvin |
|
From: pierre.cardinal <pie...@sy...> - 2024-12-21 20:33:49
|
The site http://geowebcache.org is redirect to https://systranet.com/ |
|
From: pierre.cardinal <pie...@sy...> - 2024-12-21 20:33:35
|
The site http://geowebcache.org is redirect to https://systranet.com/ |
|
From: Troels A. <tr...@ar...> - 2024-10-17 18:12:55
|
Hello,
I'm trying to set up GeoWebCache in a way where the cache directory is
writeable for GeoWebCache, but the configuration is read-only.
So I've set GEOWEBCACHE_CACHE_DIR and GEOWEBCACHE_CONFIG_DIR
("/READONLY" for this example) to two different directories. Both are
readable for tomcat's user, while only the former is also writeable.
The geowebcache webapp fails to start. This is what is seen in the log:
19:31:33 (main) CONFIG [config.XMLConfiguration] - Initializing GridSets
from /READONLY
19:31:33 (main) WARN [support.XmlWebApplicationContext] - Exception
encountered during context initialization - cancelling refresh attempt:
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'gwcXmlConfig' defined in ServletContext resource
[/WEB-INF/geowebcache-core-context.xml]: Invocation of init method
failed; nested exception is java.lang.IllegalArgumentException: Resource
provider must have an input
When stracing, I see that GWC does indeed opening /READONLY, but it
seems to me it insists on opening it it read-write:
...
1489140 newfstatat(AT_FDCWD, "/READONLY", {st_mode=S_IFDIR|0755,
st_size=4096, ...}, 0) = 0
1489140 access("/READONLY", W_OK) = -1 EACCES (Permission denied)
...
I would think GWC could very well work with a read-only geowebcache.xml,
but it seems not(?). Can I in some other way achieve read-only access to
geowebcache.xml?
--
Kind regards,
Troels Arvin
|
|
From: Troels A. <tr...@ar...> - 2024-02-19 15:41:27
|
Hello, I have a GeoWebCache 1.24.0 installation which sometimes stops responding after POST requests to /geowebcache/rest/masstruncate. In Tomcat's access log, I see lines like this: 10.x.x.x - - [19/Feb/2024:15:12:20 +0100] "POST /geowebcache/rest/masstruncate HTTP/1.1" 401 712 10.x.x.x - - [19/Feb/2024:15:12:20 +0100] "POST /geowebcache/rest/masstruncate HTTP/1.1" 200 - 10.x.x.x - - [19/Feb/2024:15:12:20 +0100] "POST /geowebcache/rest/masstruncate HTTP/1.1" 401 712 10.x.x.x - - [19/Feb/2024:15:12:20 +0100] "POST /geowebcache/rest/masstruncate HTTP/1.1" 200 - The lines correspond to lines like this in catalina.out: [2024-02-19 15:12:20] [info] 15:12:20 (GWC Seeder Thread-16) INFO [file.FileBlobStore] - Truncated 0 tiles [2024-02-19 15:12:20] [info] 15:12:20 (GWC Seeder Thread-16) INFO [seed.GWCTask] - Thread group finished TRUNCATE task after 0.0 seconds [2024-02-19 15:12:20] [info] 15:12:20 (GWC Seeder Thread-11) INFO [file.FileBlobStore] - Truncated 0 tiles [2024-02-19 15:12:20] [info] 15:12:20 (GWC Seeder Thread-11) INFO [seed.GWCTask] - Thread group finished TRUNCATE task after 0.0 seconds [2024-02-19 15:12:20] [info] 15:12:20 (GWC Seeder Thread-2) INFO [file.FileBlobStore] - Truncated 0 tiles [2024-02-19 15:12:20] [info] 15:12:20 (GWC Seeder Thread-2) INFO [seed.GWCTask] - Thread group finished TRUNCATE task after 0.0 seconds [2024-02-19 15:12:20] [info] 15:12:20 (GWC Seeder Thread-7) INFO [file.FileBlobStore] - Truncated 45 tiles [2024-02-19 15:12:20] [info] 15:12:20 (GWC Seeder Thread-7) INFO [seed.GWCTask] - Thread group finished TRUNCATE task after 0.009 seconds [...] [2024-02-19 15:12:20] [info] 15:12:20 (http-nio-8080-exec-7452) INFO [seed.TruncateLayerRequest] - Layer: LAYERNAME,Truncated Gridset :EPSG:25832-DK [2024-02-19 15:12:20] [info] 15:12:20 (http-nio-8080-exec-9769) INFO [seed.TruncateLayerRequest] - Layer: LAYERNAME-withoutlabel,Truncated Gridset :EPSG:25832-DK [2024-02-19 15:12:20] [info] 15:12:20 (http-nio-8080-exec-9769) INFO [file.FileBlobStore] - /srv/geowebcache/XXX-deleted-elements does not exist or is not writable [2024-02-19 15:12:20] [info] 15:12:20 (http-nio-8080-exec-9769) INFO [seed.TruncateLayerRequest] - Layer: XXX-deleted-elements,Truncated Gridset :EPSG:25832-NO [2024-02-19 15:12:20] [info] 15:12:20 (http-nio-8080-exec-9769) INFO [file.FileBlobStore] - /srv/geowebcache/XXX-deleted-elements does not exist or is not writable [2024-02-19 15:12:20] [info] 15:12:20 (http-nio-8080-exec-9769) INFO [seed.TruncateLayerRequest] - Layer: XXX-deleted-elements,Truncated Gridset :EPSG:25832-SV [2024-02-19 15:12:20] [info] 15:12:20 (http-nio-8080-exec-9769) INFO [file.FileBlobStore] - /srv/geowebcache/XXX-deleted-elements does not exist or is not writable [2024-02-19 15:12:20] [info] 15:12:20 (http-nio-8080-exec-9769) INFO [seed.TruncateLayerRequest] - Layer: XXX-deleted-elements,Truncated Gridset :EPSG:3008 [...] After this, requests to /geowebcache/service/wmts?REQUEST=getcapabilities stop responding (but the access log still shows some activity). In this state, there is virtually no CPU activity on the server, in particular no Java activity. jstack outputs this: https://troels.arvin.dk/misc/gwc/20240219/jstack-output.txt A Tomcat restart makes GWC respond normally again. In the (roughly) 10 minutes before the masstruncate request, and until the restart, Tomcat's thread count rises from roughly 500 to 3050 (I've tried various thread count limits like 500, 1000, and 3000, and I always end up seing the limit reached). My cache is not very big. At the time of writing, it has 134 000 files taking up 840 MiB. It takes less than two seconds to delete all of the files when I test that. masstruncat requests happen often during the day, and it normally doesn't cause any trouble. Tomcat version: 9.0.58, Java 17.0.9, OS: Linux with XFS as file system. What could be going on? My hypothesis is that I'm hitting a corner case hitting some kind of deadlock in GWC. -- Kind regards, Troels Arvin, Copenhagen |
|
From: Kevin S. <sm...@dr...> - 2024-01-16 20:16:35
|
It looks like the issue is that Planet Federal (formerly Boundless) held the domain, but did not transfer it to OSGeo when the other GeoServer related domains were transferred. We never pestered them about transferring or renewing it and so it expired. For now, https://geowebcache.osgeo.org/ is working so there is still access to the docs. If we can't get geowebcache.org back, I'm happy to stick with an OSGeo third level domain. On 2024-01-11 13:49, Kevin Smith wrote: > Sorry, meant OSGeo not OGC. > > On 2024-01-11 13:47, Kevin Smith wrote: >> And it looks like the name has now been hijacked. >> >> Does anyone know if this was one of the domains Planet Transferred to >> the OGC or were they still holding on to it? Or was it held by >> someone else? >> >> On 2023-12-20 06:46, Troels Arvin via Geowebcache-users wrote: >>> Hello, >>> >>> At the time of writing, https://www.geowebcache.org/ states "The >>> domain has expired". >>> -- Kevin Smith sm...@dr... |
|
From: Kevin S. <sm...@dr...> - 2024-01-11 22:06:21
|
And it looks like the name has now been hijacked. Does anyone know if this was one of the domains Planet Transferred to the OGC or were they still holding on to it? Or was it held by someone else? On 2023-12-20 06:46, Troels Arvin via Geowebcache-users wrote: > Hello, > > At the time of writing, https://www.geowebcache.org/ states "The > domain has expired". > -- Kevin Smith sm...@dr... |
|
From: Kevin S. <sm...@dr...> - 2024-01-11 22:06:16
|
Sorry, meant OSGeo not OGC. On 2024-01-11 13:47, Kevin Smith wrote: > And it looks like the name has now been hijacked. > > Does anyone know if this was one of the domains Planet Transferred to > the OGC or were they still holding on to it? Or was it held by > someone else? > > On 2023-12-20 06:46, Troels Arvin via Geowebcache-users wrote: >> Hello, >> >> At the time of writing, https://www.geowebcache.org/ states "The >> domain has expired". >> -- Kevin Smith sm...@dr... |
|
From: Troels A. <tr...@ar...> - 2023-12-20 15:05:10
|
Hello, At the time of writing, https://www.geowebcache.org/ states "The domain has expired". -- Regards, Troels Arvin |
|
From: Cécile V. <cec...@ca...> - 2023-11-13 16:15:09
|
Thanks Ian - your message sent me on a good track and I managed to make
it work by changing or removing the filter CharacterEncodingFilter in
web.xml in GeoServer (working with 2.20 and 1.17 which where our
original target versions, the original problem being the use of FormPost
with filters that contain accented characters)
Cheers, Cécile
On 10/19/23 1:07 PM, Ian Turton wrote:
> That's usually a format mismatch - you need to make sure the
> content-type header is set to something like text/xml otherwise
> GeoWebCache defaults to form/encoded or something like that and it is
> unable to understand the XML you are sending.
>
> Ian
>
> On Thu, 19 Oct 2023 at 10:19, Cécile Vuilleumier
> <cec...@ca...> wrote:
>
> Hi all,
> We would like to use POST requests for a GeoServer WMS layer in
> GeoWebCache. I tried this with versions 2.23 / 1.23 and 2.24 /
> 1.24. I added <httpRequestMode>FormPost</httpRequestMode> to the
> layer definition in geowebcache.xml but this results in an error
> in GeoServer:
>
> geoserver | 19 Oct 08:48:43 ERROR [geoserver.ows] -
> geoserver | com.ctc.wstx.exc.WstxUnexpectedCharException:
> Unexpected character 'F' (code 70) in prolog; expected '<'
> geoserver | at [row,col {unknown-source}]: [1,1]
> geoserver | at
> com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:666)
> geoserver | at
> com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2148)
> geoserver | at
> com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1180)
> geoserver | at
> org.geoserver.ows.Dispatcher.readOpPost(Dispatcher.java:1605)
> geoserver | at
> org.geoserver.ows.Dispatcher.service(Dispatcher.java:515)
> geoserver | at
> org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:245)
> geoserver | at
> org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:177)
>
> Attached is also a wireshark screenshot of the request. We use
> tomcat for GS and GWC. The requests work when not using the
> FormPost option.
> Do we need further configuration in order to make this work?
>
> Many thanks in advance for your suggestions
> Cécile
> --
> *camptocamp*
> *Cécile Vuilleumier
> *
> Geospatial developer
> www.camptocamp.com <http://www.camptocamp.com>
> _______________________________________________
> Geowebcache-users mailing list
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geowebcache-users
>
>
>
> --
> Ian Turton |
|
From: Alexandre G. <ale...@gm...> - 2023-11-10 15:25:21
|
Yes we tried also with the version and we have the same problem. Regards Alexandre Le ven. 10 nov. 2023 à 16:10, Joaquín Bacigalupo <jo...@gm...> a écrit : > Hello, good morning, have you tried adding the WMS version to your URL? > > https://data.geopf.fr/wms-r/wms?SERVICE=wms&version=1.3.0 > > > <wmsUrl> > <string>https://data.geopf.fr/wms-r/wms?SERVICE=WMS&version=1.3.0 > </string> > </wmsUrl> > > Best regards. > > *Ing. Bacigalupo Joaquín Andrés* > > > El vie, 10 nov 2023 a la(s) 12:01, Alexandre Gacon ( > ale...@gm...) escribió: > >> Hello there, >> >> I am trying to setup a GeoWebCache layer for a WMS source with the >> following configuration: >> >> <?xml version="1.0" encoding="UTF-8"?> >> <wmsLayer> >> <enabled>true</enabled> >> <inMemoryCached>true</inMemoryCached> >> <name>test_ign</name> >> <mimeFormats> >> <string>image/png</string> >> <string>image/jpeg</string> >> </mimeFormats> >> <gridSubsets> >> <gridSubset> >> <gridSetName>EPSG:4326</gridSetName> >> </gridSubset> >> <gridSubset> >> <gridSetName>EPSG:900913</gridSetName> >> </gridSubset> >> </gridSubsets> >> <metaWidthHeight> >> <int>4</int> >> <int>4</int> >> </metaWidthHeight> >> <expireCache>0</expireCache> >> <expireClients>0</expireClients> >> <parameterFilters/> >> <gutter>0</gutter> >> <cacheWarningSkips/> >> <wmsUrl> >> <string>https://data.geopf.fr/wms-r/wms?SERVICE=WMS</string> >> </wmsUrl> >> <wmsLayers>ORTHOIMAGERY.ORTHOPHOTOS</wmsLayers> >> </wmsLayer> >> >> >> >> The WMS service works fine but when I try to preview the layer or to seed >> tiles, GeoWebCache fails and no longer works. >> >> The error I have in the call stack: >> >> 10 Nov 14:29:39 ERROR [geowebcache.GeoWebCacheDispatcher] - All backends >> (1) failed. Reason: Unexpected response code from backend: 400 for >> https://data.geopf.fr/wms-r/wms?SERVICE=WMS. Last request: ' >> https://data.geopf.fr/wms-r/wms?SERVICE=WMS'. >> http://localhost:8080/geoserver/gwc/service/wmts >> 10 Nov 14:29:39 ERROR [geowebcache.GeoWebCacheDispatcher] - Request >> failed >> org.geowebcache.GeoWebCacheException: All backends (1) failed. Reason: >> Unexpected response code from backend: 400 for >> https://data.geopf.fr/wms-r/wms?SERVICE=WMS. Last request: ' >> https://data.geopf.fr/wms-r/wms?SERVICE=WMS'. >> at >> org.geowebcache.layer.wms.WMSHttpHelper.makeRequest(WMSHttpHelper.java:154) >> at >> org.geowebcache.layer.wms.WMSSourceHelper.makeRequest(WMSSourceHelper.java:53) >> at >> org.geowebcache.layer.wms.WMSLayer.getMetatilingReponse(WMSLayer.java:371) >> at org.geowebcache.layer.wms.WMSLayer.getTile(WMSLayer.java:282) >> at org.geowebcache.util.ResponseUtils.writeTile(ResponseUtils.java:101) >> at >> org.geowebcache.GeoWebCacheDispatcher.handleServiceRequest(GeoWebCacheDispatcher.java:426) >> at >> org.geowebcache.GeoWebCacheDispatcher.handleRequestInternal(GeoWebCacheDispatcher.java:286) >> >> Any idea on what can be wrong? >> >> -- >> Alexandre Gacon >> _______________________________________________ >> Geowebcache-users mailing list >> Geo...@li... >> https://lists.sourceforge.net/lists/listinfo/geowebcache-users >> > -- Alexandre Gacon |
|
From: Alexandre G. <ale...@gm...> - 2023-11-10 15:00:31
|
Hello there, I am trying to setup a GeoWebCache layer for a WMS source with the following configuration: <?xml version="1.0" encoding="UTF-8"?> <wmsLayer> <enabled>true</enabled> <inMemoryCached>true</inMemoryCached> <name>test_ign</name> <mimeFormats> <string>image/png</string> <string>image/jpeg</string> </mimeFormats> <gridSubsets> <gridSubset> <gridSetName>EPSG:4326</gridSetName> </gridSubset> <gridSubset> <gridSetName>EPSG:900913</gridSetName> </gridSubset> </gridSubsets> <metaWidthHeight> <int>4</int> <int>4</int> </metaWidthHeight> <expireCache>0</expireCache> <expireClients>0</expireClients> <parameterFilters/> <gutter>0</gutter> <cacheWarningSkips/> <wmsUrl> <string>https://data.geopf.fr/wms-r/wms?SERVICE=WMS</string> </wmsUrl> <wmsLayers>ORTHOIMAGERY.ORTHOPHOTOS</wmsLayers> </wmsLayer> The WMS service works fine but when I try to preview the layer or to seed tiles, GeoWebCache fails and no longer works. The error I have in the call stack: 10 Nov 14:29:39 ERROR [geowebcache.GeoWebCacheDispatcher] - All backends (1) failed. Reason: Unexpected response code from backend: 400 for https://data.geopf.fr/wms-r/wms?SERVICE=WMS. Last request: ' https://data.geopf.fr/wms-r/wms?SERVICE=WMS'. http://localhost:8080/geoserver/gwc/service/wmts 10 Nov 14:29:39 ERROR [geowebcache.GeoWebCacheDispatcher] - Request failed org.geowebcache.GeoWebCacheException: All backends (1) failed. Reason: Unexpected response code from backend: 400 for https://data.geopf.fr/wms-r/wms?SERVICE=WMS. Last request: ' https://data.geopf.fr/wms-r/wms?SERVICE=WMS'. at org.geowebcache.layer.wms.WMSHttpHelper.makeRequest(WMSHttpHelper.java:154) at org.geowebcache.layer.wms.WMSSourceHelper.makeRequest(WMSSourceHelper.java:53) at org.geowebcache.layer.wms.WMSLayer.getMetatilingReponse(WMSLayer.java:371) at org.geowebcache.layer.wms.WMSLayer.getTile(WMSLayer.java:282) at org.geowebcache.util.ResponseUtils.writeTile(ResponseUtils.java:101) at org.geowebcache.GeoWebCacheDispatcher.handleServiceRequest(GeoWebCacheDispatcher.java:426) at org.geowebcache.GeoWebCacheDispatcher.handleRequestInternal(GeoWebCacheDispatcher.java:286) Any idea on what can be wrong? -- Alexandre Gacon |
|
From: Ian T. <ijt...@gm...> - 2023-10-19 11:07:42
|
That's usually a format mismatch - you need to make sure the content-type
header is set to something like text/xml otherwise GeoWebCache defaults to
form/encoded or something like that and it is unable to understand the XML
you are sending.
Ian
On Thu, 19 Oct 2023 at 10:19, Cécile Vuilleumier <
cec...@ca...> wrote:
> Hi all,
> We would like to use POST requests for a GeoServer WMS layer in
> GeoWebCache. I tried this with versions 2.23 / 1.23 and 2.24 / 1.24. I
> added <httpRequestMode>FormPost</httpRequestMode> to the layer definition
> in geowebcache.xml but this results in an error in GeoServer:
>
> geoserver | 19 Oct 08:48:43 ERROR [geoserver.ows] -
> geoserver | com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected
> character 'F' (code 70) in prolog; expected '<'
> geoserver | at [row,col {unknown-source}]: [1,1]
> geoserver | at
> com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:666)
> geoserver | at
> com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2148)
> geoserver | at
> com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1180)
> geoserver | at
> org.geoserver.ows.Dispatcher.readOpPost(Dispatcher.java:1605)
> geoserver | at
> org.geoserver.ows.Dispatcher.service(Dispatcher.java:515)
> geoserver | at
> org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:245)
> geoserver | at
> org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:177)
>
> Attached is also a wireshark screenshot of the request. We use tomcat for
> GS and GWC. The requests work when not using the FormPost option.
> Do we need further configuration in order to make this work?
>
> Many thanks in advance for your suggestions
> Cécile
> --
> *camptocamp*
>
> *Cécile Vuilleumier *
> Geospatial developer
> www.camptocamp.com
> _______________________________________________
> Geowebcache-users mailing list
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geowebcache-users
>
--
Ian Turton
|
|
From: Cécile V. <cec...@ca...> - 2023-10-19 09:13:09
|
Hi all,
We would like to use POST requests for a GeoServer WMS layer in
GeoWebCache. I tried this with versions 2.23 / 1.23 and 2.24 / 1.24. I
added <httpRequestMode>FormPost</httpRequestMode> to the layer
definition in geowebcache.xml but this results in an error in GeoServer:
geoserver | 19 Oct 08:48:43 ERROR [geoserver.ows] -
geoserver | com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected
character 'F' (code 70) in prolog; expected '<'
geoserver | at [row,col {unknown-source}]: [1,1]
geoserver | at
com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:666)
geoserver | at
com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2148)
geoserver | at
com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1180)
geoserver | at
org.geoserver.ows.Dispatcher.readOpPost(Dispatcher.java:1605)
geoserver | at
org.geoserver.ows.Dispatcher.service(Dispatcher.java:515)
geoserver | at
org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:245)
geoserver | at
org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:177)
Attached is also a wireshark screenshot of the request. We use tomcat
for GS and GWC. The requests work when not using the FormPost option.
Do we need further configuration in order to make this work?
Many thanks in advance for your suggestions
Cécile
--
*camptocamp*
*Cécile Vuilleumier
*
Geospatial developer
www.camptocamp.com <http://www.camptocamp.com> |
|
From: tim k. <tim...@gm...> - 2023-06-23 19:49:26
|
Hey there, I was wondering if you would be able to help me implement fullwms mode for a standalone geowebcache. I've been doing some testing with fullwms but I have been unsuccessful in achieving a high throughput for my get map requests. Is this a limitation of fullwms in geowebcache or are there configuration changes I can make to improve the throughput of my proxied getmap requests? I've included additional information in a stack exchange question I just made for additional context. Thanks for reading, I look forward to hearing from you. https://gis.stackexchange.com/questions/462244/how-can-i-improve-the-throughput-of-fullwms-for-a-standalone-geowebcache Thanks, -Tim Kebbel |
|
From: Thunø, K. <kas...@sw...> - 2023-04-27 08:23:07
|
Hi, I am currently struggling setting up a Geowebcache in a production environment with a high load. Problem is that it seems to be running as a single threaded instance where the GWC is extremely busy (queuing) but the underlaying WMS is not doing much and the requests look like being handled sequentially. The GWC is running standalone on Ubuntu with a lot of memory assigned and its not at all running low on resources - on the contrary, it's more a case of queuing up. I need some pointers as to how I can ensure that the GWC is spawning a whole lot more simultaneous requests to the underlaying WMS. The Tomcat is already set up with an Executor with a thread pool of 800 threads which seems to spawned but are in no way reflected on the WMS. I hope someone has ideas as I am running out of them myself :-/ /Kasper |
54 messages has been excluded from this view by a project administrator.
