While working on a very big Documentum project with several other teams, some people were complaining that the JMS wouldn’t start anymore on one of the DEV environments. It is kind of rare to face an issue with the JMS itself (JBoss works pretty well usually…) so I was interested in checking this. This was a Documentum 7.2 environment but I’m sure it would apply to older versions as well as newer versions (7.x, 16.4, …). This was the content of the JMS console output:<\/p>\n
[dmadmin@content_server_01 ~]$ cat $JMS_HOME\/server\/nohup-JMS.out\n...\n2018-06-12 07:15:54,765 UTC INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA\n2018-06-12 07:15:54,968 UTC INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA\n2018-06-12 07:15:55,019 UTC INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final \"Brontes\" starting\n2018-06-12 07:15:56,415 UTC INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)\n2018-06-12 07:15:56,417 UTC INFO [org.xnio] XNIO Version 3.0.3.GA\n2018-06-12 07:15:56,428 UTC INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA\n2018-06-12 07:15:56,437 UTC INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA\n2018-06-12 07:15:56,448 UTC INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers\n2018-06-12 07:15:56,478 UTC INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 27) JBAS016200: Activating ConfigAdmin Subsystem\n2018-06-12 07:15:56,486 UTC INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 32) JBAS010280: Activating Infinispan subsystem.\n2018-06-12 07:15:56,510 UTC INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 40) JBAS011940: Activating OSGi Subsystem\n2018-06-12 07:15:56,518 UTC INFO [org.jboss.as.naming] (ServerService Thread Pool -- 39) JBAS011800: Activating Naming Subsystem\n2018-06-12 07:15:56,527 UTC INFO [org.jboss.as.security] (ServerService Thread Pool -- 45) JBAS013101: Activating Security Subsystem\n2018-06-12 07:15:56,533 UTC INFO [org.jboss.as.security] (MSC service thread 1-9) JBAS013100: Current PicketBox version=4.0.7.Final\n2018-06-12 07:15:56,535 UTC INFO [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)\n2018-06-12 07:15:56,548 UTC INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 49) JBAS015537: Activating WebServices Extension\n2018-06-12 07:15:56,585 UTC INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service\n2018-06-12 07:15:56,594 UTC INFO [org.jboss.as.mail.extension] (MSC service thread 1-12) JBAS015400: Bound mail session \n2018-06-12 07:15:56,688 UTC INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-8) JBoss Web Services - Stack CXF Server 4.0.2.GA\n2018-06-12 07:15:56,727 UTC INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-10) Starting Coyote HTTP\/1.1 on http--0.0.0.0-9080\n2018-06-12 07:15:56,821 UTC INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-13) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=$JMS_HOME\/server\/DctmServer_MethodServer\/data\/messagingjournal,bindingsDirectory=$JMS_HOME\/server\/DctmServer_MethodServer\/data\/messagingbindings,largeMessagesDirectory=$JMS_HOME\/server\/DctmServer_MethodServer\/data\/messaginglargemessages,pagingDirectory=$JMS_HOME\/server\/DctmServer_MethodServer\/data\/messagingpaging)\n2018-06-12 07:15:56,827 UTC INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-13) Waiting to obtain live lock\n2018-06-12 07:15:56,852 UTC INFO [org.hornetq.core.persistence.impl.journal.JournalStorageManager] (MSC service thread 1-13) Using AIO Journal\n2018-06-12 07:15:56,923 UTC INFO [org.hornetq.core.server.impl.AIOFileLockNodeManager] (MSC service thread 1-13) Waiting to obtain live lock\n2018-06-12 07:15:56,924 UTC INFO [org.hornetq.core.server.impl.AIOFileLockNodeManager] (MSC service thread 1-13) Live Server Obtained live lock\n2018-06-12 07:15:56,981 UTC INFO [org.jboss.as.remoting] (MSC service thread 1-5) JBAS017100: Listening on 0.0.0.0\/0.0.0.0:9092\n2018-06-12 07:15:56,982 UTC INFO [org.jboss.as.remoting] (MSC service thread 1-14) JBAS017100: Listening on \/127.0.0.1:9084\n2018-06-12 07:15:56,996 UTC INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-10) JBAS015012: Started FileSystemDeploymentService for directory $JMS_HOME\/server\/DctmServer_MethodServer\/deployments\n2018-06-12 07:15:57,019 UTC INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment bundle.jar\n2018-06-12 07:15:57,020 UTC INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment bundle.jar\n2018-06-12 07:15:57,021 UTC INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment bundle.jar\n2018-06-12 07:15:57,023 UTC INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment bundle.jar\n2018-06-12 07:15:57,024 UTC INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment bundle.jar\n2018-06-12 07:15:57,025 UTC INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment bundle.jar\n2018-06-12 07:15:57,026 UTC INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found ServerApps.ear in deployment directory. To trigger deployment create a file called ServerApps.ear.dodeploy\n2018-06-12 07:15:57,027 UTC INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found XhiveConnector.ear in deployment directory. To trigger deployment create a file called XhiveConnector.ear.dodeploy\n2018-06-12 07:15:57,028 UTC INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found bpm.ear in deployment directory. To trigger deployment create a file called bpm.ear.dodeploy\n2018-06-12 07:15:57,029 UTC INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found acs.ear in deployment directory. To trigger deployment create a file called acs.ear.dodeploy\n2018-06-12 07:15:57,090 UTC INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP\/1.1 on http-0.0.0.0-0.0.0.0-9082\n2018-06-12 07:15:57,235 UTC INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-13) Started Netty Acceptor version 3.2.5.Final-a96d88c 0.0.0.0:9090 for CORE protocol\n2018-06-12 07:15:57,237 UTC INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-13) Started Netty Acceptor version 3.2.5.Final-a96d88c 0.0.0.0:9091 for CORE protocol\n2018-06-12 07:15:57,239 UTC INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-13) Server is now live\n2018-06-12 07:15:57,239 UTC INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-13) HornetQ Server version 2.2.13.Final (HQ_2_2_13_FINAL_AS7, 122) [b774a781-a4da-11e6-a1e8-005056082847]) started\n2018-06-12 07:15:57,256 UTC INFO [org.jboss.as.messaging] (MSC service thread 1-14) JBAS011601: Bound messaging object to jndi name java:jboss\/exported\/jms\/RemoteConnectionFactory\n2018-06-12 07:15:57,257 UTC INFO [org.jboss.as.messaging] (MSC service thread 1-14) JBAS011601: Bound messaging object to jndi name java:\/RemoteConnectionFactory\n2018-06-12 07:15:57,258 UTC INFO [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011601: Bound messaging object to jndi name java:\/ConnectionFactory\n2018-06-12 07:15:57,261 UTC INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-9) trying to deploy queue jms.queue.touchRpcQueue\n2018-06-12 07:15:57,267 UTC INFO [org.jboss.as.messaging] (MSC service thread 1-9) JBAS011601: Bound messaging object to jndi name java:jboss\/exported\/jms\/queue\/touchRpcQueue\n2018-06-12 07:15:57,268 UTC INFO [org.jboss.as.messaging] (MSC service thread 1-9) JBAS011601: Bound messaging object to jndi name java:\/queue\/touchRpcQueue\n2018-06-12 07:15:57,269 UTC INFO [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:\/TouchRpcQueueConnectionFactory\n2018-06-12 07:15:57,270 UTC INFO [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:jboss\/exported\/jms\/TouchRpcQueueConnectionFactory\n2018-06-12 07:15:57,301 UTC INFO [org.jboss.as.deployment.connector] (MSC service thread 1-8) JBAS010406: Registered connection factory java:\/JmsXA\n2018-06-12 07:15:57,311 UTC INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-8) HornetQ resource adaptor started\n2018-06-12 07:15:57,312 UTC INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-8) IJ020002: Deployed: file:\/\/RaActivatorhornetq-ra\n2018-06-12 07:15:57,316 UTC INFO [org.jboss.as.deployment.connector] (MSC service thread 1-4) JBAS010401: Bound JCA ConnectionFactory \n2018-06-12 07:15:57,343 UTC ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) Operation (\"add\") failed - address: ([(\"deployment\" => \"bundle.jar\")]) - failure description: \"JBAS014803: Duplicate resource [(\"deployment\" => \"bundle.jar\")]\"\n2018-06-12 07:15:57,348 UTC ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS014654: Composite operation was rolled back\n2018-06-12 07:15:57,349 UTC INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http:\/\/127.0.0.1:9085\n2018-06-12 07:15:57,350 UTC ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS014654: Composite operation was rolled back\n2018-06-12 07:15:57,350 UTC INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final \"Brontes\" started in 2885ms - Started 148 of 226 services (78 services are passive or on-demand)\n2018-06-12 07:15:57,351 UTC ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS014654: Composite operation was rolled back\n2018-06-12 07:15:57,353 UTC ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS014654: Composite operation was rolled back\n2018-06-12 07:15:57,354 UTC ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS014654: Composite operation was rolled back\n2018-06-12 07:15:57,355 UTC ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {\"JBAS014653: Composite operation failed and was rolled back. Steps that failed:\" => {\"Operation step-1\" => \"JBAS014803: Duplicate resource [(\"deployment\" => \"bundle.jar\")]\"}}\n2018-06-12 07:15:57,357 UTC ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) undefined\n2018-06-12 07:15:57,358 UTC ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) undefined\n2018-06-12 07:15:57,359 UTC ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) undefined\n2018-06-12 07:15:57,359 UTC ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) undefined<\/pre>\n <\/p>\n
This was linked to deployments so I tried as a first step to force a redeploy of all Documentum applications. It can be done as shown below and in those cases, it is better to stop the JMS before otherwise it will try to redeploy the applications on the fly, which might work but you aren’t sure they will start again on next startup… So here are the steps:<\/p>\n
[dmadmin@content_server_01 ~]$ cd $JMS_HOME\/server\/DctmServer_MethodServer\/deployments\n[dmadmin@content_server_01 deployments]$ \n[dmadmin@content_server_01 deployments]$ find . -maxdepth 1 -name \"*.failed\"\n.\/acs.ear.failed\n.\/ServerApps.ear.failed\n.\/error.war.failed\n.\/bpm.ear.failed\n[dmadmin@content_server_01 deployments]$ \n[dmadmin@content_server_01 deployments]$ \n[dmadmin@content_server_01 deployments]$ for i in `find . -maxdepth 1 -name \"*.failed\"`; do name=`echo ${i} | sed 's,.failed,.dodeploy,'`; mv ${i} ${name}; done\n[dmadmin@content_server_01 deployments]$<\/pre>\n <\/p>\n
Then you can just start again the JMS:<\/p>\n
[dmadmin@content_server_01 deployments]$ $JMS_HOME\/server\/startJMS.sh\nStarting the JMS...\nThe JMS process has been started.\n[dmadmin@content_server_01 deployments]$<\/pre>\n <\/p>\n
Unfortunately in this case, the JMS logs were similar and the Documentum applications were still in failed. So looking closer at these logs, it seemed to be related to a bundle.jar file:<\/p>\n
[dmadmin@content_server_01 deployments]$ find . -name bundle.jar\n.\/felix-cache\/bundle3\/version0.0\/bundle.jar\n.\/felix-cache\/bundle5\/version0.0\/bundle.jar\n.\/felix-cache\/bundle1\/version0.0\/bundle.jar\n.\/felix-cache\/bundle4\/version0.0\/bundle.jar\n.\/felix-cache\/bundle6\/version0.0\/bundle.jar\n.\/felix-cache\/bundle2\/version0.0\/bundle.jar\n[dmadmin@content_server_01 deployments]$\n[dmadmin@content_server_01 deployments]$ ls felix-cache\/*\nfelix-cache\/bundle0:\nbundle.id\n\nfelix-cache\/bundle1:\nbundle.id bundle.lastmodified bundle.location bundle.startlevel bundle.state version0.0\n\nfelix-cache\/bundle2:\nbundle.id bundle.lastmodified bundle.location bundle.startlevel bundle.state version0.0\n\nfelix-cache\/bundle3:\nbundle.id bundle.lastmodified bundle.location bundle.startlevel bundle.state version0.0\n\nfelix-cache\/bundle4:\nbundle.id bundle.lastmodified bundle.location bundle.startlevel bundle.state version0.0\n\nfelix-cache\/bundle5:\nbundle.id bundle.lastmodified bundle.location bundle.startlevel bundle.state version0.0\n\nfelix-cache\/bundle6:\nbundle.id bundle.lastmodified bundle.location bundle.startlevel bundle.state version0.0\n[dmadmin@content_server_01 deployments]$\n[dmadmin@content_server_01 deployments]$\n[dmadmin@content_server_01 deployments]$ for i in `ls felix-cache\/`; do echo \"felix-cache\/${i}:\"; cat felix-cache\/${i}\/bundle.location; echo; echo; done\nfelix-cache\/bundle0:\ncat: felix-cache\/bundle0\/bundle.location: No such file or directory\n\n\nfelix-cache\/bundle1:\nfile:$JMS_HOME\/server\/DctmServer_MethodServer\/deployments\/acs.ear\/lib\/HttpService.jar\n\nfelix-cache\/bundle2:\nfile:$JMS_HOME\/server\/DctmServer_MethodServer\/deployments\/acs.ear\/lib\/HttpServiceImpl.jar\n\nfelix-cache\/bundle3:\nfile:$JMS_HOME\/server\/DctmServer_MethodServer\/deployments\/acs.ear\/lib\/Common.jar\n\nfelix-cache\/bundle4:\nfile:$JMS_HOME\/server\/DctmServer_MethodServer\/deployments\/acs.ear\/lib\/Web.jar\n\nfelix-cache\/bundle5:\nfile:$JMS_HOME\/server\/DctmServer_MethodServer\/deployments\/acs.ear\/lib\/Jmx.jar\n\nfelix-cache\/bundle6:\nfile:$JMS_HOME\/server\/DctmServer_MethodServer\/deployments\/acs.ear\/lib\/org.apache.felix.bundlerepository-1.2.1.jar\n\n[dmadmin@content_server_01 deployments]$\n[dmadmin@content_server_01 deployments]$ diff felix-cache\/bundle1\/version0.0\/bundle.jar $JMS_HOME\/server\/DctmServer_MethodServer\/deployments\/acs.ear\/lib\/HttpService.jar\n[dmadmin@content_server_01 deployments]$\n[dmadmin@content_server_01 deployments]$ diff felix-cache\/bundle3\/version0.0\/bundle.jar $JMS_HOME\/server\/DctmServer_MethodServer\/deployments\/acs.ear\/lib\/Common.jar\n[dmadmin@content_server_01 deployments]$<\/pre>\n <\/p>\n
This felix-cache is normally created by the ACS when you start it and it will normally be placed in the folder from where you start the JMS. In this case, it was under the deployments folder, probably because someone started the JMS using the startMethodServer.sh script directly and he didn’t use our custom start script (startJMS.sh as you can see above and below) which actually takes care of that and switch to the correct folder before (and with the proper nohup, aso…). Because it was created under the deployments folder, the JMS was trying to deploy it as any other applications and so it failed. As you can see above, the file “bundle.jar” (in the different folders) is actually a copy of some of the ACS library files – the ones mentioned in the bundle.location – that has been put to the felix-cache by the ACS.<\/p>\n
As you know, with a newly installed JMS for Documentum, there is no felix-cache folder under the deployments. What you can find here are the ServerApps, ACS or BPM for example but that’s pretty much it. Therefore, to solve this issue, simply remove the felix-cache folder, force a new deployment of all Documentum applications, restart it again properly and it should be good then:<\/p>\n
[dmadmin@content_server_01 deployments]$ $JMS_HOME\/server\/stopMethodServer.sh; sleep 5; ps -ef | grep MethodServer\n[dmadmin@content_server_01 deployments]$\n[dmadmin@content_server_01 deployments]$ rm -rf felix-cache\/\n[dmadmin@content_server_01 deployments]$\n[dmadmin@content_server_01 deployments]$ find . -maxdepth 1 -name \"*.failed\"\n.\/acs.ear.failed\n.\/ServerApps.ear.failed\n.\/error.war.failed\n.\/bpm.ear.failed\n[dmadmin@content_server_01 deployments]$\n[dmadmin@content_server_01 deployments]$ for i in `find . -maxdepth 1 -name \"*.failed\"`; do name=`echo ${i} | sed 's,.failed,.dodeploy,'`; mv ${i} ${name}; done\n[dmadmin@content_server_01 deployments]$\n[dmadmin@content_server_01 deployments]$ $JMS_HOME\/server\/startJMS.sh\nStarting the JMS...\nThe JMS process has been started.\n[dmadmin@content_server_01 deployments]$<\/pre>\n <\/p>\n
Then checking if the issue is gone and if all the applications are now properly deployed:<\/p>\n
[dmadmin@content_server_01 deployments]$ grep -E \" deployment | Deployed \" $JMS_HOME\/server\/nohup-JMS.out\n2018-06-12 07:30:15,142 UTC INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found ServerApps.ear in deployment directory. To trigger deployment create a file called ServerApps.ear.dodeploy\n2018-06-12 07:30:15,144 UTC INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found XhiveConnector.ear in deployment directory. To trigger deployment create a file called XhiveConnector.ear.dodeploy\n2018-06-12 07:30:15,145 UTC INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found bpm.ear in deployment directory. To trigger deployment create a file called bpm.ear.dodeploy\n2018-06-12 07:30:15,146 UTC INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found acs.ear in deployment directory. To trigger deployment create a file called acs.ear.dodeploy\n2018-06-12 07:30:15,503 UTC INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file:\/\/RaActivatorhornetq-ra\n2018-06-12 07:30:15,535 UTC INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of \"bpm.ear\"\n2018-06-12 07:30:15,535 UTC INFO [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015876: Starting deployment of \"ServerApps.ear\"\n2018-06-12 07:30:15,535 UTC INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of \"error.war\"\n2018-06-12 07:30:15,535 UTC INFO [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015876: Starting deployment of \"acs.ear\"\n2018-06-12 07:30:17,824 UTC INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of \"documentum-bocs-ws.war\"\n2018-06-12 07:30:17,825 UTC INFO [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015876: Starting deployment of \"bocs.war\"\n2018-06-12 07:30:18,093 UTC INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[\/ACS]] (MSC service thread 1-16) Initializing CORS filter as per the deployment descriptor\n2018-06-12 07:30:18,608 UTC INFO [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015876: Starting deployment of \"DmMethods.war\"\n2018-06-12 07:30:18,608 UTC INFO [org.jboss.as.server.deployment] (MSC service thread 1-9) JBAS015876: Starting deployment of \"DmMail.war\"\n2018-06-12 07:30:18,904 UTC INFO [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015876: Starting deployment of \"bpm.war\"\n2018-06-12 07:30:32,017 UTC INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed \"bpm.ear\"\n2018-06-12 07:30:32,019 UTC INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed \"error.war\"\n2018-06-12 07:30:32,020 UTC INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed \"acs.ear\"\n2018-06-12 07:30:32,021 UTC INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed \"ServerApps.ear\"\n[dmadmin@content_server_01 deployments]$<\/pre>\n <\/p>\n
So takes care when you start the JMS, if you do not have any custom script (it’s pretty much mandatory for the JMS!) or if you do not change the working directory before executing the startMethodServer.sh script, you might have some surprises.<\/p>\n
<\/p>\n
Edit: After writing this blog, I searched the OTX website for something related to this and found that there is a KB (KB7795388) about this but I think this blog still makes sense because it provides more information and some explanation. That’s a bad habit of mine, I usually try fixing things myself before checking the OTX website because I don’t like it and the less I’m using it, the better.<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
While working on a very big Documentum project with several other teams, some people were complaining that the JMS wouldn’t start anymore on one of the DEV environments. It is kind of rare to face an issue with the JMS itself (JBoss works pretty well usually…) so I was interested in checking this. This was […]<\/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":[1391,129,903,872],"type_dbi":[],"class_list":["post-11394","post","type-post","status-publish","format-standard","hentry","category-application-integration-middleware","category-enterprise-content-management","tag-bundle-jar","tag-documentum","tag-jms","tag-server"],"acf":[],"yoast_head":"\n
Documentum - Unable to restart a JMS, failed deployment of bundle.jar - 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-unable-to-restart-a-jms-failed-deployment-of-bundle-jar\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Documentum - Unable to restart a JMS, failed deployment of bundle.jar\" \/>\n<meta property=\"og:description\" content=\"While working on a very big Documentum project with several other teams, some people were complaining that the JMS wouldn’t start anymore on one of the DEV environments. It is kind of rare to face an issue with the JMS itself (JBoss works pretty well usually…) so I was interested in checking this. This was […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/documentum-unable-to-restart-a-jms-failed-deployment-of-bundle-jar\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2018-07-01T17:21:53+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-unable-to-restart-a-jms-failed-deployment-of-bundle-jar\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-unable-to-restart-a-jms-failed-deployment-of-bundle-jar\/\"},\"author\":{\"name\":\"Morgan Patou\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"headline\":\"Documentum – Unable to restart a JMS, failed deployment of bundle.jar\",\"datePublished\":\"2018-07-01T17:21:53+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-unable-to-restart-a-jms-failed-deployment-of-bundle-jar\/\"},\"wordCount\":565,\"commentCount\":0,\"keywords\":[\"bundle.jar\",\"Documentum\",\"jms\",\"server\"],\"articleSection\":[\"Application integration & Middleware\",\"Enterprise content management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-unable-to-restart-a-jms-failed-deployment-of-bundle-jar\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-unable-to-restart-a-jms-failed-deployment-of-bundle-jar\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/documentum-unable-to-restart-a-jms-failed-deployment-of-bundle-jar\/\",\"name\":\"Documentum - Unable to restart a JMS, failed deployment of bundle.jar - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2018-07-01T17:21:53+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-unable-to-restart-a-jms-failed-deployment-of-bundle-jar\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-unable-to-restart-a-jms-failed-deployment-of-bundle-jar\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-unable-to-restart-a-jms-failed-deployment-of-bundle-jar\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Documentum – Unable to restart a JMS, failed deployment of bundle.jar\"}]},{\"@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 - Unable to restart a JMS, failed deployment of bundle.jar - 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-unable-to-restart-a-jms-failed-deployment-of-bundle-jar\/","og_locale":"en_US","og_type":"article","og_title":"Documentum - Unable to restart a JMS, failed deployment of bundle.jar","og_description":"While working on a very big Documentum project with several other teams, some people were complaining that the JMS wouldn’t start anymore on one of the DEV environments. It is kind of rare to face an issue with the JMS itself (JBoss works pretty well usually…) so I was interested in checking this. This was […]","og_url":"https:\/\/www.dbi-services.com\/blog\/documentum-unable-to-restart-a-jms-failed-deployment-of-bundle-jar\/","og_site_name":"dbi Blog","article_published_time":"2018-07-01T17:21:53+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-unable-to-restart-a-jms-failed-deployment-of-bundle-jar\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-unable-to-restart-a-jms-failed-deployment-of-bundle-jar\/"},"author":{"name":"Morgan Patou","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"headline":"Documentum – Unable to restart a JMS, failed deployment of bundle.jar","datePublished":"2018-07-01T17:21:53+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-unable-to-restart-a-jms-failed-deployment-of-bundle-jar\/"},"wordCount":565,"commentCount":0,"keywords":["bundle.jar","Documentum","jms","server"],"articleSection":["Application integration & Middleware","Enterprise content management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/documentum-unable-to-restart-a-jms-failed-deployment-of-bundle-jar\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-unable-to-restart-a-jms-failed-deployment-of-bundle-jar\/","url":"https:\/\/www.dbi-services.com\/blog\/documentum-unable-to-restart-a-jms-failed-deployment-of-bundle-jar\/","name":"Documentum - Unable to restart a JMS, failed deployment of bundle.jar - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2018-07-01T17:21:53+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-unable-to-restart-a-jms-failed-deployment-of-bundle-jar\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/documentum-unable-to-restart-a-jms-failed-deployment-of-bundle-jar\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-unable-to-restart-a-jms-failed-deployment-of-bundle-jar\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Documentum – Unable to restart a JMS, failed deployment of bundle.jar"}]},{"@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\/11394","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=11394"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/11394\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=11394"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=11394"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=11394"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=11394"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}