Ciao David, I have done a quick test using our training material and it looks like a bug in the code that handles the layer creation over the JMS channel, we are probably making confusion on using the workspace.
I would certainly open a JIRA issue for this. 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 fax: +39 0584 1660272 mob: +39 333 8128928 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 Wed, Oct 7, 2015 at 8:59 AM, David Niedzielski <[email protected]> wrote: > Hiya geo-dudes, > > Having some real show-stopper issues trying to get clustering via JMS > working... > > We are attempting to run 2 geoservers in a replication cluster using JMS via > an external ActiveMQ broker. The geoservers are running on separate > machines, and the broker is running on a third machine. Each geoserver is > configured as both a Master and a Slave. Basic replication works fine, > regardless of whether the catalog is changed via the GeoServer REST interface > or via the GeoServer admin site. However, one use-case fails consistently: > > 0) Both geoserver 1 and geoserver 2 have workspaces Y and Z defined. > 1) Create a layer X in workspace Y on geoserver 1. > 2) Create a layer X in workspace Z on geoserver 1. > > IOW, all I'm doing is creating a layer with the same name in two different > workspaces. After doing this, geoserver 1's catalog is fine: two > workspaces, two layers: Y.X and Z.X. However, the slave geoserver has two > instances of Y.X. If I add layers WS1.LayerName, WS2.LayerName, ..., > WSn.LayerName on one geoserver, the other geoserver will always have n > instances of layer "LayerName" in workspace WS1. > > Can anyone else reproduce this? Any suggestions? > > Basic information > =============== > Version: 2.7-SNAPSHOT > Git Revision: e0d32d1c0053b786aba2aa458b3d839634d5d49a > Build Date: 26-Jul-2015 10:40 > > Additional jars/plugins > ==================== > activemq-broker-5.9.0.jar > activemq-client-5.9.0.jar > activemq-jdbc-store-5.9.0.jar > activemq-jms-pool-5.9.0.jar > activemq-kahadb-store-5.9.0.jar > activemq-openwire-legacy-5.9.0.jar > activemq-pool-5.9.0.jar > activemq-protobuf-1.0.jar > activemq-spring-5.9.0.jar > ant-1.8.4.jar > ant-launcher-1.8.4.jar > antlr-2.7.7.jar > antlr-3.3.jar > antlr-runtime-3.3.jar > geronimo-annotation_1.0_spec-1.1.1.jar > geronimo-j2ee-management_1.1_spec-1.0.1.jar > geronimo-jms_1.1_spec-1.1.1.jar > geronimo-jta_1.0.1B_spec-1.0.1.jar > gs-control-flow-2.7-SNAPSHOT.jar > gs-jms-commons-2.7-SNAPSHOT.jar > gs-jms-geoserver-2.7-SNAPSHOT.jar > gs-printing-2.7-SNAPSHOT.jar > gs-querylayer-2.7-SNAPSHOT.jar > gs-web-wps-2.7-SNAPSHOT.jar > gs-wps-core-2.7-SNAPSHOT.jar > gt-process-geometry-13-SNAPSHOT.jar > gt-xsd-wps-13-SNAPSHOT.jar > hawtbuf-1.9.jar > itextpdf-5.4.4.jar > jms-api-1.1-rev-1.jar > jyaml-1.3.jar > mapfish-geo-lib-1.2.0.jar > metrics-core-3.0.2.jar > metrics-healthchecks-3.0.2.jar > metrics-httpclient-3.0.2.jar > metrics-json-3.0.2.jar > metrics-jvm-3.0.2.jar > metrics-log4j-3.0.2.jar > metrics-servlet-3.0.2.jar > metrics-servlets-3.0.2.jar > net.opengis.wps-13-SNAPSHOT.jar > print-lib-2.1.0.jar > serializer-2.7.1.jar > spring-jms-3.1.4.RELEASE.jar > xbean-spring-3.5.jar > xercesImpl-2.7.1.jar > xml-apis-xerces-2.7.1.jar > ------------------------------------------------------------------------------ > Full-scale, agent-less Infrastructure Monitoring from a single dashboard > Integrate with 40+ ManageEngine ITSM Solutions for complete visibility > Physical-Virtual-Cloud Infrastructure monitoring from one console > Real user monitoring with APM Insights and performance trend reports > Learn More http://pubads.g.doubleclick.net/gampad/clk?id=247754911&iu=/4140 > _______________________________________________ > Geoserver-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users ------------------------------------------------------------------------------ _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
