Troubleshooting
Problem
When starting agents and integration servers, the third-party caching framework Ehcache is initialized as well. Ehcache provides a built-in update check mechanism which performs an HTTP call to an outbound address which might not be wanted in a production environment.
Diagnosing The Problem
You may discover traffic to an address like org01.terracotta.org when running network diagnosis. Additionally, the HTTP call can be observed when tracing the agent / integration server with yfs.logall=Y. The following is printed in the log:
DEBUG :net.sf.ehcache.CacheManager@45644564: Checking for update... [system]: UpdateChecker
Resolving The Problem
Locate your agent and integration server startup scripts in <INSTALL_DIR>/bin:
- agentserver.cmd/sh
- agentserver.cmd/sh.in
- startIntegrationServer.cmd/sh
- startIntegrationServer.cmd/sh.in
Add the following property to AGENT_JAVA_OPTS and save the files:
-Dnet.sf.ehcache.skipUpdateCheck=true
This property will disable the automatic Ehcache update check.
As IBM Sterling Selling and Fulfillment Suite is certified with a fix version of Ehcache, a software update or update check will not be necessary when running the application.
Was this topic helpful?
Document Information
Modified date:
10 May 2022
UID
swg21626160