Not able to create a new package
Article ID: 87024
Updated On:
Products
CA Automic Dollar Universe
Issue/Introduction
Error Message :
In the univiewer.log file -->
#####
|2016-08-23 16:46:17,030|[BackgroundWorker-63] ERROR [] [com.orsyp.kmeleon.universe.UniverseBusiness] - [Problem occured while saving package NEW_PACKAGE]
com.orsyp.UniverseException: Problem occurred during package save: Could not roll back JPA transaction; nested exception is javax.persistence.PersistenceException: unexpected error when rollbacking
#####
In the derby.log -->
#####
ERROR XSDG1: Page Page(125,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.
#####
#####
Caused by: java.io.IOException: File too large
#####
Patch level detected:Dollar Universe 6.6.21
Product Version: Dollar.Universe 6.6.21
Description :When trying to create a new package, either the screen does not show the sent package, or there is an error message.
In the univiewer.log file -->
#####
|2016-08-23 16:46:17,030|[BackgroundWorker-63] ERROR [] [com.orsyp.kmeleon.universe.UniverseBusiness] - [Problem occured while saving package NEW_PACKAGE]
com.orsyp.UniverseException: Problem occurred during package save: Could not roll back JPA transaction; nested exception is javax.persistence.PersistenceException: unexpected error when rollbacking
#####
In the derby.log -->
#####
ERROR XSDG1: Page Page(125,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.
#####
#####
Caused by: java.io.IOException: File too large
#####
Patch level detected:Dollar Universe 6.6.21
Product Version: Dollar.Universe 6.6.21
Description :When trying to create a new package, either the screen does not show the sent package, or there is an error message.
Environment
OS: Linux
Cause
Cause type:
Configuration
Root Cause: The ulimit value for open files is not set high enough.
Configuration
Root Cause: The ulimit value for open files is not set high enough.
Resolution
The number of open files defined for the user who starts UVMS needs to be increased.
Check what the system limits are for 'open files' using these two commands, while logged in as the user who starts the UVMS:
-> ulimit -Hn
-> ulimit -n
The system limit (-Hn) is the maximum value defined on the system. This can be modified at the OS level in /proc/sys/fs/file-max
The user value (-n) might be the same, or lower than the system limit, but should never be larger. This is the value that should be increased.
In the UVMS node settings, check Advanced Settings for the value defined under 'Maximum number of File Descriptors'.
By default in v6, this value is set to 8000 and should not be larger than the values shown with the ulimit command.
If it is, then the system and user values should be increased to at least 8192.
Please note that if the UVMS is started by a non-root user, and a derby backup is being performed, this value should be set to 12288, and the ulimit values may also need to be increased accordingly.
Fix Status: No Fix
Check what the system limits are for 'open files' using these two commands, while logged in as the user who starts the UVMS:
-> ulimit -Hn
-> ulimit -n
The system limit (-Hn) is the maximum value defined on the system. This can be modified at the OS level in /proc/sys/fs/file-max
The user value (-n) might be the same, or lower than the system limit, but should never be larger. This is the value that should be increased.
In the UVMS node settings, check Advanced Settings for the value defined under 'Maximum number of File Descriptors'.
By default in v6, this value is set to 8000 and should not be larger than the values shown with the ulimit command.
If it is, then the system and user values should be increased to at least 8192.
Please note that if the UVMS is started by a non-root user, and a derby backup is being performed, this value should be set to 12288, and the ulimit values may also need to be increased accordingly.
Fix Status: No Fix
Additional Information
Workaround :
N/A
N/A
Feedback
Yes
No
Powered by
