locked
http:// protocol works while dssp.tcp:// does not in cross-node communications RRS feed

  • Question

  • I has following problem with April CTP version. I have two nodes. Node on http port 45000 and tcp port 45001 is started using DssEnvironment class;  node on http port 50000 and tcp port 50001 is started using dsshost.exe. Windows firewall is OFF and no other is installed.

     

    Service that runs on node:45000 tries to create service on node:50000 using constructor service. And the question is:

     

    Why ServiceForwarder to constructor created with dssp.tcp://nt-pc2.mslab.cs.msu.su:50001/constructor/dcd0bad9-526b-463a-9da5-750baf37e14a fails (sometimes silently, sometimes with "Outbound message failed" diagnostics) while ServiceForwarder to http://nt-pc2.mslab.cs.msu.su:50000/constructor/dcd0bad9-526b-463a-9da5-750baf37e14a works fine?

     

    Are there some limitations to cross-node dssp.tcp messaging or do I need to configure my nodes in special way?

     

    Thanks in advance!

    Wednesday, August 13, 2008 10:51 PM

Answers

  • Thank you for answer! DSS node security is turned off.

     

    It seems that problem was in Ccr.Adapters.Io.dll assembly. I didn't include it in hosting application bin folder. After placing it problem disappears.

    Monday, August 18, 2008 8:36 AM

All replies

  • Is there any reason provided in the "outbound message failed"?

     

    Also, make sure that security is either enabled for both nodes or disabled for both nodes. You may have to add an <app>.exe.config file for your dssenvironment host.

     

    Andreas

     

    Friday, August 15, 2008 4:45 PM
  • Thank you for answer! DSS node security is turned off.

     

    It seems that problem was in Ccr.Adapters.Io.dll assembly. I didn't include it in hosting application bin folder. After placing it problem disappears.

    Monday, August 18, 2008 8:36 AM