On 11/22/2016 7:14 AM, Donald McLean wrote:
it can't bind to the port one minute and then get connections the next?
Perhaps you accidentally started two copies of the Network Server, in the same directory and (trying to) listen on the same port. Both servers are writing messages to the same derby.log file, but only one of them is successfully accepting connections; the other one may have tried to start, received the "can't bind" error, then quit? Perhaps use the 'ps' command to have a close look at which 'java' processes are running on your machine. Or be more thorough: reboot your machine, then start the Network Server, then check the ps command to make sure all is well, then shut it down, and see if it's acting better now? thanks, bryan
