FAQ

Servoy Cloud FAQ covering client idle-time shutdown, WAR export dependency exclusions, and svyCloudUtils module setup for Servoy Cloud applications.

How does the idle time shutdown feature work in Servoy Cloud, and how can I modify it?

Default behavior: Servoy Cloud will automatically shut down client sessions that remain idle for more than 30 minutes. This default applies to NG1 and TiNG clients only.

Recommended approach: instead of calling application.addClientInfo() directly, use the svyCloudUtils helpers (part of the svyCloud scope) to set tenant and idle-time metadata safely. For example:

// Set max idle time in minutes using svyCloud (svyCloudUtils)
scopes.svyCloud.setMaxIdleTime(30);

Why use svyCloudUtils? The svyCloud scope ensures values are set consistently and avoids duplicate application.addClientInfo() calls that can overwrite or conflict with existing client metadata. See the svyCloud module docs for details: svyCloud — svyCloudUtils module.

Notes:

• The SERVOY_CLIENT_MAX_IDLE_TIME value (when used directly) is expressed in minutes.

• Maximum allowed value is 180 minutes.

• Batch Processors and headless clients are not affected by this shutdown behavior.

The Cloud Control Center shows tenant and max idle time values in the Active User Sessions table; those values are populated from your application using svyCloudUtils. See the user sessions doc for how these fields are used: Active user sessions.

Why is a plugin JAR missing from the WAR file?

Cause: During WAR export a plugin JAR may be skipped if the export tool detects a duplicate or conflicting library in the lib folder. The export log will show a message similar to:

Dependency '/plugins//.jar' is not exported because '.jar' is already present in the lib folder.

What to do:

• Inspect the warExportCommandLine.log in your pipeline artifacts to confirm which dependency caused the exclusion. For instructions on locating artifacts, see: Package artifacts and how to access them.

• Resolve the library conflict by ensuring a single version of the conflicting dependency is present, or update your build/pipeline configuration to include the required plugin JAR explicitly.

If the missing JAR belongs to a third-party extension, check that extension's documentation for compatibility notes. Also review your solution's extension/plugin docs and your build configuration to confirm whether any optional plugins or helpers are required.