Skip to main content
ExLibris
Ex Libris Knowledge Center

JBOSS will not start

Overview

When trying to start JBOSS the following output is received: 

##################################### 
# jboss_startup # 
##################################### 

[1] jboss_startup initialization 
[2] current directory is: /exlibris/dtl/j3_1/digitool/home/system/bin/. 
[3] checking for pid files 
PID file exists. JBOSS has already been started up 


Although the start-up script claims that the application is started, this is not the case. 

Solution

First Step - See if there is a JBOSS Process running


command jps -m will show output similar to the following when JBOSS is running: 
>jps -m 
16114 Jps -m 
14375 Bootstrap start
(Tomcat is running) 
14578 Main -b 0.0.0.0 (JBOSS is running - if this line "Main -b 0.0.0.0" is missing then JBOSS is NOT running) ..

Second Step

When JBOSS starts the following file is created 
/exlibris/dtl/j3_x/digitool/home/system/thirdparty/openserver/server/default/log/run.sh.2.pid 
This file is a text file containing the Process ID (PID) allocated to the instance of JBOSS by the operating system. 
When JBOSS is closed gracefully this file is deleted. 
The JBOSS startup script checks for the presence of this file, and if it exists, assumes that JBOSS is already running, and ends without any further action. 
This is intended to prevent multiple instances of JBOSS from being started.

If we have ascertained that JBOSS is not running we must delete this file to enable JBOSS to start.

 

To easily access the directory type:
>jb_log 

In order to allow JBOSS to start this file must first be deleted: 
>rm -f run.sh.2.pid 

Start JBOSS

Start JBOSS
>cd $jdtlh_bin 
>./jboss_startup.sh

  • Was this article helpful?
//Feedback