JIRA Install hangs when trying to connect to Oracle 11G database

[Patrick Toma]

I am trying to install JIRA 5 with an Oracle 11G database. I have filled out my dbconfig.xml file with all of the DB parameters. When I start JIRA, it just hangs at one point saying:

2012-03-14 10:26:14,250 main INFO jira.config.database.DatabaseConfigurationManagerImpl Now running Database Checklist Launcher

The log shows no other errors. Not sure what my next steps should be.

Using the same database parameters, I can connect from my JIRA server to the database using SQLPlus..

==================================================

bash-3.2$ sqlplus jiradbuser/XXXXXXXX@JIRA01

SQL*Plus: Release 11.2.0.2.0 Production on Thu Mar 15 13:40:44 2012

Copyright (c) 1982, 2010, Oracle. All rights reserved.

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> select sysdate from dual;

SYSDATE

---------

15-MAR-12

SQL>

========================================

****************

JIRA starting...

****************

2012-03-14 10:26:13,932 main INFO atlassian.jira.startup.JiraStartupLogger

___ Environment _____________________________

JIRA Build : 5.0#713-sha1:aec58e27a0d402341b1f1be2fc8c0204a0b070f6

Build Date : Wed Feb 15 00:00:00 PST 2012

JIRA Installation Type : EAR/WAR

Application Server : Apache Tomcat/6.0.35 - Servlet API 2.5

Java Version : 1.6.0_18 - Sun Microsystems Inc.

Current Working Directory : /apps/jira-home/log

Maximum Allowable Memory : 455MB

Total Memory : 122MB

Free Memory : 87MB

Used Memory : 35MB

Memory Pool: Code Cache : Code Cache: init = 2555904(2496K) used = 1244672(1215K) committed = 2555904(2496K) max = 50331648(49152K)

Memory Pool: PS Eden Space : PS Eden Space: init = 33554432(32768K) used = 32134400(31381K) committed = 33554432(32768K) max = 167772160(163840K)

Memory Pool: PS Survivor Space : PS Survivor Space: init = 5570560(5440K) used = 2311752(2257K) committed = 5570560(5440K) max = 5570560(5440K)

Memory Pool: PS Old Gen : PS Old Gen: init = 89522176(87424K) used = 2341696(2286K) committed = 89522176(87424K) max = 357957632(349568K)

Memory Pool: PS Perm Gen : PS Perm Gen: init = 21757952(21248K) used = 18665144(18227K) committed = 21757952(21248K) max = 268435456(262144K)

JVM Input Arguments : -Djava.util.logging.config.file=/apps/tomcat/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -Xms128m -Xmx512m -XX:MaxPermSize=256m -Djava.endorsed.dirs=/apps/tomcat/endorsed -Dcatalina.base=/apps/tomcat -Dcatalina.home=/apps/tomcat -Djava.io.tmpdir=/apps/tomcat/temp

___ Java System Properties _________________

catalina.base : /apps/tomcat

catalina.home : /apps/tomcat

catalina.useNaming : true

common.loader : ${catalina.base}/lib,

${catalina.base}/lib/*.jar,

${catalina.home}/lib,

${catalina.home}/lib/*.jar

file.encoding : UTF-8

file.encoding.pkg : sun.io

java.awt.graphicsenv : sun.awt.X11GraphicsEnvironment

java.awt.printerjob : sun.print.PSPrinterJob

java.class.version : 50.0

java.home : /usr/java/jdk1.6.0_18/jre

java.io.tmpdir : /apps/tomcat/temp

java.naming.factory.initial : org.apache.naming.java.javaURLContextFactory

java.naming.factory.url.pkgs : org.apache.naming

java.runtime.name : Java(TM) SE Runtime Environment

java.runtime.version : 1.6.0_18-b07

java.specification.name : Java Platform API Specification

java.specification.vendor : Sun Microsystems Inc.

java.specification.version : 1.6

java.util.logging.config.file : /apps/tomcat/conf/logging.properties

java.util.logging.manager : org.apache.juli.ClassLoaderLogManager

java.vendor : Sun Microsystems Inc.

java.vendor.url : http://java.sun.com/

java.vendor.url.bug : http://java.sun.com/cgi-bin/bugreport.cgi

java.version : 1.6.0_18

java.vm.info : mixed mode

java.vm.name : Java HotSpot(TM) 64-Bit Server VM

java.vm.specification.name : Java Virtual Machine Specification

java.vm.specification.vendor : Sun Microsystems Inc.

java.vm.specification.version : 1.0

java.vm.vendor : Sun Microsystems Inc.

java.vm.version : 16.0-b13

mail.mime.decodeparameters : true

org.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER : true

os.arch : amd64

os.name : Linux

os.version : 2.6.18-274.18.1.0.1.el5

package.access : sun.,

org.apache.catalina.,

org.apache.coyote.,

org.apache.tomcat.,

org.apache.jasper.,

sun.beans.

package.definition : sun.,

java.,

org.apache.catalina.,

org.apache.coyote.,

org.apache.tomcat.,

org.apache.jasper.

server.loader :

shared.loader :

sun.arch.data.model : 64

sun.boot.library.path : /usr/java/jdk1.6.0_18/jre/lib/amd64

sun.cpu.endian : little

sun.cpu.isalist :

sun.io.unicode.encoding : UnicodeLittle

sun.java.launcher : SUN_STANDARD

sun.jnu.encoding : UTF-8

sun.management.compiler : HotSpot 64-Bit Server Compiler

sun.os.patch.level : unknown

tomcat.util.buf.StringCache.byte.enabled : true

user.country : US

user.dir : /apps/jira-home/log

user.home : /root

user.language : en

user.name : root

user.timezone : US/Pacific

2012-03-14 10:26:13,933 main INFO atlassian.jira.startup.JiraStartupLogger Running JIRA startup checks.

2012-03-14 10:26:13,977 main INFO atlassian.jira.startup.JiraHomeStartupCheck The jira.home directory '/apps/jira-home' is validated and locked for exclusive use by this instance.

2012-03-14 10:26:13,977 main INFO atlassian.jira.startup.JiraStartupLogger JIRA pre-database startup checks completed successfully.

2012-03-14 10:26:14,167 main INFO jira.config.database.SystemTenantDatabaseConfigurationLoader Reading database configuration from /apps/jira-home/dbconfig.xml

2012-03-14 10:26:14,250 main INFO jira.config.database.DatabaseConfigurationManagerImpl Now running Database Checklist Launcher

============================================

[TylerA]

Per Patrick:

Ok, found the source of the issue. On certain linux platforms the random number generation doesn't function correctly. This is a problem as the jdbc driver needs to encrypt the connect string and username/password when transmitting across the wire. If you don't have that the program just hangs and the driver never succeeds in creating the connection. The fix is to add this line to JAVA_OPTS:

-Djava.security.egd=file:/dev../dev/urandom

Then it will work. The issue is described in detail in these blog posts:

http://www.usn-it.de/index.php/2009/02/20/oracle-11g-jdbc-driver-hangs-blocked-by-devrandom-entropy-pool-empty/

https://forums.oracle.com/forums/thread.jspa?messageID=3793101

[Norman Abramovitz]

Are you sure your jira db user has all the permissions it needs to create/insert/update/delete/drop tables/rows?