It has been a growing concern about the remoting that dotnet offers.
I have been developing to major projects using the coding examples given in the books Professional
VB.NET 2nd Edition. Ofcourse I have extended the examples to suite the requirements.
Now I have programmed a Remoting Server, that use the reflection to instantiate the attributed classes in the assembly, and register them as listeners on a TCP port and HTTP port.
The server starts up and everything works well. The client connects and communicates well with the server. While developing this also works well. Stopping/Starting the development projects also works fine.
But THEM! something happens... On the restart of the server it no longer can register to the TCP Port, since it believes that it is already in use.
I have also noticed when this happens SQL Server can no longer bind to its TCP Port 1433.
Though if I wait to restart the Remoting Server, then it does connect and bind to the TCP port and HTTP port.
The problem with this is that it takes about 5- 10 minutes before the ports are released.
This has happened at my home development PC running (Windows 2003 STD), VMWare - (Windows 2003 STD), VMWare ( Windows 2000 ) and Vmware ( Windows XP ).
Though luckily to at my work development PCs.
After consulting may different internet sites, I could not find a suitable solution.
The only one I currently have is to re-install, or to write a lower level remoting class to try to prevent this of error to occur.
I also know that there are other Remoting classes available to buy, but I do not see why this should be a solution, if something should be part of the dotnet framework.
Mr. Jean-Pierré Vermeulen
[email protected]
.NET Remoting VB.NET
