Issue
LiquidOffice fails to start
The following entry is displayed in the \logs\Liquidoffice.stdOut:
23 Apr 2014 11:20:06 - [Thread[Thread-155,5,main]] - - Total tables count: 86
23 Apr 2014 11:20:06 - [Thread[Thread-155,5,main]] - - Database initialization processed time: 00:00:31.567
23 Apr 2014 11:20:06 - [Thread[Thread-155,5,main]] - The Process Server cannot start. The maximum number of active Process Servers in this cluster allowed by the license (1) has already been reached.
23 Apr 2014 11:20:06 - [Thread[Thread-155,5,main]] - Active Server Thread has terminated.
23 Apr 2014 11:20:07 - [Thread[Thread-155,5,main]] - ProcessServer JMXConnectorServer: service:jmx:burlap://localhost:80080/xmlserver/loxmlmx
23 Apr 2014 11:20:07 - [Thread[Thread-155,5,main]] - Loading Software Sensors descriptor: file:/usr/local/Xerox/DocuShare/LiquidOffice/Resources/process/WEB-INF/lib/mlet.xml
23 Apr 2014 11:20:07 - [Thread[Thread-155,5,main]] - ... MBean: LOMX:name=com.cardiff.bpm.mbeans.Authenticator,type=LOSYS registered with MBeanServer(LOXMLMX), accessible by: Anonymous
23 Apr 2014 11:20:07 - [Thread[Thread-155,5,main]] - ... MBean: KPISettingsPersister registered with MBeanServer(LOXMLMX), accessible by: Administrator
23 Apr 2014 11:20:07 - [Thread[Thread-155,5,main]] - ... MBean: com.cardiff.bpm.mbeans.DBConnectionInfo registered with MBeanServer(LOXMLMX), accessible by: Anonymous
23 Apr 2014 11:20:07 - [Thread[Thread-155,5,main]] - ... MBean: com.cardiff.bpm.mbeans.ProcessCount registered with MBeanServer(LOXMLMX), accessible by: Administrator
23 Apr 2014 11:20:08 - [Thread[Thread-155,5,main]] - ... MBean: com.cardiff.bpm.mbeans.TaskDuration registered with MBeanServer(LOXMLMX), accessible by: Anonymous
23 Apr 2014 11:20:08 - [Thread[Thread-155,5,main]] - ... MBean: com.cardiff.bpm.mbeans.WorkQueueCount registered with MBeanServer(LOXMLMX), accessible by: Anonymous
23 Apr 2014 11:20:08 - [Thread[Thread-155,5,main]] - ... 4 Custom Software Sensors loaded.
23 Apr 2014 11:20:08 - [Thread[Thread-155,5,main]] - service:jmx:burlap://localhost:80080/xmlserver/loxmlmx
23 Apr 2014 11:20:10 - [Thread[Thread-155,5,main]] - PresentationServer JMXConnectorServer: service:jmx:burlap+ssl://localhost:80080/lomx
23 Apr 2014 11:20:13 - [Thread[Thread-155,5,main]] - ```` RemoteMBeanProxy registered for: LOMX:name=com.cardiff.bpm.mbeans.ProcessCount,type=LOKPI
23 Apr 2014 11:20:13 - [Thread[Thread-155,5,main]] - ```` RemoteMBeanProxy registered for: LOMX:name=com.cardiff.bpm.mbeans.Authenticator,type=LOSYS
23 Apr 2014 11:20:13 - [Thread[Thread-155,5,main]] - ```` RemoteMBeanProxy registered for: LOMX:name=KPISettingsPersister,type=LOSYS
23 Apr 2014 11:20:13 - [Thread[Thread-155,5,main]] - ```` RemoteMBeanProxy registered for: LOMX:name=com.cardiff.bpm.mbeans.DBConnectionInfo,type=LOKPI
23 Apr 2014 11:20:13 - [Thread[Thread-155,5,main]] - ```` RemoteMBeanProxy registered for: LOMX:name=com.cardiff.bpm.mbeans.TaskDuration,type=LOKPI
23 Apr 2014 11:20:13 - [Thread[Thread-155,5,main]] - ```` RemoteMBeanProxy registered for: LOMX:name=com.cardiff.bpm.mbeans.WorkQueueCount,type=LOKPI
23 Apr 2014 11:20:13 - [Thread[Thread-155,5,main]] - Starting lomx connector proxy..
LiquidOffice.stdError shows:
23 Apr 2014 11:20:11 - [Thread[Thread-157,5,main]] - INFO: Server startup in 47294 ms
23 Apr 2014 11:20:13 - [Thread[Thread-157,5,main]] - Apr 23, 2014 11:20:12 AM org.apache.catalina.core.StandardWrapperValve invoke
23 Apr 2014 11:20:13 - [Thread[Thread-157,5,main]] - INFO: Servlet lfserver is currently unavailable
23 Apr 2014 11:20:13 - [Thread[Thread-157,5,main]] - Apr 23, 2014 11:20:12 AM org.apache.catalina.core.StandardWrapperValve invoke
23 Apr 2014 11:20:13 - [Thread[Thread-157,5,main]] - INFO: Servlet lfserver is currently unavailable
Reason / Possible Cause:
There are two Installations of DocuShare LiquidOffice pointed to the same Database. For example: A Test Server and Production Server.
Solution
This is not allowed and needs to be reconfigured so each installation has its own Database instance.
Solution Published: May 6th, 2014
Solution ID: 1489
Keywords:
The Process Server cannot start. The maximum number of active Process Servers in this cluster allowed by the license (1) has already been reached.