Java Manager won't start on 7.00.21 or superior if node started as non root user

Products

• CA Automic Dollar Universe

Issue/Introduction

The manager Java cannot be activated/started because the autopatch upgrade to 7.00.21 or superior creates a file named $UNI_DIR_DATA/data_java/ws_proxies.xml with the owner root instead of the expected owner administrator of the node (admin).

Permissions of the file:

ls -ltr /path_to_node/data/data_java/ws_proxies.xml
-rw------- 1 root admin 206 Nov 28  2023 /path_to_node/data/data_java/ws_proxies.xml

Error in mgrjava.log:

| 2024-12-25 12:56:37 |ERROR| main | com.orsyp.mgr4java.configuration.AbstractFeatureConfiguration |  /path_to_node/data/data_java/ws_proxies.xml (Permission denied) 
java.io.FileNotFoundException:  /path_to_node/data/data_java/ws_proxies.xml (Permission denied)

Expected behavior: upgrade should create the file with the correct owner or modify the owner post copy.
Actual behavior: because of the file belonging to root, on installations where the administrator of the processes is other than root, the manager for java won't start because it reads or writes to this file upon startup.

Environment

Dollar Universe 7.00.21 or superior where node starts as other user than root and has been autopatched.

Manager for Java

Cause

Defect

Resolution

Workaround:

Change the owner of the file /path_to_node/data/data_java/ws_proxies.xml to the one starting the Dollar Universe processes, ie. for admin user and admin group:

chown admin:admin /path_to_node/data/data_java/ws_proxies.xml 

After that the manager for Java can be started.

Solution:

Update to a fix version listed below or a newer version if available.

Fix version(s): 
Component: Application.Server (Node)
Dollar Universe 7.01.11 - planned release October 2025

Additional Information

Defect ID: DE165883

Defect Public Description: Java Manager won't start on 7.00.21 or superior if node started as non root user and upgraded by autopatch

Defect Resolution: Fixed chown on file after copying it.