Release Notes 3.1.385

Publication Date: July 29th 2017

The following are the news features, enhancements and fixed issues for Cloud CMS 3.1.385 release.

Cloud CMS API

• Improved strategy for discovering custom log4j2-*.xml files from JAR files, classpath and Docker-mounted volumes (and faster load times)
• Send Email Action now auto-populates with default Email Provider settings when triggered as part of a release (and if host/username properties are not otherwise specified on the action configuration)
• Adjustments to default S3BinaryStorageProvider HTTP connection pool for lower socket and request timeouts, allowing for faster error handling and thread turnaround
• Health Check Controller now more accurate with separate CPU usage tracking for process versus system and better accuracy across VM's with multiple cores.
• S3 logging now uses "cluster.group.name" in generating key for write to S3
• Fix for distributed Quartz Job Store
• Removed extra dependencies that were no longer needed
• Added DiagInfoController to handle back admin-level debugging information for server
• Adjusted Log4j2 appender order and default config to make things a bit faster

Cloud CMS Application Server

• Improved strategy for determining host in multiple environments (local, hosted, virtual host, behind a CDN and behind a proxy)
• Proxy calls now use changeOrigin
• The insight.js analytics now uses a better expiration date, allowing for accurate invalidation

Cloud CMS Command Line Client

• Improved latency tests to provide measurements against http://api.cloudcms.com and https://api.cloudcms.com as well as our two CDN endpoints (http://api1.cloudcms.com and https://api1.cloudcms.com)
• Updated Gitana driver version