CA Service CatalogCA Service Management - Asset Portfolio ManagementCA Service Management - Service Desk Manager
Issue/Introduction
Scheduled Invoices are failing on 17.x with out of the box configuration settings. In the debug Accounting logging we see the errors
java.util.ServiceConfigurationError: com.sun.tools.attach.spi.AttachProvider: Provider sun.tools.attach.WindowsAttachProvider could not be instantiated
and
Spring context has not been initialized. Cannot provided bean:localJmsTopicMgr
Cause
The accounting service is not initializing because the Java process does not have enough memory
Environment
Release: Component: USVCT
Resolution
Correction to the following 3 configuration files is required as per your machine configuration.
#1:- accountingService.conf file in Service Catalog\accounting\conf #2:- viewService.conf file in Service Catalog\view\conf #3:- ehcache.xml file in Service Catalog\view\conf
Steps:- Go to Services.msc. Stop the following services. CA Service Catalog CA Service Accounting
Modify below files as described.
#1:- accountingService.conf file in Service Catalog\accounting\conf Modify the file as following .
# Initial Java Heap Size (in MB) wrapper.java.initmemory=512 # Maximum Java Heap Size (in MB) wrapper.java.maxmemory=1024
#2:- viewService.conf file in Service Catalog\view\conf Modify the file as following . wrapper.java.additional.13=-XX:PermSize=128m wrapper.java.additional.14=-XX:MaxPermSize=512m # Initial Java Heap Size (in MB) wrapper.java.initmemory=1024 # Maximum Java Heap Size (in MB). If maxmemory >= 1024, change -XX:PermSize value from 32m to 128m wrapper.java.maxmemory=2048
#3:- ehcache.xml file in Service Catalog\view\conf Modify the file as following (removed 0(zero)from the original maxBytesLocalHeap values).
Go to Services.msc. Start the following services.
CA Service Catalog CA Service Accounting.
You'll then want to set the scheduled billing to run at some point in the near future, so you can confirm that it takes effect.