Hi,

I have never tried that and you can test it as easily as I could be configuring 
such a layer into GWC and following what appears into the 
Geoserver/Jetty/Tomcat logs. However, I would be surprised if it will be 
anything else than GetMaps with &LAYERS=layer1,layer2,layer3

-Jukka Rahkonen-

Chris Brown wrote:

Thanks Rahkonen, I will also look into that, I had thought this was not 
possible with GeoWebCache. Do you know if GWC is getting each layer separately 
and joining the images or it's using LAYERS=layer1,layer2,layer3 in the WMS 
request?

On 12 November 2015 at 20:06, Rahkonen Jukka (MML) 
<jukka.rahko...@maanmittauslaitos.fi<mailto:jukka.rahko...@maanmittauslaitos.fi>>
 wrote:
Hi,

I don’t know your use case but perhaps you could build the group on GeoWebCache 
side by defining the layers which you want to use together in geowebcach.xml – 
wmsLayer:

<wmsLayers>layer1,layer2,layer3t</wmsLayers> <!-- layer names as known by your 
wms -->

–Jukka Rahkonen-




Chris Brown wrote:

Ciao Simone,

Sorry for being slow to response. We implemented a work around where by we 
stopped using layer groups and instead just listed the layers in the LAYERS 
argument of our WMS request, but then realized that we can't us GeoWebCache 
when doing that.

I've come back and tried to isolate this bug and find some repeatable steps. 
Here they are:

Sorry for the delay with coming back on this. I've managed to isolate this bug 
and make it easily repeatable with a standard setup.

Here's the setup:

GeoServer 1: Clean install running 2.8, in it's own Tomcat container, running 
JMS-Cluster with default settings.

GeoServer 2: Clean install running 2.8, in it's own Tomcat container, running 
JMS-Cluster with default settings.

Both GeoServer's are sharing the same data directory.

Steps to repeat:

1. GeoServer 1, create new layer group. Use the "sf" workspace and the 
"streams" layer
2. On GeoServer 1 go to layer preview and open the group layer in OpenLayers, 
it displays as expected
3. Refresh GeoServer 2, we can now see the new layer group as expected
4. On GeoServer 2 go to the layer preview and open the new group layer in 
OpenLayers
5. We are returned a NullPointerException as an XML response. The same error is 
show in the GeoServer2 logs.

Attempts to resolve:

1. Tried using 2.7
2. Tried using external ActiveMQ Broker
3. Tried using Master / Slave setup.
4. Tried using individual data directories for each GeoServer instead of shared.

None of the above worked. I've also posted this information to the bug report. 
So it seems layer groups don't work when using JMS Clustering in versions 2.7 
or 2.8 (haven't tried others).

When you have time, could you please check if you see the same thing when 
repeating the same steps as me?

Cheers,

Chris

On 22 October 2015 at 23:36, Simone Giannecchini 
<simone.giannecch...@geo-solutions.it<mailto:simone.giannecch...@geo-solutions.it>>
 wrote:
Ciao Chris,
see my message on the JIRA report.
I have tested on master and it worked for me. We might need more info.


Regards,
Simone Giannecchini
==
GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.
==
Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313<tel:%2B39%200584%20962313>
fax:     +39 0584 1660272<tel:%2B39%200584%201660272>
mob:   +39  333 8128928<tel:%2B39%20%C2%A0333%208128928>

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i 
file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo 
è consentito esclusivamente al destinatario del messaggio, per le finalità 
indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne 
il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di 
procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro 
sistema. Conservare il messaggio stesso, divulgarlo anche in parte, 
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, 
costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the 
attention and use of the named addressee(s) and may be confidential or 
proprietary in nature or covered by the provisions of privacy act (Legislative 
Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in 
accord with its purpose, any disclosure, reproduction, copying, distribution, 
or either dissemination, either whole or partial, is strictly forbidden except 
previous formal approval of the named addressee(s). If you are not the intended 
recipient, please contact 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 
made after they were sent or for other risks which arise as a result of e-mail 
transmission, viruses, etc.

On Thu, Oct 22, 2015 at 10:25 AM, Chris Brown 
<ch...@mangomap.com<mailto:ch...@mangomap.com>> wrote:
Thanks Andrea, I've added a new bug report here - 
https://osgeo-org.atlassian.net/browse/GEOS-7263.

Cheers,

Chris

On 22 October 2015 at 15:03, Andrea Aime 
<andrea.a...@geo-solutions.it<mailto:andrea.a...@geo-solutions.it>> wrote:
On Thu, Oct 22, 2015 at 10:01 AM, Chris Brown 
<ch...@mangomap.com<mailto:ch...@mangomap.com>> wrote:
Hi Andrea,

Thanks Andrea. That's definitely not the case this time, we're using a UUID for 
both the layer and group name. We're using GeoServer 2.7.2.

In that case the issue is unknown, can you report it with a step by step way to 
reproduce it (best if against the default data dir)?
https://osgeo-org.atlassian.net/projects/GEOS/issues

Cheers
Andrea


--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313<tel:%2B39%200584%20962313>
fax: +39 0584 1660272<tel:%2B39%200584%201660272>
mob: +39  339 8844549<tel:%2B39%20%C2%A0339%208844549>

http://www.geo-solutions.it
http://twitter.com/geosolutions_it


AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i 
file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo 
è consentito esclusivamente al destinatario del messaggio, per le finalità 
indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne 
il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di 
procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro 
sistema. Conservare il messaggio stesso, divulgarlo anche in parte, 
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, 
costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.



The information in this message and/or attachments, is intended solely for the 
attention and use of the named addressee(s) and may be confidential or 
proprietary in nature or covered by the provisions of privacy act (Legislative 
Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in 
accord with its purpose, any disclosure, reproduction, copying, distribution, 
or either dissemination, either whole or partial, is strictly forbidden except 
previous formal approval of the named addressee(s). If you are not the intended 
recipient, please contact 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 
made after they were sent or for other risks which arise as a result of e-mail 
transmission, viruses, etc.

-------------------------------------------------------



--
_________________

Chris Brown

MangoMap

------------------------------------------------------------------------------

_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net<mailto:Geoserver-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/geoserver-users




--
_________________

Chris Brown

MangoMap



--
_________________

Chris Brown

MangoMap
------------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to