locked
DtcGetTransactionManager() opens a listener port on a random port number when running on MS cluster node RRS feed

  • Question

  • We have an application which may need to use DTC services and so calls DtcGetTransactionManager() during startup. One of our users reported our application was listening randomly on a port on ip address 0.0.0.0 and sometimes this port number clashed with other applications that were trying to use the same port. On inspection it seems that the listener is probably bound to port 0 allowing the OS to choose the number. This is an example of what we see:

    TCP    0.0.0.0:63180          0.0.0.0:0              LISTENING       8560

    I have traced the listener to the call to DtcGetTransactionManager and the listener is opened when the application is started on a node which is a member of an MSCS cluster. We see no such listener when the application is run on a non-cluster windows server.

    Can anyone explain what this listener is for and whether we can disable it?

    thanks.

    Monday, March 10, 2014 2:19 PM

All replies

  • One of our users reported our application was listening randomly on a port on ip address 0.0.0.0 and sometimes this port number clashed with other applications that were trying to use the same port.

    Hi,

    How do you call DtcGetTransactionManager method in the application code? If you don't want it to open a port on IP "0.0.0.0", you might need to specify another ip and port for this method. 

    Check if this KB helps:

    NETSTAT Displays a LISTENING Port with IP Address 0.0.0.0


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, March 18, 2014 10:04 AM
  • Thanks for the response. Looking at the DtcGetTransactionManager function description in the documentation, there does not appear to be any place to specify a port number, only a host. I should stress we are not initiating a DTC conversation at this point, merely loading the manager. We are keen to understand why this listener port gets created on MSCS nodes when it does not happen on standalone nodes.

    thanks

    Tuesday, March 18, 2014 5:47 PM