Support Article
Recurrent SocketTimeoutException with VBD and ADM on multi-node
SA-25280
Summary
A Pega Marketing 7.13 application hangs during the execution of outbound campaigns system with recurrent exceptions in the log.
The system become unresponsive and thread dumps are generated as consequence.
Error Messages
Unable to query VBD: Could not access HTTP invoker remote service at [http://your_host:your_port/vbd/service/vbdService]; nested exception is java.net.SocketTimeoutException: Read timed out
Could not access HTTP invoker remote service at [http://your_host:your_port/adm7/ADMServer]; nested exception is java.net.SocketTimeoutException: Read timed out
Steps to Reproduce
- Configure Visual Business Director (VBD) in a multi-node environment.
- Run the application until the interaction history fact table contains tens of millions of rows.
Root Cause
A defect or configuration issue in the operating environment:
Loading the Pega Marketing dashboards involves populating data pages to retrieve KPI metrics for campaign from Visual Business Director.
VBD invalidates its cache based on inactivity. By default, this timeout is set to 12 hours of inactivity
Since the Interaction History table contains, approximately 37 Millions entries in the user environment, the time to populate the VBD cache exceeds the 60 second timeout associated with the data page load activity.
Resolution
Perform the following local-change steps:
1. Increase the VBD cache timeout inserting a row in the database table pr_data_vbd_config using property "vbd.datasource.eviction.timeout" and a value in milliseconds.
2. Restart VBD.
3. Schedule a custom activity to prime the cache of the VBD server in case of restarts and each time the cache timeout take place.
Published August 23, 2017 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.