Symptom
- SAP Event Stream Processor (ESP) Cluster Database is started.
- ESP node1 is started on one server, e.g. esp01.
- When starting node2 for a second server, e.g. esp02, from the command line of the first server, e.g. esp01, it reports errors:
FATAL - null [esp1] [3.2.5] Hazelcast CANNOT start on this node. No matching network interface found.
Interface matching must be either disabled or updated in the hazelcast.xml config file.
...
FATAL - CODE_700410 | Caught exception while starting node
java.lang.RuntimeException: Hazelcast CANNOT start on this node. No matching network interface found.
Interface matching must be either disabled or updated in the hazelcast.xml config file.
...
INFO - CODE_700025 | Node is stopped
Read more...
Environment
SAP Event Stream Processor (ESP) Cluster Node 5.1 SP11
Product
Keywords
multiple, multinode, multi-node, streaming, processingadd node , KBA , BC-SYB-ESP , Sybase ESP (Event Stream Processor) , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview