CA Release Automation IO Error: The Network Adapter could not establish the connection

Document ID : KB000106854
Last Modified Date : 17/07/2018
Show Technical Document Details
Issue:
The Release Automation Application Server cannot connect to the Database Server. The following error is seen in the nolio_dm_all log:

2018-07-08 11:47:59,253 [localhost-startStop-1] ERROR (com.nolio.platform.server.dataservices.services.upgrade.UpgradeServiceImpl:901) - Could not update version table. 
org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: Cannot create PoolableConnectionFactory (IO Error: The Network Adapter could not establish the connection) 
at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:80) 
Caused by: java.sql.SQLException: Cannot create PoolableConnectionFactory (IO Error: The Network Adapter could not establish the connection)
Environment:
All versions of CA Release Automation
Database - Oracle
Resolution:
The error 'Could not get JDBC Connection; nested exception is java.sql.SQLException: Cannot create PoolableConnectionFactory (IO Error: The Network Adapter could not establish the connection)'  can occur due to one of the following reasons:

1. Incorrect server information in tsnnames.ora and listener.ora files.
 
LISTENER_ORCL =
(ADDRESS = (PROTOCOL = TCP)(HOST = <Servername>)(PORT = <port>))

2. Incorrect database information in <RA HOME>\webapps\datamanagement\WEB-INF\distributed.propertes

# Database props
data.management.database.host = <DB Server>
data.management.database.port = <DB Port>
data.management.database.name = <DB Name>
data.management.database.user = <nolio DB User>
# The DB password shall be encrypted. Please use the encrypt_password.bat/sh utility to encrypt the password.
data.management.database.pwd = xxxxxxxxxxxxxxxxxxxxxxxxxx
data.management.database.create = false


3. Network issue between the Release Automation Application Server and the Database Server. Check whether you are able to Telnet the Database server using the Hostname/IP address on the configured port.

4. Oracle listener is not running. The status can be confirmed using the command:
lsnrctl status

5. JDBC connection issue due to incorrect Java version being used on the Release Automation Application Server.
Additional Information:
How to test JDBC connection to an Oracle Server?
https://comm.support.ca.com/kb/how-to-test-jdbc-connection-to-an-oracle-server/kb000106561