Documentum is an inexhaustible source of issues and that’s great because I can continuously write blogs on it, and I always have materials for that. In this blog, I will talk about the ACS not being able to start on the MethodServer because of an ActiveMQ error. As you might know, WildFly has been coming with an integrated ActiveMQ for quite some time now and therefore, in case something goes wrong with ActiveMQ, it might impact your Documentum applications deployed on WildFly.<\/p>\n\n\n\n
The issue I will talk about today happened after a simple restart of the MethodServer that has been done simply because some Documentum jars were updated. Unfortunately, the startup failed with the following errors:<\/p>\n\n\n
\n[dmadmin@cs-0 ~]$ cd $JMS_HOME\/server\/DctmServer_MethodServer\/log\n[dmadmin@cs-0 log]$ cat server.log\n...\n2022-05-02 06:54:23,181 UTC INFO [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final\n2022-05-02 06:54:23,635 UTC INFO [org.jboss.msc] (main) JBoss MSC version 1.4.8.Final\n2022-05-02 06:54:23,644 UTC INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final\n2022-05-02 06:54:23,801 UTC INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 17.0.1.Final (WildFly Core 9.0.2.Final) starting\n2022-05-02 06:54:24,701 UTC INFO [org.wildfly.security] (ServerService Thread Pool -- 25) ELY00001: WildFly Elytron version 1.9.1.Final\n...\n2022-05-02 06:54:31,365 UTC INFO [org.jboss.as.patching] (MSC service thread 1-4) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none\n2022-05-02 06:54:31,403 UTC INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory $DOCUMENTUM\/wildfly17.0.1\/server\/DctmServer_MethodServer\/deployments\n2022-05-02 06:54:31,406 UTC INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "ServerApps.ear" (runtime-name: "ServerApps.ear")\n2022-05-02 06:54:31,406 UTC INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "error.war" (runtime-name: "error.war")\n2022-05-02 06:54:31,406 UTC INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "acs.ear" (runtime-name: "acs.ear")\n2022-05-02 06:54:31,430 UTC INFO [org.jboss.as.remoting] (MSC service thread 1-7) WFLYRMT0001: Listening on 127.0.0.1:9084\n2022-05-02 06:54:31,447 UTC ERROR [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ224097: Failed to start server: java.io.IOException: Input\/output error\n at java.base\/sun.nio.ch.FileDispatcherImpl.pread0(Native Method)\n at java.base\/sun.nio.ch.FileDispatcherImpl.pread(FileDispatcherImpl.java:54)\n at java.base\/sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:274)\n at java.base\/sun.nio.ch.IOUtil.read(IOUtil.java:233)\n at java.base\/sun.nio.ch.FileChannelImpl.readInternal(FileChannelImpl.java:811)\n at java.base\/sun.nio.ch.FileChannelImpl.read(FileChannelImpl.java:796)\n at org.apache.activemq.artemis@2.8.1\/\/org.apache.activemq.artemis.core.server.NodeManager.createNodeId(NodeManager.java:209)\n at org.apache.activemq.artemis@2.8.1\/\/org.apache.activemq.artemis.core.server.NodeManager.setUpServerLockFile(NodeManager.java:195)\n at org.apache.activemq.artemis@2.8.1\/\/org.apache.activemq.artemis.core.server.impl.FileLockNodeManager.start(FileLockNodeManager.java:76)\n at org.apache.activemq.artemis@2.8.1\/\/org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:576)\n at org.apache.activemq.artemis@2.8.1\/\/org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:522)\n at org.apache.activemq.artemis@2.8.1\/\/org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:373)\n at org.wildfly.extension.messaging-activemq\/\/org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:206)\n at org.wildfly.extension.messaging-activemq\/\/org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:65)\n at org.wildfly.extension.messaging-activemq\/\/org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:100)\n at java.base\/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)\n at java.base\/java.util.concurrent.FutureTask.run(FutureTask.java:264)\n at org.jboss.threads@2.3.3.Final\/\/org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)\n at org.jboss.threads@2.3.3.Final\/\/org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)\n at org.jboss.threads@2.3.3.Final\/\/org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)\n at org.jboss.threads@2.3.3.Final\/\/org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348)\n at java.base\/java.lang.Thread.run(Thread.java:829)\n at org.jboss.threads@2.3.3.Final\/\/org.jboss.threads.JBossThread.run(JBossThread.java:485)\n\n2022-05-02 06:54:31,561 UTC INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTPS listener default-https listening on 0.0.0.0:9082\n2022-05-02 06:54:31,650 UTC INFO [org.jboss.ws.common.management] (MSC service thread 1-7) JBWS022052: Starting JBossWS 5.3.0.Final (Apache CXF 3.3.2)\n2022-05-02 06:54:32,837 UTC INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-3) ISPN000128: Infinispan version: Infinispan 'Infinity Minus ONE +2' 9.4.14.Final\n2022-05-02 06:54:33,191 UTC INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 62) WFLYCLINF0002: Started client-mappings cache from ejb container\n2022-05-02 06:54:33,317 UTC INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 63) WFLYUT0021: Registered web context: '\/' for server 'default-server'\n...\n2022-05-02 06:55:48,364 UTC INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0207: Starting subdeployment (runtime-name: "bocs.war")\n2022-05-02 06:55:48,364 UTC INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "documentum-bocs-ws.war")\n2022-05-02 06:55:49,289 UTC WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.acs.ear" is using a private module ("org.jboss.as.jmx") which may be changed or removed in future versions without notice.\n...\n2022-05-02 06:55:50,516 UTC INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 70) WFLYUT0021: Registered web context: '\/bocs-ws' for server 'default-server'\n2022-05-02 06:55:58,622 UTC INFO [org.jboss.as.server] (Thread-1) WFLYSRV0220: Server shutdown has been requested via an OS signal\n2022-05-02 06:55:58,656 UTC INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0019: Stopped Driver service with driver-name = h2\n2022-05-02 06:55:58,666 UTC INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) WFLYMAIL0002: Unbound mail session [java:jboss\/mail\/Default]\n2022-05-02 06:55:58,675 UTC INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 71) WFLYUT0022: Unregistered web context: '\/bocs-ws' from server 'default-server'\n2022-05-02 06:55:58,675 UTC INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 69) WFLYUT0022: Unregistered web context: '\/' from server 'default-server'\n2022-05-02 06:55:58,691 UTC ERROR [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 70) WFLYMSGAMQ0003: Exception while stopping JMS server: java.lang.NullPointerException\n at org.apache.activemq.artemis@2.8.1\/\/org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.freezeConnections(ActiveMQServerImpl.java:1302)\n at org.apache.activemq.artemis@2.8.1\/\/org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.stop(ActiveMQServerImpl.java:1104)\n at org.apache.activemq.artemis@2.8.1\/\/org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.stop(ActiveMQServerImpl.java:1027)\n at org.apache.activemq.artemis@2.8.1\/\/org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.stop(ActiveMQServerImpl.java:872)\n at org.apache.activemq.artemis@2.8.1\/\/org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.stop(ActiveMQServerImpl.java:866)\n at org.apache.activemq.artemis@2.8.1\/\/org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.stop(JMSServerManagerImpl.java:393)\n at org.wildfly.extension.messaging-activemq\/\/org.wildfly.extension.messaging.activemq.jms.JMSService.doStop(JMSService.java:218)\n at org.wildfly.extension.messaging-activemq\/\/org.wildfly.extension.messaging.activemq.jms.JMSService.access$100(JMSService.java:65)\n at org.wildfly.extension.messaging-activemq\/\/org.wildfly.extension.messaging.activemq.jms.JMSService$2.run(JMSService.java:122)\n at java.base\/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)\n at java.base\/java.util.concurrent.FutureTask.run(FutureTask.java:264)\n at org.jboss.threads@2.3.3.Final\/\/org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)\n at org.jboss.threads@2.3.3.Final\/\/org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)\n at org.jboss.threads@2.3.3.Final\/\/org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)\n at org.jboss.threads@2.3.3.Final\/\/org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)\n at java.base\/java.lang.Thread.run(Thread.java:829)\n at org.jboss.threads@2.3.3.Final\/\/org.jboss.threads.JBossThread.run(JBossThread.java:485)\n\n2022-05-02 06:55:58,700 UTC INFO [javax.enterprise.resource.webservices.jaxws.servlet.http] (ServerService Thread Pool -- 71) WSSERVLET15: JAX-WS servlet destroyed\n2022-05-02 06:55:58,703 UTC INFO [javax.enterprise.resource.webservices.jaxws.server.http] (ServerService Thread Pool -- 71) WSSERVLET13: JAX-WS context listener destroyed\n2022-05-02 06:55:59,288 UTC INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment error.war (runtime-name: error.war) in 645ms\n...\n2022-05-02 06:55:59,502 UTC INFO [stdout] (FelixStartLevel) ERROR: Error starting file:$DOCUMENTUM\/wildfly17.0.1\/server\/DctmServer_MethodServer\/deployments\/acs.ear\/lib\/Web.jar (org.osgi.framework.BundleException: Activator start error in bundle web [4].)\n2022-05-02 06:55:59,502 UTC ERROR [stderr] (FelixStartLevel) java.lang.ExceptionInInitializerError\n2022-05-02 06:55:59,503 UTC ERROR [stderr] (FelixStartLevel) at com.documentum.acs.sdi.servlet.AcsHelper.<clinit>(AcsHelper.java:161)\n2022-05-02 06:55:59,503 UTC ERROR [stderr] (FelixStartLevel) at com.documentum.acs.sdi.servlet.ACS.<clinit>(ACS.java:404)\n2022-05-02 06:55:59,503 UTC ERROR [stderr] (FelixStartLevel) at com.documentum.acs.sdi.osgi.ServletActivator$HttpTrackerCustomizer.addingService(ServletActivator.java:48)\n2022-05-02 06:55:59,503 UTC ERROR [stderr] (FelixStartLevel) at deployment.acs.ear\/\/org.osgi.util.tracker.ServiceTracker$Tracked.trackAdding(ServiceTracker.java:1030)\n2022-05-02 06:55:59,503 UTC ERROR [stderr] (FelixStartLevel) at deployment.acs.ear\/\/org.osgi.util.tracker.ServiceTracker$Tracked.trackInitialServices(ServiceTracker.java:891)\n2022-05-02 06:55:59,504 UTC ERROR [stderr] (FelixStartLevel) at deployment.acs.ear\/\/org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:296)\n2022-05-02 06:55:59,504 UTC ERROR [stderr] (FelixStartLevel) at deployment.acs.ear\/\/org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:235)\n2022-05-02 06:55:59,504 UTC ERROR [stderr] (FelixStartLevel) at com.documentum.acs.sdi.osgi.ServletActivator.start(ServletActivator.java:25)\n2022-05-02 06:55:59,504 UTC ERROR [stderr] (FelixStartLevel) at deployment.acs.ear\/\/org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:589)\n2022-05-02 06:55:59,504 UTC ERROR [stderr] (FelixStartLevel) at deployment.acs.ear\/\/org.apache.felix.framework.Felix._startBundle(Felix.java:1671)\n2022-05-02 06:55:59,505 UTC ERROR [stderr] (FelixStartLevel) at deployment.acs.ear\/\/org.apache.felix.framework.Felix.startBundle(Felix.java:1588)\n2022-05-02 06:55:59,505 UTC ERROR [stderr] (FelixStartLevel) at deployment.acs.ear\/\/org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:1180)\n2022-05-02 06:55:59,505 UTC ERROR [stderr] (FelixStartLevel) at deployment.acs.ear\/\/org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:265)\n2022-05-02 06:55:59,505 UTC ERROR [stderr] (FelixStartLevel) at java.base\/java.lang.Thread.run(Thread.java:829)\n2022-05-02 06:55:59,513 UTC ERROR [stderr] (FelixStartLevel) Caused by: com.google.inject.CreationException: Guice creation errors:\n...\n2022-05-02 06:55:59,677 UTC INFO [org.wildfly.naming] (FelixStartLevel) WildFly Naming version 1.0.10.Final\n2022-05-02 06:55:59,838 UTC INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 68) WFLYUT0021: Registered web context: '\/ACS' for server 'default-server'\n2022-05-02 06:55:59,838 UTC INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 68) WFLYUT0022: Unregistered web context: '\/ACS' from server 'default-server'\n2022-05-02 06:55:59,908 UTC INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0019: Host default-host stopping\n2022-05-02 06:55:59,925 UTC INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0208: Stopped subdeployment (runtime-name: documentum-bocs-ws.war) in 1285ms\n2022-05-02 06:55:59,928 UTC INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0008: Undertow HTTPS listener default-https suspending\n2022-05-02 06:55:59,928 UTC INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0008: Undertow HTTP listener default suspending\n2022-05-02 06:55:59,929 UTC INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0007: Undertow HTTPS listener default-https stopped, was bound to 0.0.0.0:9082\n2022-05-02 06:55:59,929 UTC INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 0.0.0.0:9080\n2022-05-02 06:55:59,930 UTC INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0004: Undertow 2.0.21.Final stopping\n2022-05-02 06:55:59,930 UTC INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 68) WFLYCLINF0003: Stopped client-mappings cache from ejb container\n2022-05-02 06:56:00,101 UTC INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0208: Stopped subdeployment (runtime-name: bocs.war) in 1457ms\n[dmadmin@cs-0 log]$\n<\/pre><\/div>\n\n\nAs you can see on the above log, the issue appears to be on the ACS application (the ServerApps URL responds but not the ACS one) and it’s definitively caused by ActiveMQ that doesn’t start properly: “AMQ224097: Failed to start server: java.io.IOException: Input\/output error<\/em>“. Just to make sure, I checked previous logs but there really was no issues on previous startup as well as during the previous runtime. No errors at all on the JMS log files so the issue really started during this startup. The only thing that changed, and the reason for this restart, as I mentioned previously, was to update a few libraries. However, these jar files were Documentum specific, nothing related to WildFly or ActiveMQ. According to the error stack, it seemed to me like it could be caused by some kind of NFS problem. Maybe a disconnection of the NFS at the wrong moment or something similar that could cause the ActiveMQ to either lose a lock file or its status. So, I looked into the ActiveMQ specific data that WildFly creates when it starts:<\/p>\n\n\n\n[dmadmin@cs-0 log]$ ls -l ..\/data\/\ntotal 0\ndrwxrwx--- 2 dmadmin dmadmin 152 Jun 12 2021 MethodServer\ndrwxrwxr-x 5 dmadmin dmadmin 152 Jun 23 2021 activemq\ndrwxrwxr-x 3 dmadmin dmadmin 152 May 2 07:05 content\ndrwxrwxr-x 2 dmadmin dmadmin 152 Jun 23 2021 kernel\ndrwxrwxr-x 2 dmadmin dmadmin 152 Jun 23 2021 timer-service-data\ndrwxrwxr-x 3 dmadmin dmadmin 152 Jun 23 2021 tx-object-store\n[dmadmin@cs-0 log]$\n[dmadmin@cs-0 log]$ ls -l ..\/data\/activemq\/\ntotal 16\ndrwxrwxr-x 2 dmadmin dmadmin 8192 Jun 23 2021 bindings\ndrwxrwxr-x 2 dmadmin dmadmin 8192 Apr 22 18:33 journal\ndrwxrwxr-x 2 dmadmin dmadmin 152 Jun 23 2021 largemessages\n[dmadmin@cs-0 log]$\n[dmadmin@cs-0 log]$ ls -l ..\/data\/activemq\/*\nactivemq\/bindings:\ntotal 4128\n-rw-rw-r-- 1 dmadmin dmadmin 1048576 Apr 22 18:34 activemq-bindings-1.bindings\n-rw-rw-r-- 1 dmadmin dmadmin 1048576 Apr 22 18:33 activemq-bindings-2.bindings\n-rw-rw-r-- 1 dmadmin dmadmin 1048576 Apr 22 18:33 activemq-jms-1.jms\n-rw-rw-r-- 1 dmadmin dmadmin 1048576 Apr 22 18:33 activemq-jms-2.jms\n\nactivemq\/journal:\ntotal 20536\n-rw-rw-r-- 1 dmadmin dmadmin 10485760 Apr 22 18:33 activemq-data-1.amq\n-rw-rw-r-- 1 dmadmin dmadmin 10485760 Apr 22 18:33 activemq-data-2.amq\n-rw-rw-r-- 1 dmadmin dmadmin 19 Apr 22 18:34 server.lock\n\nactivemq\/largemessages:\ntotal 0\n[dmadmin@cs-0 log]$\n<\/pre><\/div>\n\n\nAll the files appeared to be present, and it looked like nothing changed them in the previous days\u2026 However, since I assumed the problem was coming from the ActiveMQ data, I still tried to shutdown WildFly, backup these data and then start it again to let it regenerate the files automatically:<\/p>\n\n\n
\n[dmadmin@cs-0 log]$ mv ..\/data\/activemq ..\/data\/activemq.old\n[dmadmin@cs-0 log]$\n[dmadmin@cs-0 log]$ ls -l ..\/data\/\ntotal 0\ndrwxrwx--- 2 dmadmin dmadmin 152 Jun 12 2021 MethodServer\ndrwxrwxr-x 5 dmadmin dmadmin 152 Jun 23 2021 activemq.old\ndrwxrwxr-x 3 dmadmin dmadmin 152 May 2 07:05 content\ndrwxrwxr-x 2 dmadmin dmadmin 152 Jun 23 2021 kernel\ndrwxrwxr-x 2 dmadmin dmadmin 152 Jun 23 2021 timer-service-data\ndrwxrwxr-x 3 dmadmin dmadmin 152 Jun 23 2021 tx-object-store\n[dmadmin@cs-0 log]$\n[dmadmin@cs-0 log]$ $JMS_HOME\/server\/startJMSCustom.sh\nStarting the Java MethodServer...\nThe Java MethodServer has been started.\n[dmadmin@cs-0 log]$\n[dmadmin@cs-0 log]$ ls -l ..\/data\/\ntotal 0\ndrwxrwx--- 2 dmadmin dmadmin 152 Jun 12 2021 MethodServer\ndrwxr-x--- 5 dmadmin dmadmin 152 May 2 07:17 activemq\ndrwxrwxr-x 5 dmadmin dmadmin 152 Jun 23 2021 activemq.old\ndrwxrwxr-x 3 dmadmin dmadmin 152 May 2 07:16 content\ndrwxrwxr-x 2 dmadmin dmadmin 152 Jun 23 2021 kernel\ndrwxrwxr-x 2 dmadmin dmadmin 152 Jun 23 2021 timer-service-data\ndrwxrwxr-x 3 dmadmin dmadmin 152 Jun 23 2021 tx-object-store\n[dmadmin@cs-0 log]$\n[dmadmin@cs-0 log]$ ls -l ..\/data\/activemq\/*\nDctmServer_MethodServer\/data\/activemq\/bindings:\ntotal 4128\n-rw-r----- 1 dmadmin dmadmin 1048576 May 2 07:17 activemq-bindings-1.bindings\n-rw-r----- 1 dmadmin dmadmin 1048576 May 2 07:17 activemq-bindings-2.bindings\n-rw-r----- 1 dmadmin dmadmin 1048576 May 2 07:17 activemq-jms-1.jms\n-rw-r----- 1 dmadmin dmadmin 1048576 May 2 07:17 activemq-jms-2.jms\n\nDctmServer_MethodServer\/data\/activemq\/journal:\ntotal 20536\n-rw-r----- 1 dmadmin dmadmin 10485760 May 2 07:17 activemq-data-1.amq\n-rw-r----- 1 dmadmin dmadmin 10485760 May 2 07:17 activemq-data-2.amq\n-rw-r----- 1 dmadmin dmadmin 19 May 2 07:17 server.lock\n\nDctmServer_MethodServer\/data\/activemq\/largemessages:\ntotal 0\n[dmadmin@cs-0 log]$\n<\/pre><\/div>\n\n\nAs you can see above, all the files were properly re-created. Therefore, checking the JMS log file now, as well as its URL:<\/p>\n\n\n
\n[dmadmin@cs-0 log]$ cat server.log\n...\n2022-05-02 07:16:56,318 UTC INFO [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final\n2022-05-02 07:16:56,782 UTC INFO [org.jboss.msc] (main) JBoss MSC version 1.4.8.Final\n2022-05-02 07:16:56,792 UTC INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final\n2022-05-02 07:16:56,958 UTC INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 17.0.1.Final (WildFly Core 9.0.2.Final) starting\n2022-05-02 07:16:57,870 UTC INFO [org.wildfly.security] (ServerService Thread Pool -- 25) ELY00001: WildFly Elytron version 1.9.1.Final\n...\n2022-05-02 07:16:59,886 UTC INFO [org.jboss.as.patching] (MSC service thread 1-1) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none\n2022-05-02 07:16:59,911 UTC INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory $DOCUMENTUM\/wildfly17.0.1\/server\/DctmServer_MethodServer\/deployments\n2022-05-02 07:16:59,917 UTC INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "ServerApps.ear" (runtime-name: "ServerApps.ear")\n2022-05-02 07:16:59,919 UTC INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "error.war" (runtime-name: "error.war")\n2022-05-02 07:16:59,918 UTC INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "acs.ear" (runtime-name: "acs.ear")\n2022-05-02 07:16:59,986 UTC INFO [org.jboss.as.remoting] (MSC service thread 1-1) WFLYRMT0001: Listening on 127.0.0.1:9084\n2022-05-02 07:17:00,027 UTC INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=$DOCUMENTUM\/wildfly17.0.1\/server\/DctmServer_MethodServer\/data\/activemq\/journal,bindingsDirectory=$DOCUMENTUM\/wildfly17.0.1\/server\/DctmServer_MethodServer\/data\/activemq\/bindings,largeMessagesDirectory=$DOCUMENTUM\/wildfly17.0.1\/server\/DctmServer_MethodServer\/data\/activemq\/largemessages,pagingDirectory=$DOCUMENTUM\/wildfly17.0.1\/server\/DctmServer_MethodServer\/data\/activemq\/paging)\n2022-05-02 07:17:00,107 UTC INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ221012: Using AIO Journal\n2022-05-02 07:17:00,136 UTC INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTPS listener default-https listening on 0.0.0.0:9082\n2022-05-02 07:17:00,213 UTC INFO [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.3.0.Final (Apache CXF 3.3.2)\n2022-05-02 07:17:00,249 UTC INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE\n2022-05-02 07:17:00,250 UTC INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP\n2022-05-02 07:17:00,254 UTC INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ\n2022-05-02 07:17:00,255 UTC INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP\n2022-05-02 07:17:00,337 UTC INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ221034: Waiting indefinitely to obtain live lock\n2022-05-02 07:17:00,337 UTC INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ221035: Live Server Obtained live lock\n2022-05-02 07:17:00,952 UTC INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-8) ISPN000128: Infinispan version: Infinispan 'Infinity Minus ONE +2' 9.4.14.Final\n2022-05-02 07:17:00,991 UTC INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-6) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor\n2022-05-02 07:17:00,991 UTC INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-5) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor\n2022-05-02 07:17:00,991 UTC INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor\n2022-05-02 07:17:00,991 UTC INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor\n2022-05-02 07:17:01,264 UTC INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ221007: Server is now live\n2022-05-02 07:17:01,265 UTC INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.8.1 [default, nodeID=db920184-c9e7-11ec-8ebb-223c2a795152]\n2022-05-02 07:17:01,395 UTC INFO [org.jboss.as.connector.deployment] (MSC service thread 1-8) WFLYJCA0007: Registered connection factory java:\/JmsXA\n2022-05-02 07:17:01,396 UTC INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 66) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss\/exported\/jms\/RemoteConnectionFactory\n2022-05-02 07:17:01,401 UTC INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 67) WFLYMSGAMQ0002: Bound messaging object to jndi name java:\/TouchRpcQueueConnectionFactory\n2022-05-02 07:17:01,410 UTC INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 67) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss\/exported\/jms\/TouchRpcQueueConnectionFactory\n2022-05-02 07:17:01,411 UTC INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 68) WFLYMSGAMQ0002: Bound messaging object to jndi name java:\/ConnectionFactory\n2022-05-02 07:17:01,411 UTC INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 63) WFLYCLINF0002: Started client-mappings cache from ejb container\n2022-05-02 07:17:01,455 UTC INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-8) AMQ151007: Resource adaptor started\n2022-05-02 07:17:01,456 UTC INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-8) IJ020002: Deployed: file:\/\/RaActivatoractivemq-ra\n2022-05-02 07:17:01,467 UTC INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0002: Bound JCA ConnectionFactory [java:\/JmsXA]\n2022-05-02 07:17:01,467 UTC INFO [org.jboss.as.connector.deployment] (MSC service thread 1-8) WFLYJCA0118: Binding connection factory named java:\/JmsXA to alias java:jboss\/DefaultJMSConnectionFactory\n2022-05-02 07:17:01,583 UTC INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 64) WFLYUT0021: Registered web context: '\/' for server 'default-server'\n...\n2022-05-02 07:17:21,632 UTC INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "acs.ear" (runtime-name : "acs.ear")\n2022-05-02 07:17:21,632 UTC INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "ServerApps.ear" (runtime-name : "ServerApps.ear")\n2022-05-02 07:17:21,633 UTC INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "error.war" (runtime-name : "error.war")\n2022-05-02 07:17:21,758 UTC INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server\n2022-05-02 07:17:21,762 UTC INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 17.0.1.Final (WildFly Core 9.0.2.Final) started in 25839ms - Started 977 of 1235 services (451 services are lazy, passive or on-demand)\n[dmadmin@cs-0 log]$\n[dmadmin@cs-0 log]$ curl -kI https:\/\/`hostname -f`:9082\/DmMethods\/servlet\/DoMethod\nHTTP\/1.1 200 OK\nConnection: keep-alive\nServer: MethodServer\nContent-Length: 144\nDate: Mon, 2 May 2022 07:18:59 GMT\n\n[dmadmin@cs-0 log]$\n[dmadmin@cs-0 log]$ curl -kI https:\/\/`hostname -f`:9082\/ACS\/servlet\/ACS\nHTTP\/1.1 200 OK\nConnection: keep-alive\nServer: MethodServer\nContent-Type: text\/plain\nContent-Length: 48\nDate: Mon, 2 May 2022 07:19:07 GMT\n\n[dmadmin@cs-0 log]$\n<\/pre><\/div>\n\n\nTherefore, this seems to have fixed properly the issue since now both URLs are responding properly. As far as I know, Documentum isn’t using the ActiveMQ included by WildFly and therefore cleaning the data shouldn’t be a problem. No issues were found after that on this environment and therefore, the issue was closed as is. No real root cause was identified either, so I will most probably continue to believe that it was linked to a network and\/or NFS issue\u2026 If you are facing the same behavior, don’t hesitate to share!<\/p>\n","protected":false},"excerpt":{"rendered":"
Documentum is an inexhaustible source of issues and that’s great because I can continuously write blogs on it, and I always have materials for that. In this blog, I will talk about the ACS not being able to start on the MethodServer because of an ActiveMQ error. As you might know, WildFly has been coming […]<\/p>\n","protected":false},"author":20,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197,525],"tags":[475,2609,2610,903,1100],"type_dbi":[],"class_list":["post-18194","post","type-post","status-publish","format-standard","hentry","category-application-integration-middleware","category-enterprise-content-management","tag-acs","tag-documentum-2","tag-jboss-2","tag-jms","tag-wildfly"],"acf":[],"yoast_head":"\n
Documentum - ACS not starting because of ActiveMQ on the MethodServer - 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\/documentum-acs-not-starting-because-of-activemq-on-the-methodserver\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Documentum - ACS not starting because of ActiveMQ on the MethodServer\" \/>\n<meta property=\"og:description\" content=\"Documentum is an inexhaustible source of issues and that’s great because I can continuously write blogs on it, and I always have materials for that. In this blog, I will talk about the ACS not being able to start on the MethodServer because of an ActiveMQ error. As you might know, WildFly has been coming […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/documentum-acs-not-starting-because-of-activemq-on-the-methodserver\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2022-07-29T18:42:00+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=\"14 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\/documentum-acs-not-starting-because-of-activemq-on-the-methodserver\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-acs-not-starting-because-of-activemq-on-the-methodserver\/\"},\"author\":{\"name\":\"Morgan Patou\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"headline\":\"Documentum – ACS not starting because of ActiveMQ on the MethodServer\",\"datePublished\":\"2022-07-29T18:42:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-acs-not-starting-because-of-activemq-on-the-methodserver\/\"},\"wordCount\":482,\"commentCount\":0,\"keywords\":[\"ACS\",\"Documentum\",\"JBoss\",\"jms\",\"WildFly\"],\"articleSection\":[\"Application integration & Middleware\",\"Enterprise content management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-acs-not-starting-because-of-activemq-on-the-methodserver\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-acs-not-starting-because-of-activemq-on-the-methodserver\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/documentum-acs-not-starting-because-of-activemq-on-the-methodserver\/\",\"name\":\"Documentum - ACS not starting because of ActiveMQ on the MethodServer - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2022-07-29T18:42:00+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-acs-not-starting-because-of-activemq-on-the-methodserver\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-acs-not-starting-because-of-activemq-on-the-methodserver\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-acs-not-starting-because-of-activemq-on-the-methodserver\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Documentum – ACS not starting because of ActiveMQ on the MethodServer\"}]},{\"@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":"Documentum - ACS not starting because of ActiveMQ on the MethodServer - 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\/documentum-acs-not-starting-because-of-activemq-on-the-methodserver\/","og_locale":"en_US","og_type":"article","og_title":"Documentum - ACS not starting because of ActiveMQ on the MethodServer","og_description":"Documentum is an inexhaustible source of issues and that’s great because I can continuously write blogs on it, and I always have materials for that. In this blog, I will talk about the ACS not being able to start on the MethodServer because of an ActiveMQ error. As you might know, WildFly has been coming […]","og_url":"https:\/\/www.dbi-services.com\/blog\/documentum-acs-not-starting-because-of-activemq-on-the-methodserver\/","og_site_name":"dbi Blog","article_published_time":"2022-07-29T18:42:00+00:00","author":"Morgan Patou","twitter_card":"summary_large_image","twitter_creator":"@MorganPatou","twitter_misc":{"Written by":"Morgan Patou","Est. reading time":"14 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-acs-not-starting-because-of-activemq-on-the-methodserver\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-acs-not-starting-because-of-activemq-on-the-methodserver\/"},"author":{"name":"Morgan Patou","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"headline":"Documentum – ACS not starting because of ActiveMQ on the MethodServer","datePublished":"2022-07-29T18:42:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-acs-not-starting-because-of-activemq-on-the-methodserver\/"},"wordCount":482,"commentCount":0,"keywords":["ACS","Documentum","JBoss","jms","WildFly"],"articleSection":["Application integration & Middleware","Enterprise content management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/documentum-acs-not-starting-because-of-activemq-on-the-methodserver\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-acs-not-starting-because-of-activemq-on-the-methodserver\/","url":"https:\/\/www.dbi-services.com\/blog\/documentum-acs-not-starting-because-of-activemq-on-the-methodserver\/","name":"Documentum - ACS not starting because of ActiveMQ on the MethodServer - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2022-07-29T18:42:00+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-acs-not-starting-because-of-activemq-on-the-methodserver\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/documentum-acs-not-starting-because-of-activemq-on-the-methodserver\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-acs-not-starting-because-of-activemq-on-the-methodserver\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Documentum – ACS not starting because of ActiveMQ on the MethodServer"}]},{"@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\/18194","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=18194"}],"version-history":[{"count":1,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/18194\/revisions"}],"predecessor-version":[{"id":18195,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/18194\/revisions\/18195"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=18194"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=18194"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=18194"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=18194"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}