{"id":12758,"date":"2019-08-24T15:00:40","date_gmt":"2019-08-24T13:00:40","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/"},"modified":"2019-08-24T15:00:40","modified_gmt":"2019-08-24T13:00:40","slug":"alfresco-share-clustering-fail-with-ignored-xml-validation-warning","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/","title":{"rendered":"Alfresco – Share Clustering fail with ‘Ignored XML validation warning’"},"content":{"rendered":"

In a recent project on Alfresco, I had to setup a Clustering environment. It all went smoothly but I did face one single issue with the setup of the Clustering on the Alfresco Share layer. That’s something I never faced before and you will understand why below.<\/p>\n

Initially, to setup the Alfresco Share Clustering, I used the sample file packaged in the distribution zip (E.g.: alfresco-content-services-distribution-6.1.0.5.zip<\/em>):<\/p>\n

<?xml version='1.0' encoding='UTF-8'?>\n<beans \n       xmlns_xsi=\"http:\/\/www.w3.org\/2001\/XMLSchema-instance\"\n       xmlns_hz=\"http:\/\/www.hazelcast.com\/schema\/spring\"\n       xsi_schemaLocation=\"http:\/\/www.springframework.org\/schema\/beans\n                http:\/\/www.springframework.org\/schema\/beans\/spring-beans-2.5.xsd\n                http:\/\/www.hazelcast.com\/schema\/spring\n                https:\/\/hazelcast.com\/schema\/spring\/hazelcast-spring-2.4.xsd\">\n\n   <!--\n        Hazelcast distributed messaging configuration - Share web-tier cluster config\n        - see http:\/\/www.hazelcast.com\/docs.jsp\n        - and specifically http:\/\/docs.hazelcast.org\/docs\/2.4\/manual\/html-single\/#SpringIntegration\n   -->\n   <!-- Configure cluster to use either Multicast or direct TCP-IP messaging - multicast is default -->\n   <!-- Optionally specify network interfaces - server machines likely to have more than one interface -->\n   <!-- The messaging topic - the \"name\" is also used by the persister config below -->\n   <!--\n   <hz:topic id=\"topic\" instance-ref=\"webframework.cluster.slingshot\" name=\"slingshot-topic\"\/>\n   <hz:hazelcast id=\"webframework.cluster.slingshot\">\n      <hz:config>\n         <hz:group name=\"slingshot\" password=\"alfresco\"\/>\n         <hz:network port=\"5801\" port-auto-increment=\"true\">\n            <hz:join>\n               <hz:multicast enabled=\"true\"\n                     multicast-group=\"224.2.2.5\"\n                     multicast-port=\"54327\"\/>\n               <hz:tcp-ip enabled=\"false\">\n                  <hz:members><\/hz:members>\n               <\/hz:tcp-ip>\n            <\/hz:join>\n            <hz:interfaces enabled=\"false\">\n               <hz:interface>192.168.1.*<\/hz:interface>\n            <\/hz:interfaces>\n         <\/hz:network>\n      <\/hz:config>\n   <\/hz:hazelcast>\n\n   <bean id=\"webframework.cluster.clusterservice\" class=\"org.alfresco.web.site.ClusterTopicService\" init-method=\"init\">\n      <property name=\"hazelcastInstance\" ref=\"webframework.cluster.slingshot\" \/>\n      <property name=\"hazelcastTopicName\"><value>slingshot-topic<\/value><\/property>\n   <\/bean>\n   -->\n\n<\/beans><\/pre>\n
 <\/p>\n
I obviously uncommented the whole section and configured it properly for the Share Clustering. The above content is only the default\/sample content, nothing more.<\/p>\n
Once configured, I restarted Alfresco but it failed with the following messages:<\/p>\n
24-Aug-2019 14:35:12.974 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]\n24-Aug-2019 14:35:12.974 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat\/8.5.34\n24-Aug-2019 14:35:12.988 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDescriptor Deploying configuration descriptor [\/opt\/tomcat\/conf\/Catalina\/localhost\/share.xml]\nAug 24, 2019 2:35:15 PM org.apache.jasper.servlet.TldScanner scanJars\nINFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.\nAug 24, 2019 2:35:15 PM org.apache.catalina.core.ApplicationContext log\nINFO: No Spring WebApplicationInitializer types detected on classpath\nAug 24, 2019 2:35:15 PM org.apache.catalina.core.ApplicationContext log\nINFO: Initializing Spring root WebApplicationContext\n2019-08-23 14:35:16,052  WARN  [factory.xml.XmlBeanDefinitionReader] [localhost-startStop-1] Ignored XML validation warning\n org.xml.sax.SAXParseException; lineNumber: 18; columnNumber: 92; schema_reference.4: Failed to read schema document 'https:\/\/hazelcast.com\/schema\/spring\/hazelcast-spring-2.4.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.\n\tat java.xml\/com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:204)\n\tat java.xml\/com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.warning(ErrorHandlerWrapper.java:100)\n\tat java.xml\/com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:392)\n\tat java.xml\/com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:306)\n\tat java.xml\/com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaErr(XSDHandler.java:4218)\n  ... 69 more\nCaused by: java.net.ConnectException: Connection refused (Connection refused)\n\tat java.base\/java.net.PlainSocketImpl.socketConnect(Native Method)\n\tat java.base\/java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:399)\n\tat java.base\/java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:242)\n\t... 89 more\n...\n2019-08-23 14:35:16,067  ERROR [web.context.ContextLoader] [localhost-startStop-1] Context initialization failed\n org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Failed to import bean definitions from relative location [surf-config.xml]\nOffending resource: class path resource [web-application-config.xml]; nested exception is org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Failed to import bean definitions from URL location [classpath*:alfresco\/web-extension\/*-context.xml]\nOffending resource: class path resource [surf-config.xml]; nested exception is org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 18 in XML document from file [\/opt\/tomcat\/shared\/classes\/alfresco\/web-extension\/custom-slingshot-application-context.xml] is invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 18; columnNumber: 92; cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'hz:topic'.\n\tat org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:68)\n\tat org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:85)\n\tat org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:76)\n  ... 33 more\nCaused by: org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Failed to import bean definitions from URL location [classpath*:alfresco\/web-extension\/*-context.xml]\nOffending resource: class path resource [surf-config.xml]; nested exception is org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 18 in XML document from file [\/opt\/tomcat\/shared\/classes\/alfresco\/web-extension\/custom-slingshot-application-context.xml] is invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 18; columnNumber: 92; cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'hz:topic'.\n\tat org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:68)\n\tat org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:85)\n\tat org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:76)\n\t... 42 more\nCaused by: org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 18 in XML document from file [\/opt\/tomcat\/shared\/classes\/alfresco\/web-extension\/custom-slingshot-application-context.xml] is invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 18; columnNumber: 92; cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'hz:topic'.\n\tat org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:397)\n\tat org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:335)\n\tat org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:303)\n\t... 44 more\nCaused by: org.xml.sax.SAXParseException; lineNumber: 18; columnNumber: 92; cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'hz:topic'.\n\tat java.xml\/com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:204)\n\tat java.xml\/com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:135)\n\tat java.xml\/com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:396)\n\t... 64 more\n...\n24-Aug-2019 14:35:16.196 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file\n24-Aug-2019 14:35:16.198 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [\/share] startup failed due to previous errors\nAug 24, 2019 2:35:16 PM org.apache.catalina.core.ApplicationContext log\n...<\/pre>\n
 <\/p>\n
As you can see above, the message is pretty clear: there is a problem within the file “\/opt\/tomcat\/shared\/classes\/alfresco\/web-extension\/custom-slingshot-application-context.xml<\/em>” which is causing Share to fail to start properly. The first warning message points you directly to the issue: “Failed to read schema document ‘https:\/\/hazelcast.com\/schema\/spring\/hazelcast-spring-2.4.xsd’<\/em>”<\/p>\n
After checking the content of the sample file and comparing it with a working one, I found out what was wrong. To solve this specific issue, you can simply replace “https:\/\/hazelcast.com\/schema\/spring\/hazelcast-spring-2.4.xsd<\/em>” with “http:\/\/www.hazelcast.com\/schema\/spring\/hazelcast-spring-2.4.xsd<\/em>“. Please note the two differences in the URL:<\/p>\n
    \n
  • Switch from “https<\/em>” to “http<\/em>“<\/li>\n
  • Switch from “hazelcast.com<\/em>” to “www.hazelcast.com<\/em>“<\/li>\n<\/ul>\n
     <\/p>\n
    The issue was actually caused by the fact that this installation was completely offline, with no access to internet. Because of that, Spring wasn’t able to check for the XSD file to validate the definition in the context file. The solution is therefore to switch the URL to http with www.hazelcast.com so that the Spring internal resolution can understand and use the local file to do the validation and not look for it online.<\/p>\n
    As mentioned previously, I never faced this issue before for two main reasons:<\/p>\n
      \n
    • I usually don’t use the sample files provided by Alfresco, I always prefer to build my own<\/li>\n
    • I mainly install Alfresco on servers which have internet access (outgoing communications allowed)<\/li>\n<\/ul>\n
       <\/p>\n
      Once the URL is corrected, Alfresco Share is able to start and the Clustering is configured properly:<\/p>\n
      24-Aug-2019 14:37:22.558 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]\n24-Aug-2019 14:37:22.558 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat\/8.5.34\n24-Aug-2019 14:37:22.573 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDescriptor Deploying configuration descriptor [\/opt\/tomcat\/conf\/Catalina\/localhost\/share.xml]\nAug 24, 2019 2:37:24 PM org.apache.jasper.servlet.TldScanner scanJars\nINFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.\nAug 24, 2019 2:37:25 PM org.apache.catalina.core.ApplicationContext log\nINFO: No Spring WebApplicationInitializer types detected on classpath\nAug 24, 2019 2:37:25 PM org.apache.catalina.core.ApplicationContext log\nINFO: Initializing Spring root WebApplicationContext\nAug 24, 2019 2:37:28 PM com.hazelcast.impl.AddressPicker\nINFO: Resolving domain name 'share_n1.domain' to address(es): [10.10.10.10]\nAug 24, 2019 2:37:28 PM com.hazelcast.impl.AddressPicker\nINFO: Resolving domain name 'share_n2.domain' to address(es): [127.0.0.1, 10.10.10.11]\nAug 24, 2019 2:37:28 PM com.hazelcast.impl.AddressPicker\nINFO: Interfaces is disabled, trying to pick one address from TCP-IP config addresses: [share_n1.domain\/10.10.10.10, share_n2.domain\/10.10.10.11, share_n2.domain\/127.0.0.1]\nAug 24, 2019 2:37:28 PM com.hazelcast.impl.AddressPicker\nINFO: Prefer IPv4 stack is true.\nAug 24, 2019 2:37:28 PM com.hazelcast.impl.AddressPicker\nINFO: Picked Address[share_n2.domain]:5801, using socket ServerSocket[addr=\/0:0:0:0:0:0:0:0,localport=5801], bind any local is true\nAug 24, 2019 2:37:28 PM com.hazelcast.system\nINFO: [share_n2.domain]:5801 [slingshot] Hazelcast Community Edition 2.4 (20121017) starting at Address[share_n2.domain]:5801\nAug 24, 2019 2:37:28 PM com.hazelcast.system\nINFO: [share_n2.domain]:5801 [slingshot] Copyright (C) 2008-2012 Hazelcast.com\nAug 24, 2019 2:37:28 PM com.hazelcast.impl.LifecycleServiceImpl\nINFO: [share_n2.domain]:5801 [slingshot] Address[share_n2.domain]:5801 is STARTING\nAug 24, 2019 2:37:28 PM com.hazelcast.impl.TcpIpJoiner\nINFO: [share_n2.domain]:5801 [slingshot] Connecting to possible member: Address[share_n1.domain]:5801\nAug 24, 2019 2:37:28 PM com.hazelcast.nio.ConnectionManager\nINFO: [share_n2.domain]:5801 [slingshot] 54991 accepted socket connection from share_n1.domain\/10.10.10.10:5801\nAug 24, 2019 2:37:29 PM com.hazelcast.impl.Node\nINFO: [share_n2.domain]:5801 [slingshot] ** setting master address to Address[share_n1.domain]:5801\nAug 24, 2019 2:37:35 PM com.hazelcast.cluster.ClusterManager\nINFO: [share_n2.domain]:5801 [slingshot]\n\nMembers [2] {\n\tMember [share_n1.domain]:5801\n\tMember [share_n2.domain]:5801 this\n}\n\nAug 24, 2019 2:37:37 PM com.hazelcast.impl.LifecycleServiceImpl\nINFO: [share_n2.domain]:5801 [slingshot] Address[share_n2.domain]:5801 is STARTED\n2019-08-23 14:37:37,664  INFO  [web.site.ClusterTopicService] [localhost-startStop-1] Init complete for Hazelcast cluster - listening on topic: share_hz_test\n...<\/pre>\n
       <\/p>\n","protected":false},"excerpt":{"rendered":"
      In a recent project on Alfresco, I had to setup a Clustering environment. It all went smoothly but I did face one single issue with the setup of the Clustering on the Alfresco Share layer. That’s something I never faced before and you will understand why below. Initially, to setup the Alfresco Share Clustering, I […]<\/p>\n","protected":false},"author":20,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197,525],"tags":[3169,38,1681,1170],"type_dbi":[],"class_list":["post-12758","post","type-post","status-publish","format-standard","hentry","category-application-integration-middleware","category-enterprise-content-management","tag-alfresco","tag-cluster","tag-hazelcast","tag-share"],"acf":[],"yoast_head":"\nAlfresco - Share Clustering fail with 'Ignored XML validation warning' - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Alfresco - Share Clustering fail with 'Ignored XML validation warning'\" \/>\n<meta property=\"og:description\" content=\"In a recent project on Alfresco, I had to setup a Clustering environment. It all went smoothly but I did face one single issue with the setup of the Clustering on the Alfresco Share layer. That’s something I never faced before and you will understand why below. Initially, to setup the Alfresco Share Clustering, I […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2019-08-24T13:00:40+00:00\" \/>\n<meta name=\"author\" content=\"Morgan Patou\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@MorganPatou\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Morgan Patou\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/\"},\"author\":{\"name\":\"Morgan Patou\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"headline\":\"Alfresco – Share Clustering fail with ‘Ignored XML validation warning’\",\"datePublished\":\"2019-08-24T13:00:40+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/\"},\"wordCount\":382,\"commentCount\":0,\"keywords\":[\"Alfresco\",\"Cluster\",\"Hazelcast\",\"Share\"],\"articleSection\":[\"Application integration & Middleware\",\"Enterprise content management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/\",\"name\":\"Alfresco - Share Clustering fail with 'Ignored XML validation warning' - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2019-08-24T13:00:40+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Alfresco – Share Clustering fail with ‘Ignored XML validation warning’\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\",\"name\":\"Morgan Patou\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"caption\":\"Morgan Patou\"},\"description\":\"Morgan Patou has over 12 years of experience in Enterprise Content Management (ECM) systems, with a strong focus in recent years on platforms such as Alfresco, Documentum, and M-Files. He specializes in the architecture, setup, customization, and maintenance of ECM infrastructures in complex & critical environments. Morgan is well-versed in both engineering and operations aspects, including high availability design, system integration, and lifecycle management. He also has a solid foundation in open-source and proprietary technologies - ranging from Apache, OpenLDAP or Kerberos to enterprise-grade systems like WebLogic. Morgan Patou holds an Engineering Degree in Computer Science from ENSISA (\u00c9cole Nationale Sup\u00e9rieure d'Ing\u00e9nieurs Sud Alsace) in Mulhouse, France. He is Alfresco Content Services Certified Administrator (ACSCA), Alfresco Content Services Certified Engineer (ACSCE) as well as OpenText Documentum Certified Administrator. His industry experience spans the Public Sector, IT Services, Financial Services\/Banking, and the Pharmaceutical industry.\",\"sameAs\":[\"https:\/\/blog.dbi-services.com\/author\/morgan-patou\/\",\"https:\/\/x.com\/MorganPatou\"],\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/morgan-patou\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Alfresco - Share Clustering fail with 'Ignored XML validation warning' - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/","og_locale":"en_US","og_type":"article","og_title":"Alfresco - Share Clustering fail with 'Ignored XML validation warning'","og_description":"In a recent project on Alfresco, I had to setup a Clustering environment. It all went smoothly but I did face one single issue with the setup of the Clustering on the Alfresco Share layer. That’s something I never faced before and you will understand why below. Initially, to setup the Alfresco Share Clustering, I […]","og_url":"https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/","og_site_name":"dbi Blog","article_published_time":"2019-08-24T13:00:40+00:00","author":"Morgan Patou","twitter_card":"summary_large_image","twitter_creator":"@MorganPatou","twitter_misc":{"Written by":"Morgan Patou","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/"},"author":{"name":"Morgan Patou","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"headline":"Alfresco – Share Clustering fail with ‘Ignored XML validation warning’","datePublished":"2019-08-24T13:00:40+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/"},"wordCount":382,"commentCount":0,"keywords":["Alfresco","Cluster","Hazelcast","Share"],"articleSection":["Application integration & Middleware","Enterprise content management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/","url":"https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/","name":"Alfresco - Share Clustering fail with 'Ignored XML validation warning' - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2019-08-24T13:00:40+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/alfresco-share-clustering-fail-with-ignored-xml-validation-warning\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Alfresco – Share Clustering fail with ‘Ignored XML validation warning’"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8","name":"Morgan Patou","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","caption":"Morgan Patou"},"description":"Morgan Patou has over 12 years of experience in Enterprise Content Management (ECM) systems, with a strong focus in recent years on platforms such as Alfresco, Documentum, and M-Files. He specializes in the architecture, setup, customization, and maintenance of ECM infrastructures in complex & critical environments. Morgan is well-versed in both engineering and operations aspects, including high availability design, system integration, and lifecycle management. He also has a solid foundation in open-source and proprietary technologies - ranging from Apache, OpenLDAP or Kerberos to enterprise-grade systems like WebLogic. Morgan Patou holds an Engineering Degree in Computer Science from ENSISA (\u00c9cole Nationale Sup\u00e9rieure d'Ing\u00e9nieurs Sud Alsace) in Mulhouse, France. He is Alfresco Content Services Certified Administrator (ACSCA), Alfresco Content Services Certified Engineer (ACSCE) as well as OpenText Documentum Certified Administrator. His industry experience spans the Public Sector, IT Services, Financial Services\/Banking, and the Pharmaceutical industry.","sameAs":["https:\/\/blog.dbi-services.com\/author\/morgan-patou\/","https:\/\/x.com\/MorganPatou"],"url":"https:\/\/www.dbi-services.com\/blog\/author\/morgan-patou\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/12758","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/20"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=12758"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/12758\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=12758"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=12758"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=12758"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=12758"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}