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

Couldn't initialize services of type[StreamServer] error in log

SA-81130

Summary

User installs Pega 8.1.3. The Decision Strategy Manager (DSM) services are not used  and no nodes are configured on any of the DSM Landing page. However, error occurs in the logs every minute.


Error Messages

(prpc.service.ServiceManager)ERROR - Could not initialize services of type [StreamServer]
(prpc.service.ServiceManager)ERROR - Unexpected exception while bootstrapping service StreamServer
(prpc.service.ServiceManager)ERROR - Unexpected exception while bootstrapping service ADM
(prpc.service.ServiceManager)ERROR - Unexpected exception while bootstrapping service DDS
(prpc.service.ServiceManager)ERROR - Unexpected exception while bootstrapping service DataFlow
(prpc.service.ServiceManager)ERROR - Could not initialize services of type [DataFlow]
(ndexer.DistributedIndexerAgent)ERROR - Exception while performing queue processor management operation
pega.pegarules.pub.context.QueueProcessorManagementOperationsException:Queue processor:pyFTSIncrementalIndexer cannot be started as it is in '-' state

ERROR - Unexpected exception while bootstrapping service StreamServer
java.lang.IllegalArgumentException: pxServiceName should not be blank
at base.Preconditions.checkArgument(Preconditions.java:122)~[guava]
at pega.dsm.dnode.impl.prpc.service.ServiceHierarchy.<init>(ServiceHierarchy.java:47)~[d-node]
at pega.dsm.dnode.impl.prpc.service.ServiceHierarchy.<init>(ServiceHierarchy.java:76)~[d-node]
at pega.dsm.dnode.api.prpc.service.ServiceManager.getServiceHierarchy(ServiceManager.java:605)~[d-node]
at pega.dsm.dnode.api.prpc.service.ServiceManager.getServiceHierarchyOfType(ServiceManager.java:407)~[d-node]
at pega.dsm.dnode.api.prpc.service.ServiceManager.seriallyBootstrapServicesOfType(ServiceManager.java:388)~[d-node]


Steps to Reproduce

Unknown


Root Cause



A software use or operation error. Nodes are configured in the Stream landing page. A single Stream node is required and the users must add two Stream nodes in case of the High availability environment.

Resolution

Perform the following local-change:
Configure a Stream node in the Stream landing page by navigating to Decisioning > Infrastructure > Services > Stream.


 

Suggest Edit

Published 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