UVMS fails to start after crash caused by creation of very large package

Products

• CA Automic Dollar Universe

Issue/Introduction

Error Message :
Derby.log :
------------ BEGIN SHUTDOWN ERROR STACK -------------
ERROR XSDG1: Page Page(145,Container(0, 2256)) could not be written to disk, please check if the disk is full, or if a file system limit, such as a quota or a maximum file size, has been reached.

unistart.log :
Caused by: com.orsyp.InitializationException: Failed initializing server: Could not open JPA EntityManager for transaction; nested exception is javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: Cannot open connection

uvserver.log :
| 2017-11-02 11:12:09 |INFO | main | com.orsyp.central.server.CheckCentralServer | UniverseException: Central IO Connection problem - Connection refused [UJCENT/dollaru_ppd_MgtServer/X]
| 2017-11-02 11:12:11 |ERROR| main | org.hibernate.util.JDBCExceptionReporter | Cannot create PoolableConnectionFactory (Failed to start database '/opt/AUTOMIC/univiewer_server/dollaru_ppd_MgtServer/data/data/uvmsdb' with class loader sun.misc.Launcher$AppClassLoader@77cde100, see the next exception for details.)

UVMS crashes during the creation of a very large package.

Although the error message suggest that the disk it full, system commands show that this is not the case.

It is probably a result of database corruption.

Environment

OS Version: N/A

Cause

Cause type:
Configuration
Root Cause: The System Settings ( File Descriptors) and UVMS JVM settings are too limited to handle big packages

Resolution

1. Increase the following parameters of UVMS and system.

a. Increase the size of the JVM in which UVMS runs, by modifying the file <UVMS>/data/values.xml. Add or increase these two variables UXMINJVMMEM and UXMAXJVMMEM:

 

<var id="UXMAXJVMMEM">4096</var> 
<var id="UXMINJVMMEM">1024</var> 

b. Align the File Descriptor of the server with the default values of UXMAXFD=8000 of UVMS 

 

2. Check the value of ulimit -n and increase to 8192 for the user that starts UVMS (root or for instance uniadm). The value can be defined in /etc/security/limits.d or /etc/security/limits.conf 
3.  In case this does not fix the issue, restore the UVMS Database by replacing the directory <UVMS>/data/data/uvmsdb/ with the one from a previous backup or via the command uniderbyrestore.

Fix Status: No Fix

Fix Version(s):
N/A

Additional Information

Workaround :
N/A