[J2EE] OutSystems Services do not Start

[J2EE] OutSystems Services do not Start

  
Symptoms

After starting OutSystems services the status is “STOPPED”:

# service outsystems status
OutSystems Log Service - STOPPED
OutSystems Deployment Controller Service - STOPPED
OutSystems Deployment Service - STOPPED
OutSystems Scheduler Service - STOPPED

Using linux top monitoring tool ( # top u outsystems) we can check that there are “sleep” commands running:

top - 15:09:56 up 14 days, 21:22, 1 user, load average: 0.36, 0.18, 0.11
Tasks: 64 total, 2 running, 62 sleeping, 0 stopped, 0 zombie
Cpu(s): 1.3% us, 10.2% sy, 0.0% ni, 83.5% id, 4.6% wa, 0.3% hi, 0.0% si
Mem: 1814932k total, 1473828k used, 341104k free, 92264k buffers
Swap: 2031608k total, 636k used, 2030972k free, 597764k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
16817 outsyste 18 0 4440 596 504 S 1.0 0.0 0:00.03 sleep
16818 outsyste 18 0 5224 596 504 S 0.7 0.0 0:00.02 sleep
16820 outsyste 16 0 3988 596 504 S 0.7 0.0 0:00.02 sleep
16821 outsyste 16 0 4716 596 504 S 0.7 0.0 0:00.02 sleep
16746 outsyste 19 0 5568 1184 1036 S 0.0 0.1 0:00.03 rmi.sh
16749 outsyste 19 0 256m 11m 7564 S 0.0 0.6 0:00.53 rmiregistry
16762 outsyste 16 0 5696 1188 1036 S 0.0 0.1 0:00.04 os.controller.s
16765 outsyste 16 0 4840 1188 1036 S 0.0 0.1 0:00.05 os.log.service.
16767 outsyste 16 0 5344 1188 1036 S 0.0 0.1 0:00.09 os.scheduler.se
16770 outsyste 17 0 5540 1184 1036 S 0.0 0.1 0:00.04 os.deployment.s


Cause

One possible cause for this problem can be incorrect PATH parameters in a configuration file. Another cause is invalid permissions given to user “outsystems” (check section “java.lang.NoClassDefFoundError error running serversetup.sh or scinstall.sh”).


Resolution

First you should check, running Configuration Tool (serversetup.sh), if in “Ant Executable Location”, “JBoss Location” and “Installation Full Directory” configurations are correct.

Next, check the content of file properties.sh:

# cat properties.sh CURRENTHOSTIP=localhost JBOSSDIR=/opt/jboss-4.0.3SP1 JBOSSLIBDIR=/opt/jboss-4.0.3SP1/server/outsystems/lib JBOSSCLIENTLIBDIR=/opt/jboss-4.0.3SP1/client ANT_HOME=/opt/apache-ant-1.6.2 JAVA_HOME=/usr/java/jdk1.5.0_10
export NLS_CHARACTERSET=WE8MSWIN1252
export NLS_LANG=AMERICAN

Check if settings JBOSSDIR, JBOSSLIBDIR, JBOSSCLIENTLIBDIR, ANT_HOME and JAVA_HOME exist, are correct and if user outsystems can access them.


Notice that in some uncertified operating systems, for instance some versions of Fedora, you may need to add to this file the JAVA_HOME setting. Also check if in the beginning of the rmi.sh the following command (. properties.sh ) is present:

# cat rmi.sh
#!/bin/sh
. properties.sh

# set classpath
...

Now you shall restart the OutSystems services (service outsystems restart) and verify that the services are running:

# service outsystems status
OutSystems Log Service - RUNNING
OutSystems Deployment Controller Service - RUNNING
OutSystems Deployment Service - RUNNING
OutSystems Scheduler Service - RUNNING


Regards,

João Portela