There was no endpoint listening RRS feed

  • Question

  • Hi,

    Can somebody let me know what this error message means and where exactly it occurs? could it be caused by resource scarce on compute nodes, such as low memory?

     There was no endpoint listening at net.tcp://server1:9091/352450/NetTcp/GetResponse that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. 



    Tuesday, September 17, 2019 5:36 PM

All replies

  • Hi Diane,

    The endpoint is supposed to be opened on the broker worker for the SOA client to get responses. The error could happen on the SOA client if the broker worker has already exited. You may want to check the broker node server1 and the broker worker logs for this SOA session.


    Yutong Sun

    Sunday, September 22, 2019 7:53 AM
  • Thank you Yutong! When you say broker worker, do you mean the compute node? How do I get broker worker logs for the SOA session?


    Monday, September 23, 2019 5:10 PM
  • Broker worker is in your broker nodes (or head node if you don't have dedicated broker node, and use head node as broker node)
    Tuesday, September 24, 2019 2:59 AM
  • Thank you Sunbin!

    Tuesday, September 24, 2019 8:16 PM