Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

SocketException when adding large user segment in campaign

SA-24273

Summary



Selected 266,000 users do not appear on the grid containing the selected users. An error message appeared in the PegaRULES log. Thread dumps were generated. All threads wait for the completion of add operation, performed by a thread.

Error Messages



java.net.SocketException: Connection reset
com.pega.pegarules.data.internal.access.DeferredOperationsImpl.add(DeferredOperationsImpl.java:365)
at
com.pega.pegarules.data.internal.access.DeferredOperationsImpl.addInsertUpdateOpsToDeferredOpsList(DeferredOperationsImpl.java:2702)
at com.pega.pegarules.data.internal.access.Saver.saveDeferred(Saver.java:415)
at com.pega.pegarules.data.internal.access.DatabaseImpl.saveDeferred(DatabaseImpl.java:5089)
at com.pega.pegarules.data.internal.access.DatabaseImpl.saveDeferred(DatabaseImpl.java:5073)
.
.
.

Steps to Reproduce

  1. Create a Field Marketing Campaign using an Offer with a large Segment attached in the Field Marketing portal.
  2. Navigate to the Campaign Contacts Section and select all users.
  3. Click Add Selected.

Root Cause



The Field Marketing capability was originally built for typical field scenarios (thousands of contacts) and does not support the volumes used (hundreds of thousands). This affects any operation that utilizes Select All mechanism, such as Add All and Remove All, when used standalone or in combination with filters. The filters include column filters, top-level filters, and Segment pre-filters. Another area of impact was the automatic removal of invalid contacts from Campaigns due to a change in territory definition and pre-filter Segment population.

In any of these operations, the existing implementation runs a report definition and iterates over results, building a map of selected items. Finally, it iterated over the map and deferred the save or delete on each entry in the map.

Resolution



Apply HFix-27782
Suggest Edit

Published August 23, 2017 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us