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

Stream node failing to start on WebLogic with bind port error



Pega 8.1.3 is installed on WebLogic.

The default Bind ports required for the Stream service are not used before the system is started. While the node starts successfully, errors related to starting the Stream node are generated in the logs since the JVM_Bind port is already in use. Hence, cannot use any of the features that the stream is required for since the stream node cannot be started.

Error Messages

Caused by: Address already in use: JVM_Bind
    at Method)
    at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(
    at sun.rmi.transport.tcp.TCPTransport.listen(

Steps to Reproduce

Start a node with NodeType of Stream.

Root Cause

A defect or configuration issue in the operating environment.

A new feature added to the WebLogic 12.1.3, caused a backward compatibility issue.
The issue occurred due to the 'Filter incoming serialization data' Java 8 security feature in WebLogic. When this filter mechanism takes effect, the serialization maximum depth is 100 (this depth is insufficient).


Perform the following local-change:

Add the following JVM arguments for each JVM. To add the JVMs, tune the parameters to increase the serialization object graph depth to more than 100 which is the default maximum depth that WebLogic allows.

Suggest Edit

Published August 19, 2019 - 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