Port Mix-up…how did it ever work?

[Mark Brown]

A problem recently surfaced here that caused a big mess and I don’t understand how it ever worked in the first place.

We were setting up a new system that involved creating 3 new threads and changing 4 existing ones.  Somehow I managed to get 2 threads listening to the same port.  It ran this way for 5 months.  Then suddenly, after our routine monthly reboot of the engine, the threads swapped which caused the data from one system to feed back into itself and the other thread to send incorrect messages to another system.

My question is…why did this ever work at all and why would the threads suddenly swap and continue to work albeit incorrectly?

Topic

[Robert Gordon]

Did you try looking in the revisions diectory.  It could lead you to the culprit.  I have found that the netconfig will save configurations the first time correctly, but subsequent saves goes wrong when threads are renamed especially inbound threads, some of the times my own error.  Created a backup copy the current configuration and the changes.  If using windows use windiff from the resource kit (found at microsoft for free) and in Unix or Aix use diff or sdiff to compare changes.

[Anonymous]

First of all, I am not sure how you got it working for this long. In Clover leaf, there should be one unique port for each theread for listening. For the outbound some receiving systems are able to connect to same port.

Thats means

                    Therea A    

---

> Thread B

                    Thread C    

---

> Thread B

I do not have thread for where theread A and Thread C are listening on same port.

You might want to check this out.

What OS are you using? QDX version ?

thanks

Reggie

[Mark Brown]

I don’t know why it worked either.  

We’re running on Windows Server 2003 and QDX is 5.3 rev 1

[Author]

Replies