Problem
If the Workbench server is constrained for resources, there is a possibility that Workbench will show errors in workbench log file mci.log soon after startup.
Solution
The JAVA_OPTS environment variable can be set to modify the resource usage of Java. More specifically, you can halve the Java Stack Size from 2MB to 1MB.
e.g. $JAVA_OPTS=-Xss1024K
Related articles
- MettleCI CLI produces SLF4J errors
- Configuring MettleCI Workbench to use a Custom Port Number
- MettleCI - Infrastructure Requirements
- Running Unit Test Interception produces an error 'Can not deserialize'
- GitLab
- MettleCI CLI produces 'Failed to connect to host' error
- Configuring Authentication between Workbench and Atlassian Bitbucket
- SSLHandshakeException in Workbench after configuring issue lookup
- How does the integration/configuration with BitBucket, Jira, and Bamboo work?
- Bamboo Agent produces chcp or -107374 errors
- Azure pipeline error "You need the Git 'GenericContribute' permission"
- Command timed out waiting to complete
- The MettleCI Bamboo Command Plugin fails with NoSuchMethodError
- Workbench produces 'Failed to initialize DATASTAGE_ASB authentication' error on startup
- Workbench operations return ‘Could not find specified assets’