Framework Server FAQ's and Error Conditions

RapidDeploy Oracle Database

1. RapidDeploy fails to start with an SQLException: Io exception thrown:
2. RapidDeploy fails to start with an SQLException: Listener refused error:
3. RapidDeploy fails to create a new environment with an sql error:

RapidDeploy Package Creation

1. Creating a package gives rise to an unpredictable sequence number

RapidDeploy Oracle Database

RapidDeploy fails to start with an SQLException: Io exception thrown:

The first error seen in the logs looks like the following:

java.sql.SQLException: unable to get a connection from pool of a PoolingDataSource containing an XAPool of resource dataSource with 0 connection(s) (0 still available)

Later on in the logs you see this:

Caused by: 
java.sql.SQLException: Io exception: The Network Adapter could not establish the connection

This is likely due to the Oracle database listener not running. Start the database listener and restart the framework server.

---

RapidDeploy fails to start with an SQLException: Listener refused error:

The first error seen in the logs looks like the following:

java.sql.SQLException: unable to get a connection from pool of a PoolingDataSource containing an XAPool of resource dataSource with 0 connection(s) (0 still available)

Later on in the logs you see this:

Caused by: 
java.sql.SQLException: Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
The Connection descriptor used by the client was:
localhost:1521:XE

This is likely due to the Oracle database is not running or the listener not being configured with the given SID. Start the Oracle database and restart the framework server.

---

RapidDeploy fails to create a new environment with an sql error:

The first error seen in the logs and console looks like the following:

Cannot insert null into component_instance.id

This is because a trigger needs compiling. Please run the following script:

${MV_HOME}/web-apps/db/scripts/oracle_vX/postprocessing/VERSION-compile-all-triggers.sql

Restart RapidDeploy following this action.

RapidDeploy Package Creation

Creating a package gives rise to an unpredictable sequence number

This can happen when a previous deployment has updated configuration dynamically (e.g when deploying the latest configuration). The way numbering works is to increment the last block of numbers (however they are separated) by 1. When a late configuration is deployed the original deployment package is renumberd with a timestamp. A subsequent packaging request will increment that timestamp. In this instance, simply replace the timestamp with your next version sequence number and numbering will resume from that point on normally.