Skip to main content

Support Article

DDS nodes display in Joining status and Campaigns do not run



After installing WebLogic Security patch implementing JEP 290, the Decision Data Store (DDS) nodes display in the Joining status in Pega Designer Studio Decisioning Infrastructure landing page. As a result, Campaigns do not execute.

Error Messages

Message in the WebLogic Server logs:

<Info> <> <localhost.localdomain> <DDSServer_1> <DSM init service: DDS.Default> <<anonymous>> <> <6870ae16-8236-45ad-8e88-bdf93b703a50-00000014> <1567007075984> <[severity-value: 64] [rid: 0:42:4] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <ObjectInputFilter REJECTED: class java.rmi.server.RemoteObject, array length: -1, nRefs: 6, depth: 3, bytes: 169, ex: n/a>

Steps to Reproduce

  1. Install WebLogic Security patch.
  2. Restart all the nodes.

Root Cause

A third-party product issue.
The Application server Security patch contains the implementation of the JDK Enhancement Proposal JEP 290: Filter Incoming Serialization Data blocking JMX local traffic on Cassandra port (default port is 7199). Therefore, the Pega Engine is unable to determine the Cassandra Run status.


Make the following change to the operating environment:

Include the below arguments to the Application server Start JVM options:

Suggest Edit

Published August 30, 2019 - Updated October 17, 2019

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.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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