Troubleshooting Mango Overrides Property File Loading

Mango will continue using a file under /home/solergy/MANGO/MA_HOME_TERLIZZI/classes/ when the override is outside the active Mango home, unreadable by the service account, or not detected because the running process predates the file change. Resolve the active home first, validate the override path and access permissions, then restart Mango and test a controlled property change.

Active Mango Home Selection

Before anything else, confirm which Mango installation the running process uses. The path /home/solergy/MANGO/MA_HOME_TERLIZZI/classes/ indicates that /home/solergy/MANGO/MA_HOME_TERLIZZI is a likely active home, but the running process is the authority. A second installation, a service definition pointing elsewhere, or a process started from another environment can make a correctly constructed override directory irrelevant.

1. Identify the running Mango process and its service definition.
2. Inspect the process command line, working directory, environment, and startup configuration for the active home path.
3. Compare that path with the installation where overrides/properties was created.
4. If multiple Mango installations exist, record which one owns the active classes directory and which one contains the override.

Check	Required result	Failure indicated
Runtime home	The running process points to /home/solergy/MANGO/MA_HOME_TERLIZZI or another clearly identified home	The override was placed under a different installation
Service definition	Its paths agree with the running process	A stale or alternate service configuration is launching Mango
Override location	It belongs to the active home	The directory is valid but outside the runtime search tree

Do not move on until the active process and the override directory resolve to the same Mango home.

Override Directory and File Placement

Create the override hierarchy relative to the confirmed home, not relative to the shell's current directory or a convenient parent folder. For the observed installation, the candidate location is /home/solergy/MANGO/MA_HOME_TERLIZZI/overrides/properties/.

1. Confirm that both overrides and properties are real directories rather than broken symbolic links.
2. Place the intended property file directly in the required relative location beneath overrides/properties.
3. Compare its filename, capitalization, and extension with the corresponding file Mango currently obtains from classes. Linux path and filename comparisons are case-sensitive.
4. Check that the file contains the intended key and that the key is not misspelled or duplicated later in the same file.

Copy only the property file being tested. Copying an entire classes tree into the override area can introduce unrelated settings and obscure which file changed runtime behavior.

The placement check passes when the override has the intended relative name beneath the active home's overrides/properties directory and its target key can be identified unambiguously.

Service Account Read Access

A file copied as root can exist in the correct directory yet remain unavailable to Mango. Ownership alone does not determine access; the service account needs traversal permission on every parent directory and read permission on the file. Group ownership of root is a warning sign when the service runs under another account and group permissions do not grant access.

1. Identify the operating-system user and group running Mango.
2. Inspect ownership and permission bits on the Mango home, overrides, properties, and the property file.
3. Test file readability as the Mango service account rather than as an administrator.
4. If the test fails, assign ownership or group membership according to the site's service-account policy and grant only the directory traversal and file-read access required.
5. Repeat the readability test after changing ownership or permissions.

Object	Access Mango needs	Typical symptom when missing
Parent directories	Traversal by the service account	The file appears present to an administrator but cannot be reached by Mango
Property file	Read access by the service account	Mango continues with another readable configuration source
Symbolic-link target, if used	Traversal and read access across the complete target path	The link exists but resolves to an inaccessible location

Do not continue until a read test executed with the Mango service identity succeeds without elevated privileges.

Controlled Mango Restart

Property discovery commonly occurs during application startup. Copying a file into overrides/properties while Mango remains running does not prove that the active process has rescanned the directory. Restart the same instance whose home and service identity were verified.

1. Record the current process identity so an incomplete restart is easy to detect.
2. Restart Mango through the installation's normal service-control method.
3. Confirm that the old process ended and a new process started.
4. Review startup output for path, access, parsing, or property-loading errors.
5. Wait for normal application startup to complete before judging the property value.

A user-interface refresh, browser restart, or client reconnection is not a Mango process restart. Likewise, starting a second copy manually can leave the original service handling requests.

The restart check passes only when a new Mango process is running from the confirmed home and startup diagnostics contain no error for the override path or file.

Property Selection and Precedence Test

Seeing a resource under classes does not by itself prove that the override directory was ignored. The base file can remain present while an override supplies only selected values. Test effective behavior, not file existence.

1. Select one known property with a safe, observable effect and a value that can be restored immediately.
2. Record the current effective value.
3. Change only that property in the override file, using valid property syntax.
4. Restart Mango again so the test follows the same startup path.
5. Observe the effective value through the application behavior or the applicable runtime diagnostic.

If the value does not change, recheck the filename and relative path first, then service-account readability, parsing errors, and whether the restarted process belongs to another installation. If the value changes, the override path is active even though the corresponding base file remains under classes.

Do not move on until one isolated property demonstrates which source wins at runtime.

End-to-End Verification

1. Restore the test property if its temporary value is not the required production setting.
2. Apply the intended property value in the verified override file.
3. Restart the confirmed Mango service.
4. Confirm that the new process uses the same active home and service account.
5. Check startup diagnostics for file-access and property-parsing errors.
6. Verify the intended behavior from the application side, then confirm that it remains correct after one additional controlled restart.

The commissioning result is valid when the override file is readable under the service identity, the intended property controls runtime behavior, and the same result survives a restart without editing the file under classes.

Frequently Asked Questions