No Directory Permission When Deploying a JAR Package

Scenario

#

When E10 Ecode reports a directory-permission error while deploying a JAR package, first check whether the secdevjar deployment share path points to an actual writable directory.

Database Location

#

• Standalone mode: the ecology10 database.
• Combined mode: the e10_core_business database.

Fix

#

Query the current configuration first:

SELECT data_key, data_value
FROM ecod_system_config
WHERE data_key = 'weaver.ecode.secdevjar.deploy.sharepath';

Update data_value to the actual usable directory:

UPDATE ecod_system_config
SET data_value = '/actual/usable/path/secdevjar'
WHERE data_key = 'weaver.ecode.secdevjar.deploy.sharepath';

The directory must be readable and writable by the Ecode service process.

Reload Cache

#

After updating the database, call this endpoint to reload the system configuration cache:

/api/ecode/repair/innerOpt/reloadSystemConfig

In a cluster, call it several times so each node reloads the new system configuration. Then deploy the JAR package again to verify the fix.