I recently faced another interesting issue (c.f. this one) with Documentum xPlore where the Dsearch would refuse to start because of a stuck online rebuild. It happened on a Kubernetes environment using custom images we built (for security and scalability). The K8s Nodes were split across two DataCenters for DR reasons. However, one of the DataCenter had an important issue…
At a customer using Documentum inside Kubernetes, unusually frequent restarts of xPlore containers were noted a couple weeks after the introduction of CPS Only pods on the different Production environments. The customer had a very simple Standalone xPlore setup, with Dsearch+IndexAgent, but without CPS Only Nodes. It was noticed at this customer that the indexing and search load was reaching…
During an upgrade project of xPlore from 16.4 to 20.2 at a customer, I faced a quite interesting issue with the xPlore CPS (Content Processing Services) that couldn’t start properly and were, therefore, shown as “UNREACHABLE“. The funny thing is that the Java/WildFly processes of the PrimaryDsearch and CPS were properly running, and it was possible to login to the…
In a previous blog (see this one), I described how to setup a WildFly instance in HTTPS and I quickly mentioned something related to the CPS. When I wrote this previous blog, I was already aware of one specific issue that prevented the CPS to be usable but I didn’t want to mention it to stay focus on the WildFly…
In a previous blog (See this one), I mentioned some differences between JBoss 7.1.1 (coming with CS 7.2 / xPlore 1.5) and WildFly 9.0.1 (coming with CS 7.3 / xPlore 1.6). In this blog, I will talk about what is needed to setup a WildFly instance in HTTPS only or HTTPS+HTTP. This blog applies to both Content Servers and Full Text…
