I have a file server coded in J. It listens on a port and responds to requests.
This morning while testing I canceled the J window that the server was running in, and started it up again. It failed because it said the port number was in use (EADDRINUSE, 10048). This means that when the previous J task was terminated, it was somehow left bound to its port. This could be a problem in the field. I would think that this is an OS bug (Windows XP), but in case there is something that I or j.exe could do to prevent this, I'm reporting it here. Henry Rich ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
